Every time I update z-wave JS, I lose nodes…healing doesn’t work, restarting the entire system doesn’t work…it’s become incredibly frustrating.
I am running HA supervised under proxmox which is very stable, except when I update z-wave JS. I believe I am running in a fully supported environment.
comments? ideas?
+1 - seeming the same.
Using Silicon_Labs_HubZ_Smart_Home_Controller_C1301210
Z-Wave JS
Current version: 0.1.58
+1. I came here looking for advice on how to fix this.
I’m using the Z-Wave JS to MQTT add-on. If I try to update from 0.37.0 to 0.39.0, my 7 door sensors do not come back up, but my 30+ other devices seem to make it through. The door sensors are battery devices, and they don’t come back even if I wake them manually, re-interview, ping, restart HA, reboot, etc. Other battery-based sensors seem OK. Are all of your nodes gone or just a subset?
I didn’t find any related issues in GitHub in either node-zwave-js or zwavejs2mqtt. I don’t have time right now to dig up the information and logs needed to file an issue, so instead I restored to an older backup. The backup restored access to those door sensors, so I’ll stick with 2022.4 HA and 0.37.0 zwave for a little while.
I have battery and hard wire with the issue. A re-interview fixes all, even battery. They loose connection randomly a few times a day
Interesting…I have the same issue when upgrading to 0.39 coming from 0.37. How could we help debug this?
I updated from 0.37 to 0.40 today, and I’m happy to report that I didn’t lose any devices this time!
I did upgrade today but still had to wakeup every node.
How do you wake up each node?
going to each battery node - and press the wakup pin - either with a needle / or opening the sensor and pressing the button. i have a mix of Neo coolcam motion sensors / door window sensors and 6 heiman smoke detectors. 23 in total.
might worth mentioning - just upgraded to 0.43 without issues. Didnt had to wake every node again - everything upgraded smoothly.
I moved from an Aeotec dongle to an S2 dongle, upgraded everything to the current version and lost all my zwave nodes. I had to wake each one up by activating it once…and one of the iintermatic wall outlets just wouldn’t be found again but I kept turning it on/off manually and after a while and many reboots, it came back to life. This is an ongoing frustration…can’t some developer resolve the loss of nodes on upgrades.
Same issue here.
Running Aeotech 5+ with firmware 1.2.
Every zwave js update drops most of my network. Heal doesn’t work, waking the node doesn’t work. Restoring to back up doesn’t work.
I have remove and rejoin each failed device.
That’s terrible. Are you running your stick on an extension cable? Do you reboot / repower your system?
Outside of an electrical issue that would be solved with an extension cable and power cycling, the only other item would be if the zwave network keys are getting lost on upgrade.
Can you find the keys in your backup and confirm they are the same after upgrade?
I’ve tried the aeotec 5 with usb 2 hub and a directly connected S2 zwave stick. I do a complete reboot of my ha nuc…power off and restart. Zwave is lost. Zwave used to work great before zwavejs an zwavejsmqtt we’re introduced.