I moved to ZWaveJS on the 3rd and did the firmware update. Shut down the hub, removed power, powered back up. Went through and woke up the battery devices until everything seemed to be connected.
Since then, I am having some refresh issues, mostly with my Kwikset deadbolts. Manual locks, unlocks as well as commands from the hub are VERY delayed or missing. If several are in the same timeframe, then it seems like the entire ZWave network bogs down for a while.
I installed 2.4.1.154 with the reboot last night. This morning when every thing was sluggish I did a power down, remove power, power back up. Watching the ZWave logs when it came back up and there were a lot of "route failed" & "[Node XXX] ping failed: The node did not acknowledge the command (ZW0204)" & "Dropping message with invalid payload" messages. I saved the log file, is there a way to upload that here where it would be useful?
I gave it some time to settle down and then did a refresh statistics on the ZWave details page. Let that run for a bit and then refreshed the page. Every device shows 0 neighbors, even with populated routes. I used the re-interview command on three of my locks and then they showed neighbors:
Are the devices working? That is the important question. Some people have had the neighbor info missing but devices still worked fine.
For your logs you saved, you could post it to pastebin.com and share a link if you want. Not sure if they will be useful or not.
If you are having issues with devices not working, I would just switch back to legacy ZIP. It should go back to mostly working how it was before. Some devices may need to discover neighbors again or re-route but just be patient when switching back.
If staff engages here to work on a solution you can always switch back to JS again for further troubleshooting if needed.
Probably a coincidence, I don't think Z-wave has been touched much since the initial 2.4.1 release. Maybe one other patch right away and that's been it.
After all latest upgrades I still have 3 devices with no neighbors and no route. They are working perfectly fine. After hub reboot about half of devices showing no neighbors and no rout but sure, they are working.
Yeah, "Jammed" is still an issue in the V7.22 SiLabs firmware for the 800 series chip (C8 & C8Pro) - This is supposedly fixed in V7.23 - See ID# 1363434 in their release notes - V7.22 much improved things (fixed a bunch of race conditions in the TX queing on the radio) which is why HE issued the FW update opion with the new ZWaveJS framework. I believe V7.23 is supposed to finally fix the last edge cases. - I'm not sure if ZWaveJS is still doing testing on V7.23, or if HE is testing this latest firware
But bottom line, this is a radio FW issue, and I don't think there is much that HE can directly do about it.
It's a question of which bugs are less painful, the Z/IP gateway issues (which aren't getting any more real efforts for SiLabs,) or the newer V7.2x issues with ZWaveJS. - If these issues are hugely problematic for you, then my initial suggestion would be try flip back to ZIP and see if that's a more "liveable" set of problems for your mesh.
This is very informative, thank you. Now can we please pass an international law to ban Z-Wave and have the SiLabs team sent out to become farmers or something where they can't do as much damage? I have so much pent up frustration over Z-wave!!
Despite the positive comments, at the end of the long thread above, there still hasn't been an "official recommendation" by ZwaveJS to move to that version (an earlier version of V7.23 apparently had a NVM backup bug, which has been recently fixed) - The VERY latest SI stuff was released on 4/1/25 - And you can read the release notes for V7.23.2 (current release). HE usually stays 6-12 months behind SI releases, and usually doesn't force an firmware update without some compelling reason, but the move to V7.22 was triggered during the HE V2.4.1.x beta, as "Jammed" was an even bigger issue in the early releases of HE using ZwaveJS, moving to V7.22 definitely is better than where things started during the beta - For the latest, read https://www.silabs.com/documents/public/release-notes/SRN14930-7.23.2.0.pdf (7.23.2 also added European LR support, but that doesn't as important as not have the network stack fail and reset.)
Your guess is as good as mine, as to when SI gets all this a bit more stable, and then HE takes another plunge with a 800 series radio FW update. - Hopefully, in a few months, not a few years. - You can also roll back to Z/IP which just seemed to have significant NVM backup issues (cloud backup in the land of HE), which are likely never going to be fixed.
Thank you for the links! You’ve confirmed what I had suspected. It’s a shame that great companies like Hubitat, Zooz, etc have to face dissatisfaction from customers when it isn’t even within their control to fix the trash that comes out of Silicon Labs. Just terrible. I’m happy to be on a particular firmware that finally has my zwave network playing nicely for the first time ever. I will probably just stop updating unless SILabs gets their act together one day with zwave. They have caused me great frustration for years.
