I can now also confirm that updating the z-wave JS add on to 0.7.2 has resolved my issue.
I also had the issue with 0.7.0/0.7.1, however, my devices are still showing inoperable after updating to 0.7.2. I updated HA Core to 2024.9.2 yesterday and 0.7.2 this evening. All my network keys appear to be intact, so I’m not sure what to try next.
I also restored 0.6.0/0.6.1/0.6.2 a few times whilst troubleshooting before updating to 2024.9.2.
@DTaxx after updating z-wave js to 0.7.2, I also restarted Home Assistant. I didn’t reboot the host system; just restarted HA. I apologize for omitting that detail in the earlier post.
Have to report the update to 0.7.2 wasn’t completely successful after all
All of my Sensative Door strips remained unavailable.
Downgraded to 0.6.2 once again
I have seen all the above and thought all was fixed in 0.7.2. However, when I attempted to activate the kitchen light via a Zooz zen32 button and a very complicated Node-Red automation involving press and hold to dim-brighten etc. the light immediately went back off. After watching the Zwave events it seems that after the 0.7.2 update the Zen 32 is sending two of the same command for a single push causing the “toggle” call to be issued twice. Therefore the light goes on then off with a single press. Watched other (not Zooz) Zwave switches and do not see double commands. Rolled ZwaveJs back to 0.6.2 all cured. Is anyone else seeing similar behavior?
So I have tried multiple times to roll back both the JS add on and the core in hopes of finding a path back to functionality. However all attempts come up empty handed. I am currently rolled back to 0.6.2 and while most of my devices are no longer greyed out on my dashboards, when I use the toggle to turn something on, it thinks for a second then I get this error “
Failed to perform the action light/turn_on. unknown error”. This leaves me with nowhere to go since I thought a roll back would solve this…
Is this resolved for people with the récents updates? I still haven’t updated Node Red to 18.x
@Brounoh as pointed out a couple of times in the thread, the issue was never with NodeRed but rather with the Z-Wave JS add-on / integration. I won’t be the one to tell you it’s “safe” to update NodeRed, but NodeRed itself was never the cause of the issue for this particular topic.
Hi, that’s not really what I am experiencing.
I had Z-Wave JS UI 3.11 or 3.12 I believe, as soon as I updated to Node Red 18.x from 17.last, issue started.
I went back to Node Red 17.last and everything has been back to normal.
Then, I have been updating Z-Wave JS UI 3.11 or 3.12 incrementally to 3.13.2 and everything has been fine.
So, without any coding understanding of all the issues behind, when I update Z-Wave JS UI,⁹ everything keeps working. When I try to update Node Red to the latest 18.x, things started to break.
So based on these simple facts, I am thinking my issue is Node Red not Z-Wave JS UI.