a news - there is obviously a first fix - but I haven’t tried it yet
I’ve had a few rough updates with zwave js over teh past few releases and decided to hold off on this one. I’m now seeing theres a new update. Has anyone tested this to see if it fixes some of teh issues from the 4.0 upgrade?
I got a generic miniPC with Z.me uzb z-wave controller. Updating JS UI to 4.0 and then 4.0.1 caused all devices to go unavailable. Restoring to previous version (3.24) didn’t help either. Neither did rebooting the host computer.
The JS UI logs seemed to be flooded by thermostats shouting temperature changes… so I tried unplugging and replugging the z-wave controller from the PC. It seems to have helped, the devices are now available and responding again. Running on 3.24 … will now probably hold off from the updates until further notice 
1 Like
No, the v4.0.1 update does not address anything that was introduced in v4.0.0 (for the add-on).
1 Like
No - after what @slayeri reported, I’ll hold it back for now.
I also don’t think the responsible developers responded so quickly to the negative feedback on the 4.0.0 update.
Z-Wave JS UI 4.0.2 just released which contains driver v15.0.3 if someone wants to try it…
Bit the bullet and tried it, device interview takes a lot longer than it used to but at least doesn’t report a failure - however, it doesn’t pick up all entities for me, multiple interviews are still required 
1 Like
4.0.2 Didn’t fix anything for me…
It auto-updated overnight and when I woke up all my zwave devices were “unknown”. I rolled back to 3.4.2 and they came back.
Same for me but unsure how to roll back, was hoping to see a reinstall option
You need a backup of version z-wave js ui 3.24.0
It looks like the issue has been resolved - at least for me and my HA green. Details can be found in an issue on github.com:
is this just an add-on problem or an issue with the underlying zwavejs functionality? I run the server in plain docker and would like to know if updating that (if I ever do) is going to break anything.
The apparent fix is in zwave-js (not the add-on).
1 Like
The implication from previous posts was that it’s an issue with the underlying zwave driver and driver version v15.0.3 fixed it but based on feedback in this thread that doesn’t seem to be the fix as this driver is included in Z-Wave JS UI 4.0.2 but did not resolve people’s problems.
2 Likes
The problem persists.
But it hasn’t been.
Pretty sure it has been fixed though…
I had this issue when it happened, and zwave has been working fine ever since the fixes above went in.
Obviously, I can’t speak for others, but if this was still broken, there would be a lot of people upset… and other than you, this thread has been quiet for months.
I suspect there may be an unrelated second issue for your setup. Dunno… just a guess.
I have another friend experiencing the same issue.
My setup is simply the HA container in Proxmox on a Mini PC with a Zooz 7 stick. Worked flawlessly until the above issues started. Now it can’t go 24 hours (last night it was almost every hour it was failing).
Soft reset is and has been off (I noted that in earlier responses when folks were yelling “TURN IT OFF”. Reading the docs on the app it states that’s for C5 and earlier. I’m running a C7.
I’ll turn it back on and see what happens.