I updated Z-Wave JS this morning (Sept 13, 2024 – ironically Friday the 13th) to v0.7.1 and now my NodeRed flows that make use of the zwave_js_value_notification event are not receiving the events. I do see that the logs of z-wave JS are receiving the events from the emitting devices. Unfortunately I did not make a backup of Z-Wave JS prior to applying this update; I was running v0.7.0 prior to the update and had not encountered issues with that version. Is there something that I need to update within NodeRed or do I assume that there’s an issue with Z-Wave JS 0.7.1 and hope that it gets resolved quickly? Any advice is very much appreciated.
FWIW:
NodeRed add-on version: 18.0.5
Home Assistant OS 13.1
Home Assistant Core: 2024.9.1
Home Assistant Supervisor: 2024.9.1
fwiw:
I had the same experience updating from 7.0 to 7.1. All devices/entities unavailable.
I downgraded to 6.2 (had the backup made when updating) and the was able to go straight to 7.1 again, after which all Zwave-js related devices/entities can back
I had the same experience. HAOS, ZwaveJS, both up to date three days ago.
System got unresponsive, almost dead.
I decided to do something different. As I was still planning to migrate from JS to JS UI for a long time, I got the moment and did the migration. (Yeah, don’t shoot at me now, I know, it is not recommended to migrate, when system is troubled, no one needs to teach me that).
The migration went smooth, was minutes of work.
But even after that, same problem.
I discovered by studying the behavior, that S2 authenticated wall plugs were the problem.
Re-including them without security did the trick, everything works again.
I had to, wife was already looking at me with those question marks in her eyes
Well, by this not recommended approach i did find out, that the problem exist in JS and JS UI simultaneously. The last changed thing before it went downwards was the HA core update from 2024.9.0 to 2024.9.1
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.
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.
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.
@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.
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.
