[Resolved] Problems with Z Wave UI, Automation seems to work

Configuration Z-Wave
,
1

I’m having issues with my Z Wave Network consisting of 1 ZWP light switch, 1 Cooper Aspire Dimmer, and 1 Cooper switched receptacle. If all the devices are off I can turn them on with HA UI, but the web interface will go back to off state even though the light is on. So now I am unable to turn the switch/light off because the UI believes its already off. My automations seem to work just fine. For example I have the ZWP light switch to turn my outside lights on and off depending on the sun. This seems to work well but the UI never shows the switch/lights being on. Here is the OZW log. It shows the switch off, then I turn it on with the web UI. I wait a moment then turn it off locally at the switch. Lastly in the log it shows the automation turning the switch on, which it does, but the web UI still shows it off.
ESXI 6.5 Ubuntu Server 16.04, HA 63.3, python 3.5, aeotec z-stick gen5


2018-02-18 16:02:13.688 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2018-02-18 16:02:13.688 Info, Node004, SwitchBinary::Set - Setting node 4 to On
2018-02-18 16:02:13.688 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2a, 0x35
2018-02-18 16:02:13.688 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x2b, 0xca
2018-02-18 16:02:13.688 Detail,
2018-02-18 16:02:13.688 Info, Node004, Sending (Send) message (Callback ID=0x2a, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2a, 0x35
2018-02-18 16:02:14.688 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-18 16:02:14.688 Detail, Node004, Removing current message
2018-02-18 16:02:14.688 Detail, Node004, Notification: Notification - TimeOut
2018-02-18 16:02:14.689 Detail,
2018-02-18 16:02:14.689 Info, Node004, Sending (Send) message (Callback ID=0x2b, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x2b, 0xca
2018-02-18 16:02:15.690 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-18 16:02:15.690 Detail, Node004, Removing current message
2018-02-18 16:02:15.690 Detail, Node004, Notification: Notification - TimeOut
2018-02-18 16:02:35.791 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2018-02-18 16:02:35.791 Info, Node004, SwitchBinary::Set - Setting node 4 to On
2018-02-18 16:02:35.791 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2c, 0x33
2018-02-18 16:02:35.791 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x2d, 0xcc
2018-02-18 16:02:35.791 Detail,
2018-02-18 16:02:35.791 Info, Node004, Sending (Send) message (Callback ID=0x2c, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2c, 0x33
2018-02-18 16:02:36.791 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-18 16:02:36.791 Detail, Node004, Removing current message
2018-02-18 16:02:36.791 Detail, Node004, Notification: Notification - TimeOut
2018-02-18 16:02:36.792 Detail,
2018-02-18 16:02:36.792 Info, Node004, Sending (Send) message (Callback ID=0x2d, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x2d, 0xcc
2018-02-18 16:02:37.792 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-18 16:02:37.792 Detail, Node004, Removing current message
2018-02-18 16:02:37.792 Detail, Node004, Notification: Notification - TimeOut
2018-02-18 17:40:32.734 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2018-02-18 17:40:32.734 Info, Node004, SwitchBinary::Set - Setting node 4 to On
2018-02-18 17:40:32.734 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2e, 0x31
2018-02-18 17:40:32.734 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x2f, 0xce
2018-02-18 17:40:32.734 Detail,
2018-02-18 17:40:32.734 Info, Node004, Sending (Send) message (Callback ID=0x2e, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2e, 0x31
2018-02-18 17:40:33.735 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-18 17:40:33.735 Detail, Node004, Removing current message
2018-02-18 17:40:33.735 Detail, Node004, Notification: Notification - TimeOut
2018-02-18 17:40:33.735 Detail,
2018-02-18 17:40:33.735 Info, Node004, Sending (Send) message (Callback ID=0x2f, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0x2f, 0xce
2018-02-18 17:40:34.736 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-18 17:40:34.736 Detail, Node004, Removing current message
2018-02-18 17:40:34.736 Detail, Node004, Notification: Notification - TimeOut
2

Do you only have one of these Cooper devices that has the issue or do all the Cooper devices have this issue?

3

All devices on this network seem to have the issue. The log Node004 is actually the ZWP-WS-100 switch. I thought it might be the cooper devices having issues because when I set them up for polling they would only poll once successfully. After that they would start failing with the Error “ERROR: Dropping command, expected response not received after 1 attempt(s)” repeatedly". I have since turned polling off for all three devices.

4

What’s your controller? Some USB z-wave stick? Maybe it’s not receiving info. Might have a defective device. It’s suspect that all devices regardless of brand are behaving this way.

5

It’s an Aeotec z-stick gen5. I agree it does seem to point to the controller not being able to receive the status. It’s odd though because if the controller/Z-Wave network is restarted all seems well in the logs at the start.

6

Not sure, I have that z-stick and everything works fine. I don’t have any devices from those manufacturers though. I have GE, Nexia, and Aeotec devices.

7

Resolved: I reinstalled VMWARE ESXI on the host and everything seems to be working now.