Zwave - devices not reporting in

Configuration
1

I’m currently running HA 0.49 in an ESXI guest (debian), have a Aeotec gen 5 usb stick and a Aeotec gen 5 multi sensor. for some reason, these devices are not polling HA. In fact the only time the controller reports as sending data is when HA starts up (after this point it goes silent). According to the logs the device is asleep (and never wakes up despite the wake_up setting being 240 secs). Looking in OZWCP, it’s also reporting as being asleep there.

I then took my stick and plugged into a Virtual box (different host) guest (debian) but running HA 0.44 and the devices report in correctly.

Is this new version of HA trying to do some funny things that the old version isn’t? any ideas what’s going on?

2

Battery devices are mostly asleep but should wake up to report a change. Does it report temperature or motion? Use tail at the command line on the OZW_Log.txt file to see what zwave communication happens. You can use grep to filter just that nodeid.
tail -f OZW_Log.txt |grep Node051
Obviously the node needs to reflect your node information.

3

thanks but it’s on USB power. it reports these values when it starts up but doesn’t ever do it again. In the log:
2017-08-01 14:12:10.545 Info, Node004, Sending (WakeUp) message (Callback ID=0x2c, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x84, 0x08, 0x25, 0x2c, 0x66
2017-08-01 14:12:10.554 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-08-01 14:12:10.554 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack
2017-08-01 14:12:10.576 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0x2c, 0x00, 0x00, 0x03, 0xc4
2017-08-01 14:12:10.577 Detail, Node004, ZW_SEND_DATA Request with callback ID 0x2c received (expected 0x2c)
2017-08-01 14:12:10.577 Info, Node004, Request RTT 31 Average Request RTT 31
2017-08-01 14:12:10.577 Info, Node004, Node 4 has been marked as asleep
2017-08-01 14:12:10.577 Detail, Expected callbackId was received
2017-08-01 14:12:10.577 Detail, Expected reply was received
2017-08-01 14:12:10.577 Detail, Message transaction complete
2017-08-01 14:12:10.577 Detail,
2017-08-01 14:12:10.577 Detail, Node004, Removing current message
2017-08-01 14:12:10.577 Detail, Node004, Notification: Notification - Node Asleep
2017-08-01 14:17:35.410 Info, mgr, Refreshing node 4: COMMAND_CLASS_SENSOR_MULTILEVEL index = 3 instance = 1 (to confirm a reported change)
2017-08-01 14:17:35.410 Detail, Node004, Queuing (Send) SensorMultilevelCmd_Get (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x31, 0x04, 0x01, 0x25, 0x2d, 0xdd
2017-08-01 14:17:35.410 Detail, Node004, Queuing (Send) SensorMultilevelCmd_Get (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x31, 0x04, 0x03, 0x25, 0x2e, 0xdc
2017-08-01 14:17:35.411 Detail, Node004, Queuing (Send) SensorMultilevelCmd_Get (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x31, 0x04, 0x05, 0x25, 0x2f, 0xdb
2017-08-01 14:17:35.411 Detail,
2017-08-01 14:17:35.411 Info, Node004, Sending (Send) message (Callback ID=0x2d, Expected Reply=0x04) - SensorMultilevelCmd_Get (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x31, 0x04, 0x01, 0x25, 0x2d, 0xdd
2017-08-01 14:17:36.411 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-01 14:17:36.411 Detail, Node004, Removing current message
2017-08-01 14:17:36.411 Detail, Node004, Notification: Notification - TimeOut
2017-08-01 14:17:36.412 Detail,
2017-08-01 14:17:36.412 Info, Node004, Sending (Send) message (Callback ID=0x2e, Expected Reply=0x04) - SensorMultilevelCmd_Get (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x31, 0x04, 0x03, 0x25, 0x2e, 0xdc
2017-08-01 14:17:37.412 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-01 14:17:37.412 Detail, Node004, Removing current message
2017-08-01 14:17:37.412 Detail, Node004, Notification: Notification - TimeOut
2017-08-01 14:17:37.413 Detail,
2017-08-01 14:17:37.413 Info, Node004, Sending (Send) message (Callback ID=0x2f, Expected Reply=0x04) - SensorMultilevelCmd_Get (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x31, 0x04, 0x05, 0x25, 0x2f, 0xdb
2017-08-01 14:17:38.414 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-01 14:17:38.414 Detail, Node004, Removing current message
2017-08-01 14:17:38.414 Detail, Node004, Notification: Notification - TimeOut

4

Does it report anything to HA? Temperature, motion??? Personally, I would try removing that node and re pairing it.

Someone else in these forums @silvrr was having Zwave on ESXi issues similar to yours. Someone else in that post commented that they have experienced commented that they have seen USB passthrough drops. I just moved my install to ESXi as somewhat as a test. In my limited time, 5 days, things seem quite stable. I know there have been some USB changes in ESXi recently. How many zwave devices do you have in your setup?

5

I struggled with this for a bit, and admitted defeat. Im moved everything on to my Pi for now. I have intentions of going back to my ESXi instance but don’t have the time to right now to troubleshoot further.

6

thanks silvrr - I’ve been pulling my hair out!

So this is likely to be a ESXi issue? I am running 6.5

7

what version of ESXI are you running? which USB controller do you run?

8

Sounds familiar (exact words I used, lol)

I was on ESXi 6.5 with the Gen5 USB. @zarthan gave a lot of good options to check.

9

ESXi is very picky about hardware. You may have things work but, under any “stress” devices stop working reliably. Stress doesn’t need to mean much. I spent many years a moderator in the ESXi forums. The compatibility list was the first thing to consult if you weren’t using a fully supported hardware platform.

10

There are community submitted drivers for ESXi. I would go through the VMware forums to see what issues anyone else has with your particular platform. If there is something, you may be able to make some setting changes or see if there is a community driver that addresses the problem.

As of now I really like my HA setup on ESXi. It has only been 5 days and the Pi is still warm in the corner waiting should things change.