Project

General

Profile

Bug #593

Aeotec MultiSensor6 - UV sensor not reporting in DomotiGa

Added by marmachine over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DomoZWave
Target version:
Start date:
11/13/2015
Due date:
% Done:

100%

Estimated time:
Resolution:
Works For Me

Description

Hi,

I have been talking to Aeotec on the issue why i am not receiving any value update on the UV sensor. Basically when the sensor placed inside, there would hardly be any UV value, however it should report/update the value even though it is 0.

Parameter 101 determines which values should be returned (as Group 1). You set a value to select which you want to include. The value you set is the sum of all sensors in below list:

1 = Battery Sensor (which is why 225 is set for battery powered)
16 = UV Sensor
32 = Temperature
64 = Humidity
128 = Light

If everything is added together, (to report all sensors) the value should be set to 241 on batery or 240 on USB power.

Note: Earlier (224 and 225) values belong to older model where no UV sensor was present. With the newer (MultiSensor6) model you need to set a different value.

Set Parameter 40 [1 byte dec] = 0, to disable threshold (DomotiGa offers selector instead of a value, to set to disable)

Also determine the firmware version, before V1.6, UV sensor does not report.

As i was testing the vibration sensor, investigating why it doesn't report/update in DomotiGa, i noticed that other sensors, BUT the UV and Vibration values, are updated by the event.

In the logging however i can't find any reported value from the UV sensor. So i am not sure if this is a DomotiGa or Aeotec related issue (yet). I intend to install Domoticz to test the sensor in that system as well. Aeotec replied on this as well, after checking all requirements;

it should be fine overall, you can try different systems. I can make a few tests with the Z-Stick Gen5 and the Multisensor 6 on Domoticz or Domotiga

Logging files attached.

Vibration_triggered_logging.docx (56.5 KB) Vibration_triggered_logging.docx marmachine, 11/13/2015 10:34 AM

History

#1 Updated by johanvandyck over 3 years ago

Hi

I found it difficult to extract your problem in this bug-report. I understand your sensor is not reported value5 and 6 (UV and burglar alarm).

After updating to the latest openzwave (version 589) it was working out of the box. Of course after enabling the sensor (parameter 101 = 241).

The UV index is always 0, but I could only test it inside. An extract of my ~domotiga/logs/server-domozwave-2015-11.log

2015-11-30 21:30:11:299 [DomoZwave] JSON-RPC call successful
2015-11-30 21:30:11:300 [DomoZwave] NodeQueriesComplete: HomeId=0x184cf27 Node=14
2015-11-30 21:30:11:300 [DomoZwave] NodeQueriesComplete: HomeId=0x184cf27 Node=26
2015-11-30 21:30:11:466 [DomoZwave] ValueChanged: HomeId=0x184cf27 Node=26
2015-11-30 21:30:11:467 [DomoZwave] Genre=user (1)
2015-11-30 21:30:11:467 [DomoZwave] CommandClass=COMMAND_CLASS_SENSOR_MULTILEVEL (49)
2015-11-30 21:30:11:467 [DomoZwave] Instance=1
2015-11-30 21:30:11:467 [DomoZwave] Index=27
2015-11-30 21:30:11:467 [DomoZwave] Label=Ultraviolet
2015-11-30 21:30:11:467 [DomoZwave] Units=
2015-11-30 21:30:11:467 [DomoZwave] Type=Decimal (raw value=0)
2015-11-30 21:30:11:467 [DomoZwave] Value5=0
2015-11-30 21:30:11:467 [DomoZwave] JSON-RPC: HomeId=0x184cf27 Method=openzwave.setvalue
2015-11-30 21:30:11:467 [DomoZwave] Data={ "jsonrpc": "2.0", "method": "openzwave.setvalue", "params": { "homeid": 25480999, "nodeid": 26, "instanceid": 1, "valueid": 5, "value": "0", "label": "Ultraviolet", "unit": "" }, "id": 1533 }

As for the burglar alarm, I don't know yet how it is functioning. Clearly I receive every time when I "move" my sensor an alarm, but the contend is not clear. I also got a DomotiGa error.

After "moving" my sensor, this is the debug log of my node 26.

2015/11/30 21:50:03 [OpenZWave] Got a RemoteCall for Method 'openzwave.setvalue', Params '{"homeid": 25480999, "nodeid": 26, "instanceid": 1, "valueid": 6, "value": "Secure", "label": "Alarm Level", "unit": ""}'
2015/11/30 21:50:03 [OpenZWave] Got value changed notification for node 26 and instance 1 value6 changed to Secure.
2015/11/30 21:50:03 [Devices] Device with address '26' is 'Slaapkamer JVD - Multi6'
2015/11/30 21:50:03 [Devices] ValueUpdate called for device with id '79' valuenum '6' and value 'Secure'
2015/11/30 21:50:03 [OpenZWave] Response for Method 'openzwave.setvalue' Data 'true'

My server-domozwave-2015-11.log shows:

2015-11-30 21:50:00:166 [DomoZwave] DomoZWave_RequestNodeDynamic: HomeId=0x184cf27 Node=17
2015-11-30 21:50:00:168 [DomoZwave] DomoZWave_RequestNodeDynamic: HomeId=0x184cf27 Node=23
2015-11-30 21:50:00:170 [DomoZwave] DomoZWave_RequestNodeDynamic: HomeId=0x184cf27 Node=24
2015-11-30 21:50:03:871 [DomoZwave] ValueChanged: HomeId=0x184cf27 Node=26
2015-11-30 21:50:03:871 [DomoZwave] Genre=user (1)
2015-11-30 21:50:03:871 [DomoZwave] CommandClass=COMMAND_CLASS_ALARM (113)
2015-11-30 21:50:03:871 [DomoZwave] Instance=1
2015-11-30 21:50:03:871 [DomoZwave] Index=0
2015-11-30 21:50:03:871 [DomoZwave] Label=Alarm Type
2015-11-30 21:50:03:871 [DomoZwave] Units=
2015-11-30 21:50:03:871 [DomoZwave] Type=Byte (raw value=0)
2015-11-30 21:50:03:871 [DomoZwave] Value=0
2015-11-30 21:50:03:871 [DomoZwave] Note=Value not send, CommandClassId & label combination isn't supported by DomotiGa (this is not an issue)
2015-11-30 21:50:03:871 [DomoZwave] ValueChanged: HomeId=0x184cf27 Node=26
2015-11-30 21:50:03:871 [DomoZwave] Genre=user (1)
2015-11-30 21:50:03:871 [DomoZwave] CommandClass=COMMAND_CLASS_ALARM (113)
2015-11-30 21:50:03:872 [DomoZwave] Instance=1
2015-11-30 21:50:03:872 [DomoZwave] Index=1
2015-11-30 21:50:03:872 [DomoZwave] Label=Alarm Level
2015-11-30 21:50:03:872 [DomoZwave] Units=
2015-11-30 21:50:03:872 [DomoZwave] Type=Byte (raw value=0)
2015-11-30 21:50:03:872 [DomoZwave] Value6=Secure
2015-11-30 21:50:03:872 [DomoZwave] JSON-RPC: HomeId=0x184cf27 Method=openzwave.setvalue
2015-11-30 21:50:03:872 [DomoZwave] Data={ "jsonrpc": "2.0", "method": "openzwave.setvalue", "params": { "homeid": 25480999, "nodeid": 26, "instanceid": 1, "valueid": 6, "value": "Secure", "label": "Alarm Level", "unit": "" }, "id": 1549 }
2015-11-30 21:50:03:891 [DomoZwave] JSON-RPC call successful
2015-11-30 21:50:03:892 [DomoZwave] ValueChanged: HomeId=0x184cf27 Node=26
2015-11-30 21:50:03:892 [DomoZwave] Genre=user (1)
2015-11-30 21:50:03:892 [DomoZwave] CommandClass=COMMAND_CLASS_ALARM (113)
2015-11-30 21:50:03:892 [DomoZwave] Instance=1
2015-11-30 21:50:03:892 [DomoZwave] Index=2
2015-11-30 21:50:03:892 [DomoZwave] Label=SourceNodeId
2015-11-30 21:50:03:892 [DomoZwave] Units=
2015-11-30 21:50:03:892 [DomoZwave] Type=Byte (raw value=0)
2015-11-30 21:50:03:893 [DomoZwave] Value=0
2015-11-30 21:50:03:893 [DomoZwave] Note=Value not send, CommandClassId & label combination isn't supported by DomotiGa (this is not an issue)
2015-11-30 21:50:03:893 [DomoZwave] ValueChanged: HomeId=0x184cf27 Node=26
2015-11-30 21:50:03:893 [DomoZwave] Genre=user (1)
2015-11-30 21:50:03:893 [DomoZwave] CommandClass=COMMAND_CLASS_ALARM (113)
2015-11-30 21:50:03:893 [DomoZwave] Instance=1
2015-11-30 21:50:03:893 [DomoZwave] Index=10
2015-11-30 21:50:03:893 [DomoZwave] Label=Burglar
2015-11-30 21:50:03:893 [DomoZwave] Units=
2015-11-30 21:50:03:893 [DomoZwave] Type=Byte (raw value=3)
2015-11-30 21:50:03:893 [DomoZwave] Value=3
2015-11-30 21:50:03:893 [DomoZwave] Note=Value not send, CommandClassId & label combination isn't supported by DomotiGa (this is not an issue)

No doubt, this is not the last update for this issue.

Regards

Johan.

#2 Updated by Alexie about 3 years ago

  • Category set to DomoZWave
  • Status changed from New to Feedback
  • Assignee set to Alexie
  • Target version set to 1.0.022
  • Resolution set to Works For Me

Hi,

I checked your logfile and there is no UV (Ultraviolet) reported by the open-zwave library, thus it isn't reported to the DomoZWave wrapper. I don't think you will get a different result with Domoticz.

If you have a copy of the zwcfg*xml, email it to me, or check for "Ultraviolet" ... If it isn't in the file, the device can't do it, or isn't configured for it.

#3 Updated by Alexie almost 3 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF