core: Upgrade to 2023.10.5 causes zwave to fail
The problem
After upgrade to version 2023.10.5 problem started.
The problem is exactly the same as here:
https://github.com/home-assistant/core/issues/101532
So I see this error in logs: 2023-10-23 21:32:40.918 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Z-Wave JS’ for zwave_js integration not ready yet: None; Retrying in background 2023-10-23 21:32:41.481 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data[‘options’]. Got {‘device’: ‘/dev/serial/by-id/usb-0658_0200-if00’, ‘s0_legacy_key’: ‘REMOVED’, ‘s2_access_control_key’: ‘REMOVED’, ‘s2_authenticated_key’: ‘REMOVED’, ‘s2_unauthenticated_key’: ‘REMOVED’}
I have 13 ZWave devices. None are working.
What version of Home Assistant Core has the issue?
2023-10.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
ZWave
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2023-10-23 21:32:40.918 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Z-Wave JS’ for zwave_js integration not ready yet: None; Retrying in background
2023-10-23 21:32:41.481 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data[‘options’]. Got {‘device’: ‘/dev/serial/by-id/usb-0658_0200-if00’, ‘s0_legacy_key’: ‘REMOVED’, ‘s2_access_control_key’: ‘REMOVED’, ‘s2_authenticated_key’: ‘REMOVED’, ‘s2_unauthenticated_key’: ‘REMOVED’}
Additional information
No response
About this issue
- Original URL
- State: open
- Created 8 months ago
- Comments: 55 (7 by maintainers)
Running 0.1.96 works perfectly. I tried 0.1.97 and 0.1.98 nothing worked after. So i decided to not upgrade Z-Wave JS anymore. Then now i could not resist, so i upgraded to 0.2.1 and still same problem. No Zwave device works after upgrade so i downgraded to 0.1.96 again.
I have been running HA with Z-wave JS for like 3 years and always proud over how stable it was.
Using rpi4 + Aeon Gen5
Update! So i were by some reason not able to restore any backup after upgraded to 2023.11, not the backup that HA created automatically due to the update or not the backup i manually created before, or the automatically created every night.
It just freezes and not restoring. I dunno why. So i’ve tried hardreboot several times and after each time 2023.11 is still there with ZWAVE JS 0.2.1… So i were not able to restore to my working setup 😦.
BUT!! I finally got it to work , by updating the firmware on my Aeon Gen5 stick. Follow this url: https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update
Now it works with 2023.11 and Zwave JS 0.2.1
Why i cant restore backup, is still wierd but since it works now i hope that new backups will work, or that new version of HA will fix it.
combination of HA 23.10.3 and JS 0.2.1 seams to work even with soft-reset = Auto
This was unfortunately a very common pattern in the Z-Wave world before the 700 series came out. Things have gotten better now that everyone is using standardized chipsets and SDKs because it’s possible to build open source tooling like the zwave-js flasher, but for these older generation sticks it doesn’t surprise me.
Fantastic News! And many thanks to maglerod. I use the Aeotex Gen 5 Stick (NOT THE ONE WITH PLUS) But updating to the newer FW from the 5+ solve the problem (link above) and I can now run HA 2023.11 without any problems. YOU MADE MY DAY! Christian
Two things:
If you are having issues please try a firmware upgrade of the controller and disabling softreset. If that doesn’t work, please share the controller model along with the addon logs from startup to where you experience issues.
I updated to 2023.11 and it seems to work (knocking on wood). For context, I downgraded to 2023.10.3 after having first issues via cli command.
Upgraded to 2023.10.3 to test, and it runs fine with latest zwave-ui-js. (Have as of yet not tried 2023.10.4, but have experienced zwave issues with 2023.10.5, as previously reported. Not with 2023.10.3 or prior.)
Great, but I presume this function is normally switched on for a reason? So this is only a temporary work-around, right? I am still hoping for a permanent solution by either JS or HA teams… Will try the next core update before…
In my case the Soft-Reset disable worked flawlessly. No problems since then and yesterday I upgraded all to the latest version. Still working…knock on wood…
Same here. Roll back to 2023.10.3 and JS 0.2.1. works here as well.