Hi all, I’ve seen others have had this issue too but wondering if anyone can help me find the answer.
My hardware is: RPi running hass.io, with AEOTEC Z-Stick plugged in. So far so good. Tried to sync my AEOTEC door sensor using ‘Add Node’ in the Z-wave config within hass.io GUI but clicking ‘Add Node’ didn’t seem to do anything, so I synced it in the normal way (pressing button on stick and on sensor. Both devices are showing in hass.io:
however, triggering the sensor yields no apparent activity in the GUI. When I check the OZW logs (in the GUI), I see this:
So, it seems to be sending through a ‘basic set’ instead of ‘binary set’.
I scroll up to Node Management, choose my sensor from the dropdown, choose ‘binary’ from the Config Parameters dropdown:
… and click ‘Set Config Parameter’.
Then update the logs, they show this:
Then I go back to ‘States’, nothing has changed. Trigger the sensor again, and it’s still coming through as ‘Basic’:
In Developer Tools / Info button (left menu at the bottom right), the following error also shows up:
2017-08-29 15:30:23 ERROR (MainThread) [homeassistant.core] Invalid service data for zwave.set_config_parameter: required key not provided @ data['value']. Got None
Could this mean that it’s the parameter value that’s wrong? I’ve found the troubleshooting page for this sensor:
… and it says:
So I’ve tried changing parameter 121 in the parameter value dropdown, tried making this ‘basic and binary’ or just ‘binary’ neither has yielded any useful change to the logs (as far as I can tell) when it comes to the result of triggering the sensor:
2017-08-29 16:21:22.077 Detail, Node003, Refreshed Value: old value=255, new value=0, type=byte 2017-08-29 16:21:22.077 Detail, Node003, Changes to this value are not verified 2017-08-29 16:21:22.077 Detail, Node003, Notification: ValueChanged 2017-08-29 16:21:24.653 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x20, 0x01, 0xff, 0x2c 2017-08-29 16:21:24.653 Detail, 2017-08-29 16:21:24.653 Info, Node003, Received Basic set from node 3: level=255. Treating it as a Basic report. 2017-08-29 16:21:24.653 Detail, Node003, Refreshed Value: old value=0, new value=255, type=byte 2017-08-29 16:21:24.654 Detail, Node003, Changes to this value are not verified 2017-08-29 16:21:24.654 Detail, Node003, Notification: ValueChanged
In trying to troubleshoot, I’ve fired up Virtualbox on my (Win10) PC, run CentOS7, installed Docker and then ozcp (to try to edit the sensor and change it to binary through there), but the z-stick doesn’t show up in ozcp (maybe due to windows incompatibility, I’m not sure)
Any advice would be appreciated. Thanks!