Z-wave devices suddenly not available

Hello. Fairly new to Home Assistant (had a small system running for over a year now in my boat) and decided to migrate from HomeSeer to HA. Started the HA system from scratch and added a Zigbee stick. This is working great.

On my HS system i had a UZB1 stick that was controlling some lights, sensors and thermostats. I moved this stick over to HA and managed to import all of the nodes and it has been working for about a week now. Have not added anything new lately. The UZB1 stick is connected to the RPI with a 30cm long extension cord to move it a bit up.

Yesterday i needed to try something on another system and needed the extension cord. So i plugged the UZB1 directly into the RPI on the same port. After this my devices started to show unavailable. plugged the cabel back in with the same result.

In the z-wave integration it shows that i have 18 devices and a number of devices that are not ready (lowest number i have seen is 10 not ready. Fluctuates). I have managed to control 1 light out of all the lights that i have available. And that is it.

I have checked the the Z Wave JS add-on has the correct path to the USB device. And same with the integration. I tried rolling my system back to a full backup made 24 hours before this happened. Same result. Today i tried to remove the z-wave add-on and integration and do a new install.
All 18 nodes are shown, but they are not working. 17 are showing not ready. See the pictures below. As you can see the nodes have no other info anymore than the node number!

Anyone have any idea on what to try next? Is there a chance that the UZB1 is faulty?

Only one image pr post for new members. So here is the other picture of the nodes.

You made the mistake of disconnecting it from a running system. Reboot the Pi and hopefully it can recover.

For future reference, you should have shut down the Pi before removing the cable.

I have tried to reboot many times. Even by removing the power. Same result.

I installed the UZB1 stick in my computer with the HomeSeer system still installed and here the stick workes perfectly. So there is something wrong with the HA system…

Sorry I cannot be of much help.

I assume, from the first screenshot, that you are using the zwavejs addon. Since I use the control panel from zwavejs2mqtt I cannot be of much more help.

I use the zwavejs add on yes.

Is my only option a full new installation of the system?

It’s strange that HS sees the nodes without issue, but yet a working backup of HA can’t. Are you using the same extension cord with HS as you are with HA?

HS user here also. One of the things I’ve learned in my short time with HA is IMO it’s not nearly as fault tolerant as HS. It’s quite fragile in comparison, and thus needs to be handled with more care.

Now that HS runs as a windows service, I can almost do anything to it and it will just chug along without issue. Prior to running as a service, the biggest weakness was improper shutdown could Bork the db.

On HS i am using the stick directly into the computer without any extension.

It was the same on HA without the cord so I don’t think that is the issue.

Are you using any USB3 device plugged into the Raspberry like an SSD? The extension cord was preventing signal interference in that case. Otherwise some logging would be helpful.

Only UZB1 and Conbee II.

Which log do you want to see?

So now i tried a complete new installation with a blank SD card. Only installed the Z-Wave JS add-on and integration. Same issue with nodes not starting! Below some of the log from the add-on:

2022-01-09T18:39:27.203Z CNTRLR [Node 030] Interview stage completed: ProtocolInfo
2022-01-09T18:39:27.203Z CNTRLR » [Node 030] pinging the node…
2022-01-09T18:39:27.276Z CNTRLR [Node 003] The node is alive.
2022-01-09T18:39:27.284Z CNTRLR « [Node 003] ping successful
2022-01-09T18:39:27.286Z CNTRLR » [Node 003] querying node info…
2022-01-09T18:39:27.370Z CNTRLR [Node 002] The node is alive.
2022-01-09T18:39:27.378Z CNTRLR « [Node 002] ping successful
2022-01-09T18:39:27.378Z CNTRLR » [Node 002] querying node info…
2022-01-09T18:39:31.529Z CNTRLR [Node 004] The node did not respond after 1 attempts, it is presumed dead
2022-01-09T18:39:31.531Z CNTRLR [Node 004] The node is dead.
2022-01-09T18:39:31.561Z CNTRLR [Node 004] ping failed: Failed to send the command after 1 attempts (Status No
Ack) (ZW0204)
2022-01-09T18:39:31.561Z CNTRLR » [Node 004] querying node info…
2022-01-09T18:39:31.562Z CNTRLR » [Node 004] pinging the node…
2022-01-09T18:39:31.630Z CNTRLR [Node 005] The node is alive.
2022-01-09T18:39:31.640Z CNTRLR « [Node 005] ping successful
2022-01-09T18:39:31.641Z CNTRLR » [Node 005] querying node info…
2022-01-09T18:39:33.259Z CNTRLR No response from controller after 1/3 attempts. Scheduling next try in 100 ms.
2022-01-09T18:39:34.368Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:39:36.490Z CNTRLR [Node 008] ping failed: Timeout while waiting for an ACK from the controller (
ZW0200)
2022-01-09T18:39:36.491Z CNTRLR » [Node 008] querying node info…
2022-01-09T18:39:37.506Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:39:38.613Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:39:40.739Z CNTRLR [Node 010] ping failed: Timeout while waiting for an ACK from the controller (
ZW0200)
2022-01-09T18:39:40.740Z CNTRLR » [Node 010] querying node info…
2022-01-09T18:39:41.759Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:39:42.869Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:39:43.844Z DRIVER Node 15, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
2022-01-09T18:39:43.845Z DRIVER Node 15, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
New client
Client disconnected
Code 1000:
New client
2022-01-09T18:40:49.009Z CNTRLR [Node 011] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2022-01-09T18:40:49.010Z CNTRLR » [Node 011] querying node info…
2022-01-09T18:40:50.026Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:40:51.136Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:40:52.782Z DRIVER Node 15, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
2022-01-09T18:40:52.783Z DRIVER Node 15, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
2022-01-09T18:40:52.790Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:40:52.910Z CNTRLR The controller response indicated failure after 2/3 attempts. Scheduling next
try in 1100 ms.
2022-01-09T18:40:54.052Z CNTRLR [Node 015] The node is alive.
2022-01-09T18:40:54.060Z CNTRLR « [Node 015] ping successful
2022-01-09T18:40:54.061Z CNTRLR » [Node 015] querying node info…
2022-01-09T18:40:54.104Z CNTRLR [Node 013] The node is alive.
2022-01-09T18:40:54.117Z CNTRLR « [Node 013] ping successful
2022-01-09T18:40:54.118Z CNTRLR » [Node 013] querying node info…
2022-01-09T18:41:59.192Z CNTRLR [Node 018] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2022-01-09T18:41:59.193Z CNTRLR » [Node 018] querying node info…
2022-01-09T18:42:00.204Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:42:01.314Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:42:04.446Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:42:05.555Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:42:07.683Z CNTRLR [Node 019] ping failed: Timeout while waiting for an ACK from the controller (
ZW0200)
2022-01-09T18:42:07.684Z CNTRLR » [Node 019] querying node info…
2022-01-09T18:42:08.701Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:42:09.809Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-01-09T18:42:11.930Z CNTRLR [Node 020] ping failed: Timeout while waiting for an ACK from the controller (
ZW0200)
2022-01-09T18:42:11.931Z CNTRLR » [Node 020] querying node info…
2022-01-09T18:42:12.949Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-01-09T18:42:15.162Z CNTRLR No response from controller after 2/3 attempts. Scheduling next try in 1100 ms
.
2022-01-09T18:42:16.301Z CNTRLR [Node 022] The node is alive.
2022-01-09T18:42:16.310Z CNTRLR « [Node 022] ping successful
2022-01-09T18:42:16.311Z CNTRLR » [Node 022] querying node info…
Starting logging event forwarder at info level
Stopping logging event forwarder

Have you tried the simplest option, putting back the extension cord, even if just for an hour or so? Are mains powered devices close to the controller working without issues? (To rule out a bad mesh)

The extension cord is back yes. They are far from power lines so I don’t think interference should be a problem.

I am chasing a possibility to upgrade the firmware on the uzb1 stick.

Hi @Mr_Stian , did you solve your issue?

I’m having the exact same problem.

Yesterday there was a power failure on my area, the UPS hold up as long as it should, then the server started to shutdown on low battery power, so I expected everything to be ok.

However upon power restore and HASS startup I have all wired Z-Wave devices unavailable, just as you did.

I’ve a lot of “Endpoint 1: Trying to access endpoint instance before Multi Channel interview”, “The controller response indicated failure after 2/3 attempts. Scheduling next try in 1100 ms.” and “Dropping message with invalid payload” error messages on the Z_Wave JS log.

Any feedback would be helpful.

same here, had this problem a long time

I shutdown HASS, removed the AEOTEC USB stick, started HASS, waited for it to finish booting up, shutdown again, plug the zwave stick back, startup, and voilá, everything is fine again.