Z-wave issues after update to 105.5

Configuration Z-Wave
1

After updating to 105.5, all of my z-wave devices were unavailable. As suggested in another thread, I restored to a previous snapshot, deleted zwcfg_0xe9973468.xml, and then upgraded. Now my devices show up in lovelace, but take forever to respond if at all. I’m running on a raspberry pi 4, aeotek stick through a usb 2.0 hub. Please help. I have about 30 nodes.

Here is [some of] the log:

2020-02-23 17:47:21.756 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-23 17:47:21.756 Detail, Node004, Removing current message
2020-02-23 17:47:21.756 Detail, Node004, Notification: Notification - TimeOut
2020-02-23 17:47:21.760 Detail,
2020-02-23 17:47:21.760 Info, Node005, Sending (NoOp) message (Callback ID=0x0d, Expected Reply=0x13) - NoOperation_Set (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x00, 0x00, 0x25, 0x0d, 0xca
2020-02-23 17:47:22.760 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-23 17:47:22.761 Detail, Node005, Removing current message
2020-02-23 17:47:22.761 Detail, Node005, Notification: Notification - TimeOut
2020-02-23 17:47:22.766 Detail,
2020-02-23 17:47:22.768 Info, Node007, Sending (NoOp) message (Callback ID=0x0e, Expected Reply=0x13) - NoOperation_Set (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x00, 0x00, 0x25, 0x0e, 0xcb
2020-02-23 17:47:23.769 Error, Node007, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-23 17:47:23.769 Detail, Node007, Removing current message
2020-02-23 17:47:23.769 Detail, Node007, Notification: Notification - TimeOut
2020-02-23 17:47:23.772 Detail,
2020-02-23 17:47:23.772 Info, Node008, Sending (NoOp) message (Callback ID=0x0f, Expected Reply=0x13) - NoOperation_Set (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x00, 0x00, 0x25, 0x0f, 0xc5
2020-02-23 17:47:24.772 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-23 17:47:24.772 Detail, Node008, Removing current message
2020-02-23 17:47:24.772 Detail, Node008, Notification: Notification - TimeOut
2020-02-23 17:47:24.775 Detail,
2020-02-23 17:47:24.775 Info, Node009, Sending (NoOp) message (Callback ID=0x10, Expected Reply=0x13) - NoOperation_Set (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x00, 0x00, 0x25, 0x10, 0xdb
2020-02-23 17:47:25.776 Error, Node009, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-23 17:47:25.776 Detail, Node009, Removing current message
2020-02-23 17:47:25.776 Detail, Node009, Notification: Notification - TimeOut
2

I had this issue as well. Either all or large numbers of wave entities were unavailable. Many of them reverted back to manufacturer names rather than the custom names I had given them. I rolled back to a snapshot in the 103 release series and the problem went away. Not a fox, of course, but wanted to make sure that people saw the issue wasn’t just yours.

1 Like
3

Turns out my issue was due to remodeling my kitchen. I removed 2 z-wave switches without removing them from the network. I just assumed i could pull them and the network would rebuild itself. Caused odd behavior especially when trying to access certain nodes that were through those removed switches.

I powered up the switches, removed them via the Z-Wave UI, healed network, all good again.