ZHA devices Identify becoming unavailable/Unknown after 2024.8.1 update

[robin-gh2]

The problem

After installing the 2024.8.1 update, all my Aqara devices became unavailable and reported ' Identify became unavailable' & 'Identify became unknown' in the Logbook. I was able to add the devices again by getting them in pairing mode and use the 'Add Device' option in ZHA, which worked for a couple of minutes.

What version of Home Assistant Core has the issue?

core-2024.8.1

What was the last working version of Home Assistant Core?

core-2024.8.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

config_entry-zha-ca6fe7d84957f6ecce6bd04e37b69ab0.json

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

[TheJulianJES]

To clarify, "Identify became unknown" is fine and the default when the identify button was never pressed in the UI. If it's unavailable or missing in graph, then it's an issue.

[robin-gh2]

To clarify, "Identify became unknown" is fine and the default when the identify button was never pressed in the UI. If it's unavailable or missing in graph, then it's an issue.

I wasn't aware that "Identify became unknown" messages were normal as I didn't see any [Identity] entries in the log before today, but the gaps in the sensory data due to the unavailable status isn't what I would like to see.

[puddly]

Can you enable ZHA debug logging and leave it on for a few hours to record what happens when things go unavailable? If multiple sensors are going unavailable at the same time then that likely means your coordinator is disconnecting.

[robin-gh2]

At 4.38 the device is marked unavailable, but also the sensory data the hours before it looks suspiciously stable. Hope the debug logging helps to identity the root cause.

2024-08-13 04:38:12.073 DEBUG (MainThread) [zha.zigbee.device] 0xC9FC: last_seen is 21603.111093997955 seconds ago and ping attempts have been exhausted, marking the device unavailable

home-assistant_zha_2024-08-13T06-09-52.630Z.log

[mamartins]

Same here for all my signee devices.

I thought that this issue was already identified and was going to be fixed on the first August release

[puddly]

@robin-gh2 According to your debug log, your device joined on 2024-08-12 22:24:47.786, and sent a bunch of packets for about a minute while it was in joining mode. After that, it sent two temperature updates and was never heard from again. The device seems to be joined directly to your coordinator so if it was awake and sent anything at all (or even woke up to ask for data), it'd be in the log and it's not.

I suggest you change its battery. Is the device near the coordinator? It's joined directly to it. If not, re-join it by finding the physically closest routing device to where it will sit and then in the three-dot menu click "add devices via this device" to force the sensor to re-join through that parent when you reset it.

[robin-gh2]

Thanks @puddly for your suggestions. I did replace the batteries and after that didn't fix the issue, I forced the devices to a routing device which is within 3meters line of sight. The flatlines are still happening and they also become unavailable in the same manner as 3 days ago.

[Teldor1]

Same problem here.

[tdubu]

Two of my four zigbee devices stopped responding after I updated to 2024.08.02. I've tried resetting them and changing the batteries but no success so far.

[mamartins]

For me, every 24h all my devices go offline and to fix it I have to reload zigbee integration

[alexkey79]

With HA 2024.8.x I have many Zigbee missing device or nor available the main effected device are: *** lumi aq2 door sensor: all of them were re-setup and recognised as magnets some months ago. The sensor with the old setup is open-close don't show issues.

***philips HUE lamp LCT026

*** some Lumi Themperature sensors

The batteries of the device are good.

I tried a re-piring, but after a day lost again and the magnet sensor never worked

I tried remove and re-setup: start the recognition but the setup failed

[robin-gh2]

Is there anything I can do to work towards a solution for this issue?

[andyb2000]

I am also having this issue, it seems mainly around battery zigbee devices, they seem to drop off and even re-adding, re-pairing they do the same as shown in the image above, the temperature seems to stick at the last known value, sit for a while before they timeout (the "consider battery powered devices unavailable after (seconds)" setting for ZHA).

This is also the same as issue https://github.com/home-assistant/core/issues/124588

I'm running HASS

Core: 2024.9.2
Supervisor: 2024.09.1
Operating System: 13.1
Frontend: 20240909.1

ZHA is using: Sonoff Zigbee 3.0 USB Dongle Plus I've gone with two firmwares on the dongle to test, went up to CC1352P2_CC2652P_launchpad_coordinator_20240710.hex and now back down to CC1352P2_CC2652P_launchpad_coordinator_20230507.hex with no differences so I don't believe it's hardware. Also, same in terms of pairing, keeping the device in the same location with good signal strength and not moving it after pairing. Same with new batteries and I also modified one of my units to use a different battery pack to ensure they don't dip in voltage/current supplied to avoid that as a possible issue.

Additional info @puddly - These devices drop off at different intervals and are just the battery powered devices, so I suspect its more down to quirks in their buggy implementation rather than the co-ordinator going offline. If I check my TRV's (Danfoss) they remain connected and can see Checkin events firing and updates/last seen showing correct values.

[andyb2000]

Something else I've noted, not sure if relevant or how to capture this information. If I disable ZHA, wait a few minutes then re-enable ZHA (Integration within Home Assistant) then the devices that were having issues STILL show as missing/unknown, however other battery devices, etc, all resume operation correctly. Not sure if that is relevant, helps or not, but seems relevant since when ZHA is restarted does it do a 'wakeup' or discovery and devices check in correctly?

[sjanssen15]

For me, every 24h all my devices go offline and to fix it I have to reload zigbee integration

For me it seems to be the same issue, Aqara led strip works fine and after 24 hours it goes offline. If I restart ZHA however I get an error and if I reboot Home Assistant + the led strip, it works again.

Version: Docker / 2024.10.4 (but had this issue in previous version)

[croixpond]

I started using Home Assistant about a month ago. I started out using ZHA with my ZBDongle-e and several ThirdReality outlet/routers plugged in around the house. I had similar problems to those listed above: all my cheap battery powered Tuya stuff (mainly temp/humidity sensors) would work for half a day, then flatline. Then I'd restart HA and the same cycle - work for half a day and then flatline and be unavailable. Even the plugged in devices would drop off and become unavailable. I finally removed all zigbee devices and started fresh using zigbee2mqqt rather than ZHA. It's 100% better now, all the devices are staying online and reliable. I used this video to help me setup zigbee2mqqt: https://www.youtube.com/watch?v=sfsZF0R0HtE I flashed the dongle with firmware: ncp-uart-hw-v7.4.4.0-zbdonglee-115200.gbl and am using the latest 2025 HAOS update.

[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.

[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.