-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
Description
The problem
In the logs regarding the razberry daughterboard (zwave nodeid 1) I see every few hours: "Z-wave.Me Razberry Daughterboard Status is niet meer beschikbaar" (is niet meer beschikbaar = not available anymore"), followed up by a message "Z-wave.Me Razberry Daughterboard Status gewijzigd in Ready" (gewijzigd in = changed to) one or two minutes later. Also, the log get completely filled up with all kind of messages regarding all zwave components, +/- 50 in total, first hundreds of entries of all of them dead and then all of them being alive again. I have not been able to pinpoint the root cause, and I hope some can help me out. zwave_js, core and OS are all up to date, running on raspberry PI. I did a debug logging on ZWave_JS, relevant portion included as attachment, where razberry goes dead at 8:07:03
What version of Home Assistant Core has the issue?
core-2025.2.5
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
ZWave_JS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
Example YAML snippet
Anything in the logs that might be useful for us?
Before resetting at 8:07:03, I see a lot of unusual messages at 8:07:02 like
2025-02-28 08:07:02.196 DEBUG (MainThread) [zwave_js_server.server] 2025-02-28T07:07:02.037Z:
2025-02-28T07:07:02.037Z SERIAL « 0x01120004004b0a600d080031050122014dbc002a (20 bytes)
2025-02-28 08:07:02.197 DEBUG (MainThread) [zwave_js_server.server] 2025-02-28T07:07:02.121Z:
Additional information
No response