Zigbee devices no longer communicating

[boasist]

The problem

About 11:50am on July 8, some of my zigbee lights started flashing without any user input, this went on for about five minutes before I went to the dashboard and turned them off. The flashing happened again shortly after, and now since then they are showing completely offline and I cannot communicate to them. Power outlet is operating normally, other zigbee devices flickered as well, yet are operating as usual.

While these are hue lights, I have them all configured directly through zigbee, and not a hue bridge.

I've tried to reconfigure them with no change, as it fails on communication.

Attached is the debug log where I attempted to reconfigure two of the offline units, and then issued commands with the hue remote to turn them on. home-assistant_zha_2024-07-09T13-15-10.838Z.log

What version of Home Assistant Core has the issue?

2024.7.1

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

Zigbee

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

[home-assistant[bot]]

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)}}

[colecrew]

Same problem

[puddly]

Have you tried power cycling the lights? Off for five seconds, then back on? The firmware in some is known to crash.

[kittyscastle]

@puddly I searched the known issues, because of ZHA issues that started with 2024.7.x, and saw the same remark about ‘power cycling’ a couple of times.

first I suspected the ‘database foreign …’ to be the cause, tried again when I saw the included fix in 7.2 but running into the same issues of ZHA not passing initialisation.

Quickest stable (so far) fix: regression to a 2024.6.x backup. Restarting after that and immediately starting to see the sensors and lights coming back to report.

I do not pretend to know the code and structure of ZHA, but could the two be related: the fix for the database causing ZHA to run into it’s own trouble? (maybe just for old database and early ZHA adopters)

PS two tries of going forward and backwards a core version with same results & prior ‘years’ of stable ZHA-zigbee network & immediate reporting from the ‘external’ coordinator which did not restart zigbee since it’s external via IP socket. (The old sonoff wifi coordinator)

[puddly]

@kittyscastle Can you include a ZHA debug log and open a separate issue? If you're having issues with startup, it won't be the same root cause as this issue.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.