Updating to 2024.7.x crashed Zigbee Ikea lamps and switches and Tuya RGB lamps. 2024.7.2 did the same

[gvdarts]

The problem

Hi all, My Raspberry Pi3 with Home assistant OS 2024.6.x and Zigbee Sonof 3.0 with IKEA Zigbee lights and Dimmers ran great. I also have some TUYA RGB E27 lights who also worked fine. All the updates (2024.6.x) updated fine and after the updates HomeAssistant ran great without a problem.

I enjoyed Home Assistant very much

But Updating to 2024.7 made the lamps and dimmers(IKEA) unresponsive and messed up the Tuya light bulbs (Tuya needed to be reconfigured). Restoring a previously working full backup, 2024.6.4 didn't fix the problem. The lights sometimes worked but with a lot of delay.

Updating to the new 2024.7.2 had the same problem. No more zigbee and tuya

Anybody an idea why this is happening and maybe have a solution ??

Devices: Home Assistant OS on RaspberryPi3 SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coördinator, Universele USB IKEA e14 lamps, IKEA Dimmers, IKEA Wallsocket, IKEA Doorcontacts and IKEA Motion Sensor Tuya RGB E27

What version of Home Assistant Core has the issue?

2024.7.x

What was the last working version of Home Assistant Core?

2024.6.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zigbee and Tuya

Link to integration documentation on our website

No response

Diagnostics information

Logger: zigpy.zcl Source: runner.py:190 First occurred: 18:08:33 (1 occurrences) Last logged: 18:08:33

[0x541D:1:0x0020] Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 342, in request return await req.result ^^^^^^^^^^^^^^^^ asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/zigpy/zcl/init.py", line 377, in request return await self._endpoint.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/zigpy/endpoint.py", line 265, in request return await self.device.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 341, in request async with asyncio_timeout(timeout): File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in aexit raise TimeoutError from exc_val TimeoutError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/general.py", line 631, in check_in_response await self.checkin_response(True, self.CHECKIN_FAST_POLL_TIMEOUT, tsn=tsn) File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 81, in wrapper with wrap_zigpy_exceptions(): File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit self.gen.throw(value) File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 64, in wrap_zigpy_exceptions raise HomeAssistantError( homeassistant.exceptions.HomeAssistantError: Failed to send request: device did not respond

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.bootstrap
Source: bootstrap.py:733
First occurred: 18:05:31 (1 occurrences)
Last logged: 18:05:31

Waiting on integrations to complete setup: {('zha', '790d40f4f41cd1ed92a2798025719f3f'): 20284.117815465}

Additional information

No response

[lizsugar]

Same issue, started with 2024.7.0. Downgrading to 2024.6.4 a version where my lights did work, does not resolve the issue. Same SONOFF dongle, but with Sengled lightbulbs.

[lizsugar]

Tentative update: I re-upgraded back to 2024.7.2 after 2024.6.4 failed to resolve the issue. I flashed the firmware on my dongle (link to guide below) and rebooted the bulbs. So far they're both responding to changes and reporting their states correctly.

This usually happened after a full reboot of the bulbs and HASS though, so I'm monitoring it throughout the rest of the day with manual adjustments and my daily automations. I'll update accordingly.

This might be worth trying though anyway

Link to guide:

https://lizsugar.me/2024/04/08/sonoff-nvram-corrupted.html#okay-so-how-do-you-actually-fix-this-though

(the guide was written for a different issue I had encountered, but the process of flashing is the same)

[lizsugar]

It's just shy of a full 24 hours and all my zigbee lights are still working perfectly.

Why did this happen? How did this happen? How will the Home Assistant project make sure this doesn't happen again?

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

[puddly]

Restoring a previously working full backup, 2024.6.4 didn't fix the problem.

If restoring a backup doesn't fix the problem, the problem is with your Zigbee network. Unfortunately, there's nothing that really can be done to fix device-level issues like this. Reboot them and any intermediate routers, sometimes their firmware crashes in strange ways.

[gvdarts]

I have tried to repair my zigbee stuff (with version 2024.6.4 installed) , but that didn't work. So I updated Home assistant OS to 2024.7.2 Then updated my zigbee antenna, and reset the zigbee switches and lamps. Then I added all the zigbee stuff. I also had to reconfigure the tuya lamps, because these tuya lamps also stop functioning after the update.

Now everything is working again.

Still strange, that this problem never existed while updating in 2024.5.x and 2024.6.x The problem started after the update from 2024.6 to 2024.7

I hope, the problem stays away with future updates.

[lizsugar]

Restoring a previously working full backup, 2024.6.4 didn't fix the problem.

If restoring a backup doesn't fix the problem, the problem is with your Zigbee network. Unfortunately, there's nothing that really can be done to fix device-level issues like this. Reboot them and any intermediate routers, sometimes their firmware crashes in strange ways.

Except the issue is introduced by upgrading to 2024.7. Two working zigbee networks documented in this thread both broke after that update to mainline HASS. There are others in other open issues, all in time with the 2024.7 update.

Why did a HASS update break so many zigbee networks?

[puddly]

Except the issue is introduced by upgrading to 2024.7.

About 25% of all Home Assistant users run ZHA. That's a lot of people. If just two people have an issue after an upgrade, it doesn't necessarily mean it was caused by the upgrade, just that they had an issue at roughly the same time the upgrade was released.

ZHA isn't in control of your Zigbee network to the extent that an update will change the connectivity of individual devices. That's 100% a network stability issue and dictated by your environment.

If you can reproduce a connectivity issue that is introduced by the 2024.7.0 upgrade and fixed by downgrading, that's a different story.

[igi01]

I have the Same issue with Same coordinator

[skyflyer]

If it helps anyone: one sonoff mini switch and one Tuya switch stopped working after upgrade. Switched to 2024.6.4, same deal. Then, I:

• shutdown the computer running HA
• took the dongle out for 10 seconds
• booted up again (same situation)
• reset the switches (turn on/off repeatedly for a 5-10 times)
• they became back online
• upgraded to 2024.7.3, works.

For now.

Note: I did an upgraade from 2023.11 before that, so I was running quite an old version.