home-assistant[bot]
commented
2 weeks ago Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
3dtrix
kjurcik
ErikSabel
The problem
ZHA fails after some time, between the same day or after a couple of days (2 or 3 days) It stays in a inizializing loop, what is visually seen. The only way to get it out is the turn it off, and back on. And a complete reboot is required to get it working, not only HA but also the system where it is installed on Not sure when it started, but at least a couple of weeks ago. Tried to swap the stick between USB2 and 3, but doesnt influence the effect
What version of Home Assistant Core has the issue?
core-2024.8.3
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
ZHA
Link to integration documentation on our website
No response
Diagnostics information
https://we.tl/t-kClFfF43QS
The logging file is to big, so i created a wetransfer link
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response