Z-wave Receiving Commands but Not Sending (800-series controller) #6429
-
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?YES, BUT a Home Assistant developer has told me to come here Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?YES, BUT a Z-Wave JS UI developer has told me to come here Checklist
Describe the bugWhat causes the bug? Unknown What do you observe? After running correctly for some time (at least days, if not longer), Z-wave JS stops successfully sending z-wave commands, even though it continues to receive commands correctly. Thus (most) devices still update, but controlling devices is not possible. Fully rebooting the hardware seems to remedy the issue. It's possible this relates to #6260, but filing a new bug since that oen is resolved. What did you expect to happen? Z-wave commands are successfully sent to devices. Steps to reproduce the behavior: Unknown Device informationI am running: zwave-js-ui: 9.1.2 My controller is a Zooz ZAC93 running the (problematic) 1.20 (SDK 7.19.3) firmware. I am running Zwave JS UI via the 2.1.2 HA plugin under HA 2023.10.3 using HAOS 11.0. How are you using
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
|
I'm not 100% sure when the issue started in the logs, but things seemed to be working correctly prior to |
Beta Was this translation helpful? Give feedback.
-
|
What seems to happen is the same issue you already linked to. The implemented recovery mechanism also works. But your power meters and multilevel sensors that tried to send a report to the controller during the time it was unresponsive went in full-on panic mode and started repeating their reports over and over via different routes, to the point that
Unfortunately this is nothing we can work around. I recommend going through this guide and applying it to reduce the strain on the network and the likelyhood of this happening until the firmware update drops. |
Beta Was this translation helpful? Give feedback.
-
|
No, but from Silabs, the update is scheduled for December, probably. Seems to be a complicated issue, which also affects other things than this lockup problem we're experiencing. |
Beta Was this translation helpful? Give feedback.
-
|
I reached out to zooz. They said silabs has an eta of 4 weeks for the new sdk. |
Beta Was this translation helpful? Give feedback.
-
|
Any update on this given its been about 4 weeks now? |
Beta Was this translation helpful? Give feedback.
-
|
You can watch the Silabs GitHub project for new releases. https://github.com/SiliconLabs/gecko_sdk/releases/ I'm guessing that the newly added 7.21.0 Known Issue 1227385 "The 700/800 controller can lock itself up. The controller is not able to |
Beta Was this translation helpful? Give feedback.
-
|
Reached out to zooz again. They have no ETA. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, @AlCalzone. I'll see if I can reduce the network load some and continue to wait for the permanent firmware fix. |
Beta Was this translation helpful? Give feedback.
What seems to happen is the same issue you already linked to. The implemented recovery mechanism also works.
But your power meters and multilevel sensors that tried to send a report to the controller during the time it was unresponsive went in full-on panic mode and started repeating their reports over and over via different routes, to the point that
Unfortunately this is nothing we …