Decided to upgrade to 7.1 from the 6.1 I restored to. This time it worked. I wonder if there was an interaction between the two updates I installed back to back.
1 Like
I’m running HA on a virtual machine, and when the update broke I would try it again, I thought that the fourth time worked but it stopped 10 minutes later. So I am still having the issue as well.
Installing the 6.1 backup and then restarting and then upgrading to the 7.1 seems to fix it for me once and for all
Keep me posted, because I had the same issue (upgrade from 0.6.2 to 0.7.1), just after upgrade all good, but all devices and entities became unavailable after 12 hours. I had to downgrade to 0.6.2.
1 Like
Nope, hours later, one device dropped and I imagine more would too as before. Back to 6.1
1 Like
Zhis is a Z-Wave JS issue, not a NodeRed issue. I think this should be merged with this other thread:
@Buenavista I’m pretty confident that i did call it out as a “z-wave” issue and not an explicit NodeRed issue… Read the original post. I included a link to the GitHub issue that I created against the z-wave add-on in that first post.
That´s great. Not here to fight. It´s just that the head lines says the update has broken NodeRed…
I just now looked at Github as I did not have time before. There had already been active an issue reported here:
Not sure where this is correct but as I said, this one is quite active.
1 Like
It broke my Honeywell T6 communications. Both thermostats went unavailable.
Reverted to backup version and all works now.
Running HA and HA OS on a VM … all are latest version.
Edit… my working (reverted) zwave version is 0.6.2 and everything’s back to normal
so today I updated to HA OS 13.1 with the scenario above (0.6.2 - 0.7.0 - 0.7.1- unavailable -back to 0.6.2 and final update to 0.7.1 working). see Update to z-wave js 0.7.1 seems to have broken NodeRed - #4 by Mariusthvdb
OS 13.1 update went fine, and very quick indeed. Only to see all Z-Wave devices went unavailable once again… reload add-on didnt help, nor did reloading integration, not even the HA reboot.
had to downgrade to 0.6.2 backup, and devices are back.
dare I try updating to 0.7.1 once again… ??
It appears that the team has fixed the issue in HA core and also bumped the add on version to pick up the fix. I’m away from my instance; has anyone applied z-wave js 0.7.2 yet and can you confirm that the issue is resolved? Z-wave not responsing after update of today ! · Issue #125843 · home-assistant/core · GitHub
can confirm that I see all of my devices after updating to 0.7.2 add-on.
integration was no yet updated,
1 Like
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.