ZW0202 Error Source #7491
-
Checklist
Describe the issueWhat is happening?
The nodes this specific error appears on seems to be sporadic and nonspecific to single nodes Steps to reproduce the behavior:
Anything else we should know? Software versionsZ-Wave JS UI: 3.18.0 Home Assistant Z-Wave Integration: Driver: 14.3.7 || Server: 1.40.2 Z-Wave Controller (Stick/Dongle/...)Zooz ZST39 800 Series LR Zwave Stick Device informationUsually part of the problem: Manufacturer: Inovelli Manufacturer: Inovelli Not usually part of the problem: (because they really arent part of the automations that smash the system) Manufacturer: Leviton Manufacturer: Ultrapro Manufacturer: Ecolink Checklist
Upload Logfile |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I can't see which firmware version you're on. 700 and 800 series have been plagued by a series of issues where the controller fails to send, sometimes sporadically, sometimes when there has been a bit of incoming traffic before. Sending a command to 22 nodes that also respond is a good way to trigger these issues. This typically shows up in the logs like the callback just above the log you quoted:
The most recent fix for this has been in SDK 7.23.0, but unfortunately there is no Zooz firmware built with that yet AFAIK. Side note: your background RSSI also seems very high. For 800 series I'd expect values around -110 dBm.
I also see a bunch of repeated electric measurements on a timed schedule, which can cause additional load/noise in your network. For both I recommend working through https://zwave-js.github.io/node-zwave-js/#/troubleshooting/first-steps - it might just help with your original problem too. |
Beta Was this translation helpful? Give feedback.
I can't see which firmware version you're on. 700 and 800 series have been plagued by a series of issues where the controller fails to send, sometimes sporadically, sometimes when there has been a bit of incoming traffic before.
Sending a command to 22 nodes that also respond is a good way to trigger these issues.
This typically shows up in the logs like the callback just above the log you quoted: