Open AlCalzone opened 1 month ago
The upstream issue https://github.com/home-assistant-libs/zwave-js-server-python/issues/1009 has been fixed, but I wonder if there should be some kind of backoff mechanism instead of immediately retrying the connection.
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
The problem
While working on the migration of Z-Wave JS Server to node-zwave-js v13, which had some incompatible changes, I noticed tons of logs in the server logs:
I still had a HA instance with the Z-Wave addon pointed to that IP address. In the HA logs, this error shows up several thousand times aswell:
What version of Home Assistant Core has the issue?
core-2024.8.0.dev202407060218
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS
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?
No response
Additional information
No response