ZHA not working properly after upgrade to 2023.5.0 with HUSBZB-1

[seblang]

The problem

Since I have done the update some Zigbee device are working some other are working !
I have done the update to 2023.5.1 this morning, after this some Zigbee devise are working again but other not!
For exemple one of my Lumi weather is connected and work fine and another not!

What version of Home Assistant Core has the issue?

2023.5.0 and 1

What was the last working version of Home Assistant Core?

2023.4.6

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

zha-82d0623a1db9a205c6271a6eb5f9bb54-LUMI lumi.weather-f2416bf360e4270732e6a3c4ffb51276.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[maguiresf]

Yeah, had exactly the same thing, not just Weather but also Aqara motion and door open/close sensors so far. They are all starting to get stuck in one state then eventually drop off the network. Repairing fixes for a couple of hours then they start dropping again. Was mostly stable until 2023.5, nothing else at all has changed. Was similar to what I was seeing with older ZHA versions using a SkyConnect stick. Moving over to a SonOff had fixed it for a few months but now the failures are present on this stick as well. Sigh...

[gramsaran]

Same, last night I re-connected all the devices and the four main sensors is now unavailable again. Some of them are still active but the majority of my network is down. I'm using the zigbee stick as well.

[ronrose77]

I am having the same issues with my Aqara temp and water sensors. Don't update and eventually goes to Unavailable.
I am seeing this in the HA log after the upgrade, no other changes to my environment except upgrading to 2023.5.

Logger: zigpy.application
Source: components/zha/core/gateway.py:205
First occurred: May 4, 2023 at 9:09:49 PM (2 occurrences)
Last logged: May 4, 2023 at 9:09:49 PM

Zigbee channel 15 utilization is 92.06%!
If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.

[K0HAX]

I'm having this problem too. Is there some way to downgrade, this is unusable!

[Murcin86]

the same with Zigbee2MQTT - some plug working, some not... even sensor value looks like was freeze...
below example - plug shows some value but was not used since two days :(

[gramsaran]

I rolled back HAOS (core update --version 2023.4.6) and removed the updated Integrations, reconnected the zha clients and so far so good. Been about 12 hours and no disconnects.

[fabricioavil]

I had possibly the same problem, I spent the last 2 days trying to fix it. I tried many different things: changed WIFI channels and config, added even longer USB extension, restarted VM and host, etc. nothing was helping. What looks to have solved was a Conbee II firmware update (I had 26580700 and installed 26780700). When I reconnected the Conbee and restarted the VM, everything was back to normal.

I used the instructions from here to update the firmware:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-windows

[perosb]

@dmulcahey @Adminiuga can you please help label and triage this?

[KrunkKracker]

I have this same issue, and for whatever reason I cannot get my backups to restore.

What logs would be beneficial to help get the troubleshooting started?

[fiyahStrum]

Also having same issue. Have removed and readded devices multiple times but they no longer join the network to communicate with each other. One device will show it's connected in the network visualization but the others remain on their own and stop working after 10 minutes.

[333fred]

https://community.home-assistant.io/t/2023-5-0-broke-12-different-aqara-zigbee-devices has a number of other users who've experienced the same thing on 2023.5.X. For myself, I could not get any of my aqara devices to reliably stay on the network with 2023.5.0, .1, or .2. Rolling back to 2023.4.6 (with HAOS 10.1) stabilized it for me. Whatever logs I can provide to help, I'm happy to do so.

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, 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.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[puddly]

Whatever logs I can provide to help, I'm happy to do so.

ZHA debug logs of things working with 2023.4.6 and not working with 2023.5.2 would be helpful. Leave HA running for 20 minutes with each configuration to make sure enough traffic is collected. The logs will contain quite a bit of information so you're welcome to email them to me if you don't want to publicly attach them to this issue.

I rolled back HAOS (core update --version 2023.4.6) and removed the updated Integrations, reconnected the zha clients and so far so good.

Do you mean that you deleted the ZHA integration and set it up again? When you did so, did you select "erase network settings and form a new network", or did you restore a previous automatic network settings backup?

[gramsaran]

I restored from a previous automatic backup.

[333fred]

I'll try to get those logs tomorrow, if someone else doesn't get them first.

[sockmonkey0223]

I experienced the same after upgrading from 2023.4.6 to 2023.5.2. I rolled back to 2023.4.6 and everything has been stable. I did not (knowingly) update or rollback the ZHA integration.
I'll gather some debug logs on 2023.4.6. When I have the time to go through the upgrade & rollback again, I'll gather logs from 2023.5.2 as well.

[KrunkKracker]

I experienced the same after upgrading from 2023.4.6 to 2023.5.2. I rolled back to 2023.4.6 and everything has been stable. I did not (knowingly) update or rollback the ZHA integration. I'll gather some debug logs on 2023.4.6. When I have the time to go through the upgrade & rollback again, I'll gather logs from 2023.5.2 as well.

I've been trying to rollback with a backup, but it just reboots and does nothing. Looks like I'm stuck until this is figured out.

[zettalion]

Similar issues when I upgraded to 2023.5.x ZHA Integration fails to load- I'll send logs if the group needs more than provided by the contributors above.

Updated --- On a lark i went out and power cycled my ZHA device which is a sonoff. (never had to do this before after having stable operation for years). My system is back running again.

[RTS007]

Same issue by me. The whole Zigbee network is down (except Philips Hue Motion Sensor). I can add my debug files.

config_entry-zha-1092df2b1575785bddd04df13646bacf.json.txt
home-assistant_zha_2023-05-12T01-18-49.068Z.log

[puddly]

@RTS007 DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>') means that the current channel is too congested due to interference and the Conbee will not transmit (but likely will still receive). This is a common problem and one that is resolved by using a USB 2.0 extension cable and moving the device away from USB 3.0 ports, SSDs, 2.4GHz APs, and other sources of interference.

[JediBrown]

Adding a +1 to experiencing the issue, was fine before 2023.5.0. Affected devices are Aqara(aka Lumi) Cube, wireless switch, door sensors. Aqara sensors not affected: Temperature/humidity. Other zigbee brands/devices do not appear to be affected. Able to reconfigure the affected devices to get them to pair but they drop off after a period of time.

[puddly]

@JediBrown @seblang Can you upload the diagnostic JSON for the ZHA integration (click the exact button shown below and it will generate in a few seconds)?

[JediBrown]

config_entry-zha-.json.txt
@puddly

[tomlyo]

Same issue with both the 5.x updates I've taken. I've restored to 4.6 twice now as all my devices (primarily Aqara) go offline/unavailable. Restoring to 4.6 fixes the issue.

[rofo69]

Can I just confirm something. The write up for this bug suggested it was only affecting 'older' coordinators.

I am using a Sonoff Dongle-E that has the same chipset in it as the skyconnect, flashed to the recommended version 6.10.3 which was only updated 2 months ago. From what I have read this uses ezsp v8,so do I have to do anything else ?

Should I reflash it to the very latest 7.1.4 and would this resolve the issue before the fix comes out ?

This is the output from my ZHA debug info about the coordinator:

    "metadata": {
      "ezsp": {
        "manufacturer": "",
        "board": "",
        "version": "6.10.3.0 build 297",
        "stack_version": 8,
        "can_write_custom_eui64": true
      }

Stack version is (I think) ezsp version, so I am at v8, with a pretty recent firmware version.
So why is the bug reported affecting me ?

Especially given this phrase from the release notes here:

#92999

"This is a bugfix release that fixes a major issue with some Aqara devices dropping from the network when used with an older Silicon Labs coordinator (e.g. the HUSBZB-1). It affects no other coordinator combination."

[cgbeer]

Curious if this mornings update 2023.5.3 resolved issues for anyone? It did not for me as of now. I'll probably roll back to 2023.4.something as mothers day here and she's not happy when motion based automations not working.

• Bump bellows to 0.35.5 to fix Aqara Zigbee connectivity issue (@puddly - [Bump bellows to 0.35.5 to fix Aqara Zigbee connectivity issue #92999]/))
• Bump ZHA dependencies (@puddly - #92870)

[rofo69]

I've just updated but its too soon to tell. I also have the query in my last post above that doesn't seem to fit with the issue as described.

I'll check again in the morning to see if any devices have dropped offline.

[JeffCrum1]

I had the issue. I certainly fit the issues listed.

Just updated about an hour ago. I'll know more in 6-10 hours I think.

[scorfman]

Updated today as well and no improvement. Perhaps even a bit worse. Will report back in the morn.

[333fred]

For myself, 2023.5.3 appears to be working correctly. I updated this morning and none of my sensors have dropped after 8+ hours. Thanks puddly!

[KrunkKracker]

I was able to downgrade to 2023.4.6 by using the command below. This solved all my issues.

ha core update --version 2023.4.6

[milnergroup]

So far working for me. Have 2 installations with various zha sensors and devices
Aqara/ Lumi included and failed upon .0, .1 and .2 versions. Latest version fixed the issue so far.

[markaggar]

My aqara sensors have always been flakey, and I could only get one of them reliably connected. That good one fell off the network when I upgraded to 2023.5.0. Was hoping to get it and the other aqara sensors back online with 5.3, but they are still having the same issues. I have fairly large zigbee mesh with lots of repeaters, and these are the only devices that won't stay connected. I've read that aqara devices are notorious for disconnecting unless using (and only using) specific repeaters, so I'm surprised that the folks reporting this issue haven't had the same issues before now...

[milnergroup]

I had to add the devices after the upgrade but once I did they’re not dropping

[puddly]

Aqara devices work fine with Zigbee 3.0 routers, they only have issues with older routers that timed them out after a long period of inactivity (Aqara devices can be dormant for up to an hour, which for pre-3.0 routers was enough to consider them disconnected). Most devices you buy nowadays are Zigbee 3.0.

This issue only affected older Aqara devices that were joined as children to a HUSBZB-1 coordinator, since the setting responsible for telling it to ignore unresponsive child devices was not set properly. It now is. Older Aqara devices also did not pick their parent routers intelligently and seem to just pick the first one they detect when joining, so it's very possible for "distant" Aqara devices to have dropped off the network, since they were direct children of the coordinator by mistake.

When re-adding older Aqara devices, make sure to only permit joins through the physically closest routing device to where they will end up sitting:

[KrunkKracker]

Aqara devices work fine with Zigbee 3.0 routers, they only have issues with older routers that timed them out after a long period of inactivity (Aqara devices can be dormant for up to an hour, which for pre-3.0 routers was enough to consider them disconnected). Most devices you buy nowadays are Zigbee 3.0.

This issue only affected older Aqara devices that were joined as children to a HUSBZB-1 coordinator, since the setting responsible for telling it to ignore unresponsive child devices was not set properly. It now is. Older Aqara devices also did not pick their parent routers intelligently and seem to just pick the first one they detect when joining, so it's very possible for "distant" Aqara devices to have dropped off the network, since they were direct children of the coordinator by mistake.

When re-adding older Aqara devices, make sure to only permit joins through the physically closest routing device to where they will end up sitting:

I had this problem and I don't think I have a single Aqara device, although I do have a HUSBZB-1. Just an FYI.

[markaggar]

UPDATE
Success - I re-added all 3 of my aqara contact sensors explicitly via the 'Silicon Labs EZSP' ZigBee coordinator and they seem to be staying connected (unlike when I just 'Add Zigbee device' or try Adding via another ZigBee repeater). You can tell they are more likely to work by seeing the last update time being updated, and (after you refresh topology on the view network page and reload) they finally have a connection line to the coordinator. I did have to move the sensors closer to the stick to get them connected, but I've moved them further away since and the connection is still holding. Fingers crossed.

Original post
I've tried many times to connect the aqara contact sensors via other devices (centralite, securifi and tradfi) but they always disconnect, except the one that was working before I upgraded to 2023.5 (which won't stay connected now). My sense is that the aqara devices won't stick to the device they are initially connected to. I'm moving the devices closer to the silicon labs stick now to see if it will at least stay connected to that. Would be handy there was a way to tell the device or mesh to keep the device connected to the one it originally connected to the network with.

[rofo69]

So far so good since the upgrade to 2023.5.3.. Devices are staying online.

I would reiterate that my coordinator is not 'old' its the latest version of the Sonoff Dongle-E, running ezsp v8, so still not sure why it would have been affected.

[JeffCrum1]

27 hours and all still good. I'd say this was a success.

[cgbeer]

JeffCrum1, did everything connect right away when you updated or did you have to do that manually, I ask as one of may main motion detectors is shown as there but is not showing movement so not sure if i need to do anything else beyond just upgrading? When I update it's missing several zha devices, and some are showing but not actually changing states and when I go back to 2023.4.6 everything is connected right away.

[JeffCrum1]

JeffCrum1, did everything connect right away when you updated or did you have to do that manually, I ask as one of may main motion detectors is shown as there but is not showing movement so not sure if i need to do anything else beyond just upgrading? When I update it's missing several zha devices, and some are showing but not actually changing states and when I go back to 2023.4.6 everything is connected right away.

I am sorry. I should have given better details. After upgrade to 2023.5.3, I had to readd all devices. That happened at the time I reported above and everything has been good since then.

[andyjduncan]

Same here. I've been running 2023.5.3 for over a 24 hours now, and everything's working perfectly. All of my devices connected automatically.

[sockmonkey0223]

Updated to 2023.5.3 about 12 hours ago. I did not need to reconnect anything and Zigbee has been totally stable.

[exx76]

I upgraded to 2023.5.3 24 hours ago, and everything seemed fine. Woke up this morning, and 8 aqara devices are offline, so whatever was done was not the solution.

[rofo69]

My devices have stayed online, about 24 hours later,, so the change has been effective for me so far. If anything changes I'll update this thread.

[markaggar]

UPDATE. Success (fingers crossed). I re-added all 3 of my aqara contact sensors explicitly via the 'Silicon Labs EZSP' ZigBee coordinator as illustrated in @KrunkKracker's post above and they seem to be staying connected (unlike when I just 'Add Zigbee device' or try Adding via another ZigBee repeater). You can tell they are more likely to work by seeing the last update time being updated periodically, and (after you refresh topology on the view network page and reload) they finally have a connection line to the coordinator. I did have to move the sensors closer to the stick to get them connected, but I've moved them further away since and the connection is still holding. Fingers crossed. Thanks again @KrunkKracker for the guidance.

[tomlyo]

Mixed bag whether updating fixes, or doesn't fix the issue for people. Anybody know for sure if 5.3 fixes this? Otherwise I'll hold off for now.

[exx76]

It did NOT fix it for me. In fact, in some ways, it made it worse. At least with the three prior 5.x versions it was always the same devices falling off the network - now it's random. Devices that were never affected before have begun falling off. Very irritating to say the least.

[rofo69]

I'm now several days in and still stable. No issues to report.

[scorfman]

Looking rock solid now for me. All devices have recovered and connected. Thanks for the fix!

[cgbeer]

Tried it again and didn’t loose any devices on upgrading this time and have stayed on overnight.  Awesome and thanksCheers,Chris GrahamMoreFlavor Inc  Sorry for spelling errors or brevity, this was sent from my phone.On May 18, 2023, at 5:49 AM, Steve-O ***@***.***> wrote: Looking rock solid now for me. All devices have recovered and connected. Thanks for the fix! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[bfish2]

Still very much an issue for me. Skyconnect/ZHA. On 2023.5.3