Can someone please clarify, is there still an issue after upgrading to Z-Wave JS v2.0.1 (I’m on 1.16.0 currently) ?
Thanks.
2 Likes
Where did you find 2.0.1 ? latest i can find on addons is 0.1.93
Depending on if you use the official or UI addon, you’ll see different:
I have both installed but one disabled.
1 Like
Which one are you actively using? This has the potential of creating a broken configuration. Your original post seems to indicate ZUI, which would be fine, but then what purpose is there for having Z-Wave JS add-on installed in that case?
1 Like
I am also waiting on upgrading to see if there are still issues after upgrading to HA v2023.9.3 & Zwave JS UI v2.0.1 (currently on 1.15.11). Can anyone confirm?
I’m using JSUI and the other add-on is completely stopped and disabled from startup. I only recently moved from JS and migrated over.
Original JS isn’t removed yet as I migrated primarily for nvm backup, having used the original add-on for years. I didn’t want to delete the old config straight away to find any surprises i wish i hadn’t migrated for.
so JS shows up in the updates list as well for now. 
(edit: everything is running perfectly as is. Issues only started to appear like they did with everyone else after recent updates)
There are still issues on z-wave JS UI v2.0.1 for me
2 Likes
I gave up, i had one dead /ghost node that refused to be removed no matter what i tried.
So what i did was reset the enire Uzb1 usb controller and spent the last hours readding everything.
As long as you have 1 dead/unknown/ghost node none of the above mentioned suggestions will work.
If you have jus 1 bad node the zwave js or zwave js ui will try to reset the controller and it will fail over and over.
So clean slate now running zwave js UI everything works.
Hope no nodes dies ten i guess it will crash again.
Thats my exact concern too. This dead node being related to constant crashes has been mentioned more than once by different people.
Do you have any debug driver logs that demonstrate this? This is not my observation, a dead node is simply detected as dead and the controller is not restarted. Maybe there is more to it than that.
I don’t have logs yet (when i have time to deal with fallout of upgrade again i’ll be sure to get them), but in one example of logs earlier, reactions to dead nodes (or lack of ACK relating to them) have caused the driver restarts:
Comment directly below that stated that removing the dead node stopped it happening. Does seem somethings happening with dead nodes or how they are being handled
The logs looks the same as most already posted.
I did a test before I did a complete reset.
I installed a complete fresh HA on another rpi4 moved usb only installed zwave nothing else, added the old keys it just kept crashing.
As soon as the network with the dead node was removed everything works.
Seems like a lot of people who have had this issue who either got lucky and could remove the dead node or like me that did a complete reset the issue got resolved.
So I feel pretty comfortable with pointing to that as the crash reason.
Ok. It may be the case that removing these dead nodes solves the problem in certain cases, but it’s also true that having a dead node doesn’t mean you will hit the problem either (proof is myself, a dead node does not reset the controller). Could also be a 500 vs 700 series issue, as I have a 700.
If I were in this position and had access to a Windows PC, I would try using PC Controller to remove the dead nodes first, instead of rebuilding the entire network. Or just rollback to a previous version of the add-on that is not affected. These new add-on versions aren’t required until HA 2023.10, so there’s no reason to stay in them if they’re causing this much trouble.
1 Like
Still having issues using Z-Wave JS (ZJS) 1.93. I had to revert to HA 2023.8.x and ZJS 1.87.
I read on one of the GitHub threads that ZJS 1.9 wasn’t supported on HA 2023.8. Either way, ZJS keeps losing connection to the controller.
My Setup:
Here are my troubleshooting steps:
- Restore to HA Core 2023.8.2 – confirm working, leave for 24+ hours
- Update ZJS to 1.93 – Controller soft reset attempt fails
- Reboot entire server just to make sure there’s nothing that needs to be cleared out
- Restore to #1, confirm working.
- Update HA Core to 2023.9.3 – Controller soft reset attempt fails (logs attached)
– Note that HA Core 2023.9.3 Installs ZHA v1.93. I read on one of the GitHub issue threads that ZHA 1.8x isn’t compatible with HA 2023.9.x - Restore to #1, confirm working.
- Switch to ZWave UI v2.0.1, disable Soft Reset in UI, still fails (logs attached)
What started this whole debacle instead of just leaving the restore well enough alone was that I needed to set associations between devices, thanks to a whole slew of new Inovelli dimmers and a plethora of 3-way switches (previous owner was an electrician…) 
What I finally ended up doing is installing ZWave JS UI v1.16.0:
I forked the add-on repo from the official one and set the version I wanted so I could downgrade (v1.16.0). NOW, I can upgrade HA to the latest until this gets fixed for good.
After figuring out how to downgrade, I followed the excellent guide to switch from Z-Wave JS to Z-Wave JS UI by @freshcoast for the rest. The only thing that is different is the add-on identifier in Step 9, which should be the same if you use my repo:
ws://ed7eb4c2-zwavejs2mqtt:3000
You could be right on the 500 vs 700 dead node statement. I’m using a 500 controller now (downgraded from 700, as the not really dead nodes that kept occurring daily on the 700 despite latest firmware was driving me mad, and kept breaking heating automations which have to work all the time. Network has been perfectly stable ever since)
So when 2023.10 is out will this help the situation and we can upgrade safely to JS UI V2.0.1 ?
1 Like
No, HA versions have nothing to do with the problems expressed here. If you upgrade to HA 2023.10 you will be forced to upgrade your add-on.
Given that @freshcoast, right now it looks like the best preventative is what? Being On a 700 series coordinator or turning off soft reset on a 500?
Ive got this update on hold because the thought of reconnecting 80 devices on ladders is not exactly thrilling. But I also have been waiting on something in 2023.10 to fix something else.
I’m confused then, there seems to be a big problem with JS UI V2.0.1 where you can lose access to all your devices and HA 2023.10 will require it…
So what do we do? Is someone working on a fix, does an issue need to be raised, logs provided somewhere?