I did run into problems with this Zwave bug also, needed 4 days to fix it. As I had to restore a 9 GB backup multiple time’s, which takes hours.
Well, I used this situation also simultaneously to make the switch from HA Supervised to HAOS, because the devs completely destroyed everything, that has made Supervised the best version, we had.
I’m running Zwave with the Zwave.me 500gen stick. ZwaveJS addon and ZwaveJS integration.
After trying out all the possible combi’s of updates of HA Core, Zwave JS and all kinds of resets (HA restart, system restart, unplugging the USB stick and so on, after days of swetting here in the midnight hours and shortage on sleep, it looks, I have it back to stable.
Things, I did found out here on the forums and by trial and error finally got me there, I hope. It runs now for 2 days fine.
I never had issues with dead nodes, never ever. That may be the Zwave.me stick, I never heard of people with this stick having dead nodes. Allmost all this issues affect people with Aeotec sticks. So, even without dead nodes Zwave did fall down here.
If you have a 9GB backup, that could be the recorder data. I skipped the mariaDB plugin when doing restores and selected everything else (individual zwave plugin restores didnt fix the issues, and caused more).
Skipping that large database (but only 1.3GB in my case) made the restore much quicker.
I don’t have the ability to release ZUI itself, just the addon. I did submit a PR to bump the version in the official addon as well as in the ZUI repo - that will need to get merged, then released, then we can update the addon
Somehow the zwave addon got set to not start at boot. I did not change this, but once I started the addon and re-set the option to start at boot - everything seems fine.
The exact same thing happened to me.
I really wish the addons and integrations pages were one tap away from each other, like tabs on a page or something.
Exact same here.
It took me a while to recognize that the zwave JS was disabled (and still is on boot - never changed that).
So no backup restore was needed in my case (fortunately).
I am on:
HAOS
Home Assistant 2023.10.0
Supervisor 2023.10.0
Operating System 10.5
Frontend 20231002.0 - latest
Z-Wave JS Current version: 0.1.94
“driverVersion”: “12.0.2”,
“serverVersion”: “1.32.1”,
Aeotec Z-Stick Gen5
I am still unclear about how to set the soft-reset option.
Any suggestion? What is it good for vs. Ping?
Alright.
Actually I knew where to find it. but to raise another question:
What kind of config requires (or benefits) from this to be ON?
I am using:
Home Assistant 2023.10.1
Supervisor 2023.10.0
Operating System 10.5
Frontend 20231005.0 - latest
with
ZWAVE JS 0.1.96
"driverVersion": "12.0.3",
"serverVersion": "1.32.1",
Aeotec Z-Stick Gen5+
plus 51 devices from Aeotec, Fibaro, Danalock, Ring
Basically I am happy about the stablilty.
Every now and then the lock (on the garden shed) loses connection, but this is repaired by an automated Ping.
But, maybe soft-reset was also working in the background in the past and I did not recognize.
Anyway, I will disable it for testing and see what happens.
