After every Z-wave update all my devices show as unavailable. I can fix it by re-interviewing them all one by one, but it’s not ideal and doesn’t seem normal. Also reverting to recent addon backup doesn’t fix it.
I’m using a Zooz ZST39 controller on a home assistant yellow. I set up all this just a few weeks ago, so I’m pretty new to this.
Thoughts?
Hi Richard, assume you’re using ZW JS UI – having the same problem. Was your install a fresh/new ZWave network or did you migrate with the ZW39 using it as a secondary controller as I did?
I’m using plain Z-wave JS. I tried UI and had to re-interview despite carefully following instructions for avoiding that problem. Restored plain JS in part hoping that would fix it but of course it didn’t.
I never used the Zooz stick as a secondary controller on Home Assistant. But I did migrate from Homey Bridge, which has Z-Wave built in. When I set up the Yellow and the Zooz stick, it could see the old nodes as I excluded them from Homey and included them on HA one by one. Does that count as a fresh install?
I’m hoping I don’t have to start over. I’ve got about thirty Leviton and Zooz dimmers and would have to either switch to unsecured or remove wall plates to get all the PINs or QR codes. (I’ve got a lot recorded, but not all.)
Thank you!
Yeah it’s a fresh install if you excluded a device from the old network and rediscovered into the new. And so the stick must be primary on a new home network.
I’m sticking with UI myself and still trying to figure this out. Can you check the version of firmware on the stick?
Mine shows:
FW: v1.50
SDK: v7.22.1
In my case Z-Wave JS and had a similar issue.
I was able to fix it by:
Configure Z-Wave JSAfter rebuilding network routes everything seemed to work fine.
Also 1.5.
(I don’t see the sdk info.)
Interesting. Did this shortcut re-interviewing unavailable devices? Or did it prevent devices from going unavailable on future updates?
OK - we’re both on the same version. I can’t imagine why rebuild network routes would change anything, unless the root of your issues is some problem with the mesh (which would be more of an issue controlling devices than having to re-interview them on restart).
So, update.
All my devices just spontaneously became unavailable. I pressed a few buttons on a remote (Zooz 4 button) to turn different lights on and off and it just stopped working and all devices went unavailable. (Of course this was in the middle of me demonstrating the remote to my wife.) I waited a while, restarted the add on, restarted home assistant, but no luck.
At this point I’m willing to exclude everything (33 devices) and start over if that might fix the problem.
Do I uninstall and reinstall the add-on and integration? Any other steps I need to take?
Are there any logs etc. that would be helpful for me to share?
Have you tried rebuilding routes like I suggest? That worked for me; it wasn’t a re-interview and I didn’t add or remove any devices. Just updated and rebuilt routes from settings.
I did try it when everything went unavailable again. But no luck. I’m guessing there are different issues causing similar symptoms. Some people say just pinging works, but not for me. Perhaps in those cases rebuilding the network is a quick solution?
I appreciate your suggestion and hope it helps someone else.
Hmm for your reference I’m running.
In Devices, click z-wave, configure, and there’s a Diagnostics panel. There’s a dropdown for Controller statistics. You should see high counts for Messages TX/RX and zero Dropped messages TX/RX (in my case I see 1 dropped message RX). Other than Messages and the one RX failure I see everything is zero.
What do your Controller statistics show?
Review this list
My driver and server versions are the same. My dropped TX are zero, dropped TX are 14 (versus 21k successful), and all the rest zeros.
Thanks, this is a helpful resource.
I just have the same issue. I have a HA yellow and am using the built in HA 800 Series LR GPIO Module with the plain Z-wave JS add-on. It just upgraded itself to version 0.15.0 yesterday (6/12/2025). My whole network is dead, which is SUPER frustrating. In another place I am using eisy and I NEVER EVER had that these reliability issues. I am not always home and this can’t happen if I am not home.
Since I have not found any solution, I will have to rebuild my network. ALSO, as a lesson learned, I will make sure NONE of the software on the HA will auto-update EVER.
I totally shut down HA, disconnected, restarted, etc… left overnight.
All my nodes (except the HA node) say either:
This device is currently being interviewed and may not be fully operational.
This device has been provisioned but is not yet included in the network.
Mind you that all devices worked perfectly BEFORE the upgrade.
The Log file shows this:
2025-06-12 20:41:43.404 CNTRLR [Node 002] The node did not respond after 1 attempts, it is presumed dead
2025-06-12 20:41:43.405 CNTRLR [Node 002] The node is dead.
2025-06-12 20:41:43.409 CNTRLR [Node 002] ping failed: The node did not acknowledge the command (ZW0204)
FWIW, I rebuilt the network from scratch and it’s worked like a dream since. An update has never caused a problem since. I switched from Z-wave JS plain to IU, but I don’t think that was the difference. I also switched from a USB stick to GPIO controller, but I don’t think that was the difference either.
What I think did make the difference was not setting up while another controller–a Homey bridge, as I mention above–was still online. On the first, bad setup, I could see the Homey nodes as I removed them from the Homey and added them to HA. That meant, for instance, that my HA controller was not node 1. Can’t imagine why that would matter but it was weird and in fact I had tons of problems. Now that I’ve rebuilt, the GPIO controller is node 1 and everything is neat, clean, and works.
I wish I understood technically what was going on. I don’t. But I hope that’s helpful as a data point.
Good luck!
My devices became unavailable after upgrading Z-Wave JS to 0.14. This upgrade set the region to Australia-New Zealand and my devices are for USA. Frequency is different in these regions. Changing the region to USA solved the issue.
You can change the region in: Settings | Add-ons | Z-Wave JS | Configuration | Radio frequency region.
Greetings from Uruguay
I’m having a similar issue. I upgraded from 10.2.0 to 11.4.1 and all my nodes went dead. Rebuilding the network did nothing.
Backing down the upgrade to 10.11.0 fixed the issue.
I was also using a Zooz 800 based stick with firmware 1.5, but after I got it stable, moved to the home assistant z wave antenna that was just released. I haven’t tried upgrading to 11 again.
I have had a similar issue, but the devices always seem to come back after a full reboot of the machine.