Z-wave config died after migration to SSD

I just migrated my working system over to SSD via a backup/restore operation. After the migration I noticed that my Add Ons and my Z-Wave devices were not functioning. I posted here about that and got some great help to get my Add Ons going again, and right after the Add Ons started working, my Z-Wave devices came back online and I was able to control them. However, about 2 hours later, for some reason all my Z-Wave devices went to status Unknown, then status Dead and none of them are working. I may be able to just remove then re-add them again, but there are a good number of them, so I’d rather fix the problem if I can. I’m still new with Z-Wave so I’m looking for where to start troubleshooting for this. I’ve been in IT for over 30 years, but I’m not a programmer LOL. I’m familiar with the concepts but just need some help tracking down my problem. Any help would be appreciated.

Thank you,

The zwavel Ui could help you see if the network is up. Else, just a restart of your add-on and check the add-on logs

1 Like

what addon are you using? have you set it up for debug logging? if so what’s the log say?

What hardware are you using? What is your OS/VM setup? Is your ZWave device connected with USB? If so, are you using an extension cord to prevent USB3 interference?

Thank you for all the questions. First, I have heard a lot about the UI, but I’m not sure if I have found it yet. If you could remind me where that UI is located that would be great. I found one time a place where I was able to see a “map” of my Z-Wave devices, but I can’t find that anymore. If I go to the Integration, I found the place where I can add and remove devices and “heal” the network. I tried the “heal” option and it got part way through the process and just stopped. I let it go all night but it never finished. After posting my question, I dd find a log and it appears that only 4 of my 14 devices stopped working. Not all 14. I will post the log I found.
I’m using a Zooz USB stick. I am not using an extension cord, but I am using one of those cases that looks like a vintage Nintendo game console and the USB ports are on short cords that connect to the back of the Raspberry Pi inside the case, so that may count as an extension cord. I’m using a Raspberry Pi 4 8GB with the Home Assistant OS. Everything is up to date as I thought maybe installing an update might fix my problem. I don’t think the Z-Wave is set up for debug logging, so I will turn that on and reboot everything. I’ve restarted the Z-Wave.JS Add On several times and also rebooted the computer. I apologize for my ignorance, but for the most part I’ve been using this setup for a couple years and it just works! I have never had to troubleshoot a problem with it until this SSD conversion. Thank you for all the responses!

I tried to attach the diagnostic info I was able to download, but the system told me it was too big.
Here is the logging I found for the Z-Wave JS Add On.

2022-12-28T14:07:09.816Z CNTRLR   [Node 011] The node is dead.
2022-12-28T14:07:09.829Z CNTRLR   [Node 011] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:07:24.829Z CNTRLR   [Node 014] The node did not respond after 1 attempts, it is presumed dead
2022-12-28T14:07:24.830Z CNTRLR   [Node 014] The node is dead.
2022-12-28T14:07:24.848Z CNTRLR   [Node 014] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:07:34.360Z CNTRLR   [Node 015] The node did not respond after 1 attempts, it is presumed dead
2022-12-28T14:07:34.361Z CNTRLR   [Node 015] The node is dead.
2022-12-28T14:07:34.375Z CNTRLR   [Node 015] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:07:34.382Z CNTRLR » [Node 015] querying node info...
2022-12-28T14:07:34.384Z CNTRLR » [Node 015] pinging the node...
2022-12-28T14:07:43.475Z CNTRLR   [Node 016] The node did not respond after 1 attempts, it is presumed dead
2022-12-28T14:07:43.477Z CNTRLR   [Node 016] The node is dead.
2022-12-28T14:07:43.493Z CNTRLR   [Node 016] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:08:00.109Z CNTRLR   [Node 017] The node did not respond after 1 attempts, it is presumed dead
2022-12-28T14:08:00.111Z CNTRLR   [Node 017] The node is dead.
2022-12-28T14:08:00.130Z CNTRLR   [Node 017] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:08:13.472Z CNTRLR   [Node 018] The node did not respond after 1 attempts, it is presumed dead
2022-12-28T14:08:13.474Z CNTRLR   [Node 018] The node is dead.
2022-12-28T14:08:13.475Z CNTRLR   All nodes are ready to be used
2022-12-28T14:08:13.507Z CNTRLR   [Node 018] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:08:23.136Z CNTRLR   [Node 015] The node did not respond after 1 attempts, it is presumed dead
2022-12-28T14:08:23.142Z CNTRLR   [Node 015] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-12-28T14:08:23.143Z CNTRLR   [Node 015] Interview attempt (1/5) failed, node is dead.
2022-12-28T17:25:14.194Z CNTRLR « [Node 013] received wakeup notification
2022-12-28T17:25:14.200Z CNTRLR   [Node 013] The node is now awake.
2022-12-28T17:25:15.205Z CNTRLR » [Node 013] Sending node back to sleep...
2022-12-28T17:25:15.278Z CNTRLR   [Node 013] The node is now asleep.
2022-12-28T21:26:28.007Z CNTRLR « [Node 013] received wakeup notification
2022-12-28T21:26:28.011Z CNTRLR   [Node 013] The node is now awake.
2022-12-28T21:26:28.053Z CNTRLR « [Node 013] received wakeup notification
2022-12-28T21:26:29.056Z CNTRLR » [Node 013] Sending node back to sleep...
2022-12-28T21:26:29.097Z CNTRLR   [Node 013] The node is now asleep.
2022-12-28T21:27:01.735Z CNTRLR « [Node 013] received wakeup notification
2022-12-28T21:27:01.737Z CNTRLR   [Node 013] The node is now awake.
2022-12-28T21:27:02.741Z CNTRLR » [Node 013] Sending node back to sleep...
2022-12-28T21:27:02.801Z CNTRLR   [Node 013] The node is now asleep.
2022-12-28T21:27:46.053Z CNTRLR « [Node 013] received wakeup notification
2022-12-28T21:27:46.054Z CNTRLR   [Node 013] The node is now awake.
2022-12-28T21:27:47.059Z CNTRLR » [Node 013] Sending node back to sleep...
2022-12-28T21:27:47.104Z CNTRLR   [Node 013] The node is now asleep.
2022-12-28T21:27:49.819Z CNTRLR « [Node 013] received wakeup notification
2022-12-28T21:27:49.821Z CNTRLR   [Node 013] The node is now awake.
2022-12-28T21:27:50.824Z CNTRLR » [Node 013] Sending node back to sleep...
2022-12-28T21:27:50.857Z CNTRLR   [Node 013] The node is now asleep.
2022-12-29T01:35:00.352Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T01:35:00.353Z CNTRLR   [Node 013] The node is now awake.
2022-12-29T01:35:19.473Z CNTRLR   [Node 013] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-12-29T01:35:36.993Z CNTRLR   [Node 013] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-12-29T01:35:53.506Z CNTRLR   [Node 013] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2022-12-29T01:35:53.507Z CNTRLR   [Node 013] The node is now asleep.
2022-12-29T05:36:05.162Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T05:36:05.164Z CNTRLR   [Node 013] The node is now awake.
2022-12-29T05:36:05.224Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T05:36:23.170Z CNTRLR   [Node 013] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-12-29T05:36:34.684Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T05:36:40.700Z CNTRLR   [Node 013] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-12-29T05:36:58.231Z CNTRLR   [Node 013] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2022-12-29T05:36:58.233Z CNTRLR   [Node 013] The node is now asleep.
2022-12-29T05:37:23.077Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T05:37:23.079Z CNTRLR   [Node 013] The node is now awake.
2022-12-29T05:37:41.069Z CNTRLR   [Node 013] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-12-29T05:37:58.591Z CNTRLR   [Node 013] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-12-29T05:38:15.104Z CNTRLR   [Node 013] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2022-12-29T05:38:15.105Z CNTRLR   [Node 013] The node is now asleep.
2022-12-29T09:38:28.244Z CNTRLR « [Node 013] TODO: no handler for application command
2022-12-29T09:38:54.963Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T09:38:54.965Z CNTRLR   [Node 013] The node is now awake.
2022-12-29T09:39:13.980Z CNTRLR   [Node 013] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-12-29T09:39:31.497Z CNTRLR   [Node 013] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-12-29T09:39:46.488Z CNTRLR « [Node 013] received wakeup notification
2022-12-29T09:39:48.010Z CNTRLR   [Node 013] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2022-12-29T09:39:48.012Z CNTRLR   [Node 013] The node is now asleep.
Starting logging event forwarder at info level
Stopping logging event forwarder
Starting logging event forwarder at error level
Stopping logging event forwarder
Starting logging event forwarder at warn level
Stopping logging event forwarder
Starting logging event forwarder at verbose level
Stopping logging event forwarder
Starting logging event forwarder at verbose level
Stopping logging event forwarder
New client
Client disconnected
Code 1000: 
Starting logging event forwarder at verbose level
Stopping logging event forwarder
Starting logging event forwarder at error level
Stopping logging event forwarder

if the 4 devices are mobile, try to move them near to the controller and heal the node one by one. if not, try the controller to be mobile and move it to the nodes.
If either don’t help, a factory reset of your nodes and re adding them could be of help. Advisable to have node and controller near to each other in this scenario too.

You should not have to exclude devices to get it to work,

I’d try the USB extension cable,3’
I’d verify you have the USB path set correctly in zwavejs
I’d power cycle the entire box
Try to capture the start of the zwavejs debug log, so we can see what it does as it starts up.

Thank you all for your responses. I appreciate your time and willingness to help! After doing some research, I have figured out that my Z-Wave stick is a series 500 chip, not a series 700 which has more features and much longer range. I think that what I’m going to do is to purchase a new Z-Wave stick, and basically start over from scratch on my Z-Wave config by resetting all my devices and re-including them and by setting up with the Z-Wave UI Add on instead of the basic add on that I’ve been using now for a year or more. I didn’t realize that there was an add on that had a full UI that I can use to configure my Z-wave network. I think this is the best way to go so that I’ll have all the newest and best building blocks for the best Z-Wave network. Hopefully, I can get through this re-config without too much trouble. Thank you again.