addons: Z-Wave JS failure
Describe the issue you are experiencing
Since the last version of home assitant Home Assistant 2023.9.3 Supervisor 2023.09.2 Operating System 10.5 Interface utilisateur : 20230911.0 - latest Z-Wave JS Current version: 0.1.93
My Z-Wave devices are not working. I have this error in the logs:
2023-09-27T16:30:01.702Z CNTRLR [Node 026] ping failed: The node did not acknowledge the command (ZW0204)
2023-09-27T16:30:04.424Z DRIVER no handlers registered!
2023-09-27T16:31:09.423Z CNTRLR The controller is unresponsive
2023-09-27T16:31:09.427Z DRIVER Attempting to recover unresponsive controller...
2023-09-27T16:31:09.518Z CNTRLR The controller does not support soft reset or the soft reset feature has been
disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment va
riable.
2023-09-27T16:31:09.521Z DRIVER Recovering unresponsive controller failed. Restarting the driver...
Error in driver ZWaveError: Recovering unresponsive controller failed. Restarting the driver... (ZW0100)
at Driver.destroyWithMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2769:17)
at fail (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3484:14)
at /usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3533:5
at runNextTicks (node:internal/process/task_queues:60:5)
at processTimers (node:internal/timers:509:9) {
code: 100,
context: undefined,
transactionSource: undefined
}
Shutting down
Closing server...
2023-09-27T16:31:09.541Z CNTRLR [Node 017] Assigning SUC return route failed: Timeout while waiting for a call
back from the controller (ZW0200)
Client disconnected
Code 1000:
Server closed
[16:31:10] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Z-Wave JS
What is the version of the add-on?
0.1.93
Steps to reproduce the issue
- start z-wave js addon
- check the logs with errors
System Health information
Message in french : Aucune correction n’est actuellement disponible -> no correction
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 9
- Comments: 162 (41 by maintainers)
Yeah I’m working on it. Hope to get the fix released today or tomorrow depending on how long the kids sleep later 😇
Same issue here. RPI with Z-wave HAT. Upgraded from Home Assistant 2023.6.3 and Z-Wave JS version: 0.1.84 at the same time to Home Assistant 2023.9.3 and Z-Wave JS version: 0.1.93. Z-wave started up but kept on restarting after a couple of “Failed to execute controller command after 1/3 attempts.”
Reverted to HA 2023.6.3 + 0.1.93 still problem. Revered to HA 2023.6.3 + 0.1.84 works again.
Sorry if the HA version is irrelevant here, noob here. Just thought I could chip in some info that the same happened with a HAT that isn’t USB-connected.
Upgrading my controller (gen5) and then grabbed the latest of zwave-js-ui and hass and it’s been fixed for me (so far).
I tried everything before upgrading the firmware and the system would eventually crash but after taking the plunge and upgrading it yesterday (took 10 minutes) everything has been smooth since then.
For more context, i did have four dead nodes which I’ve since removed, that will probably help the system run better too and prevent future problems.
That means your USB path isn’t detected. If it’s a VM in Unraid, then fix your pass-through configuration: https://community.home-assistant.io/t/new-setup-no-communication-to-z-wave-usb-stick/622801/7
If that doesn’t work, or not using a VM, then disable Soft Reset as mentioned previously.
there is a new version of Z-Wave JS that has been released and a PR open to update the official addon. The Z-Wave JS UI addon will probably get updated sometime tomorrow. Hopefully that will resolve all of the reported issues here
Well, fudge. I’ve been trying to find updated firmware for my Homeseer SmartStick+ G2 and found a windows tool for that that I was hoping would also let me manually delete the bad nodes from the controller. Unfortunately it has a “reset” button I tried with no tooltip or confirmation that I assumed was a soft reset. It was not. I’ll just be over here rebuilding my network now. Don’t mind me. 😢
Same issue with a dead node causing reboot loop. Using a RazBerry 2 (unclear on exact model) hat for a pie3b. Error started when upgrading to latest version of Home Assistant.
Home Assistant 2023.9.3 Supervisor 2023.10.0 Operating System 10.5 Frontend 20230911.0 - latest
Driver version: 12.0.2 Server version: 1.32.1 Z-Wave JS: 0.1.94
That would tie in with people rebuilding their networks from scratch and the problem going away, despite everything else hardware wise being the same. All well and good with a few nodes… not so much with around 60, and many hours of automations built around them 😄
So far I’ve only seen this happen when the command fails, so the dead node might be the reason.
Agree. Problems occur after recognizing a dead node. And even with 0.1.90 now the error occurs. With HA core_2023.9.3 Z-Wave JS 0.1.90 is still working.
After trying all sorts (including soft reset disable, stick unplugging and updating to JS UI 2.0.2, I’m now pretty convinced that if you have a dead node on your network, you can still suffer driver restarts constantly. https://community.home-assistant.io/t/upgrades-today-have-caused-constant-unresponsive-warnings-resulting-in-repetitive-driver-restarts-and-z-wave-interruptions/619424/75?u=cadwizzard
@psychogun I’ll need more complete driver logs (level debug) then.
That’s Z-Wave JS’s error code, has nothing to do with the device label.
I’ve pushed a PR with an updated Z-Wave JS that has a bug fix along with a new option to force disable soft-reset. If anyone in this thread has a 500 series controller and is willing to testing the PR for me, please reach out to me in Discord (same username). I can walk you through exactly what to do but the hope is that between the two things we should be able to resolve this issue for you, just needs some testing.
https://github.com/home-assistant/addons/pull/3237
Rolled back to 0.1.92 to see if that helped. It did not. Rolled back to 0.1.90 (the next backup I had) and it is working again.
Looks like a long list of changes in 0.1.91… two sound like they could be the culprit here. I’m guessing these releases came in rapid succession which is why I didn’t get 0.1.91 installed automatically.
I’m connecting trough: /dev/serial/by-id/usb-0658_0200-if00
My aeotec Gen5 stick is the old regular version (not Gen5+), running on v1.1.
I found there was a firmware update at aeotec: https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update It’s quite a tricky upgrade, it can brick the stick, so no warranty’s on this one.
I upgraded my stick 10 minutes ago via my Windows machine (it was quite a hassle to get the driver and the upgrade working). but since then no crashes yet… fingers crossed!
I have the same issue after i updated to 0.1.93 this morning. The driver seems to start, i see some z-wave nodes communicating, but then the controller seems to get unresponsive, and it tries to reboot.
After a while the driver does manage to start, but within a minute, the whole thing happens again.
This is mine