core icon indicating copy to clipboard operation
core copied to clipboard

Cannot get my Zigbee devices to stay online.

Open AndySymons opened this issue 1 year ago • 1 comments

The problem

I have a Zigbee network based on the SONOFF ZBDongle-P, six IKEA TRADFRI repeaters, a USB repeater and a Zigbee socket that acts as a repeater as well. The devices have operated all for over a year, but following intermittent problems I revised the layout last October to follow best practices for separation from WiFi and avoidance of interference.

However, three months later it all fell apart. Pretty much all the Zigbee devices went offline, except the coordinator. If I reconnect the repeaters, they configure successfully but go offline again within minutes (I have the “Consider mains powered devices unavailable after” set to 60 seconds). If the repeaters are all offline, it is not surprising that the end devices are too.

Today I completely re-installed the coordinator and all the devices. They all worked well for a couple of hours, but when I upgraded the HA core to 24.02.1, it started falling apart again – some of the repeaters went offline. Thinking that the upgrade had caused the problem, I reverted to the previous release using the HA backup. That only made matters worse. Now the repeaters are online but 29 of the battery-operated devices have gone offline.

I do not know if there is a bug or not. However, to identify the problem(s) it seems to be necessary to read the debug file and I do not know how to do that.

The attached is the debug log recorded when the system is restarted.

What version of Home Assistant Core has the issue?

24.02.1

What was the last working version of Home Assistant Core?

23.10.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

home-assistant_zha_2024-02-16T22-06-51.389Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing relevant

Additional information

No response

AndySymons avatar Feb 16 '24 22:02 AndySymons

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)

home-assistant[bot] avatar Feb 16 '24 22:02 home-assistant[bot]

I have the exact same issue, started a few months ago:

https://community.home-assistant.io/t/zigbee-connectivity-in-my-house-sucks/648916?u=mombro

I found that this is not an unusual problem, which I documented in the same thread here:

https://community.home-assistant.io/t/zigbee-connectivity-in-my-house-sucks/648916/47?u=mombro

No clue what the problem is, but maybe some device is spamming in zigbee network.

My next step is either z2m (but I like ZHA and skyconnect), or debugging (no clue how that works in ZHA, and no time for that)

Momro avatar Feb 17 '24 18:02 Momro

Yes, I saw your thread and followed a lot of advice given, in my October 2023 reconfiguration. Hedda's guide is particularly useful. https://community.home-assistant.io/t/zigbee-networks-how-to-guide-for-avoiding-interference-and-optimize-for-getting-better-range-coverage/515752

Another useful aid to me was a TinySA Ultra signal analyser (shop around, prices vary, but be sure to get the Ultra to cover 2.4 and 5 Ghz). https://www.youtube.com/watch?v=4c4oNJRnPrc I don't think there is intentional 'spamming' of Zigbee networks (who stands to gain?) but there is radio interference. The signal analyser showed that my TV was (for no apparent reason) transmitting across the whole 2.4 Ghz band. None of my diagnosis spotted this because the TV was off when I was tinkering with the network! The remedy was to move all my stuff well away from the TV.

AndySymons avatar Feb 18 '24 09:02 AndySymons

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.