Zigbee delays with ZHA and Conbee after Update HA Core to 2023.12.4

[hefetopf]

The problem

Starting with HA Core 2023.12.4 I discovered delays with Zigbee devices. Switching a simple Zigbee Wall-Plug needed around 10 Seconds and more. Several devices was unresponsive. I managed to revert to a backup of HA Core 2023.11.x and everything went fine.

What version of Home Assistant Core has the issue?

core-2023.12.4

What was the last working version of Home Assistant Core?

core-2023.12.3

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[hefetopf]

Tried once more. Got the following after Update from core-2023-11 to 2023-12.4:

Logger: homeassistant.core
Source: core.py:444
First occurred: 18:24:00 (1 occurrences)
Last logged: 18:24:00

Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: dlna_dms, update.zwave_js, fan.zha, assist_pipeline, vacuum.mqtt, cover, ssdp, wled, update.hassio, fan.mqtt, bluetooth_adapters, text.mqtt, event, device_automation, script, number.esphome, bluetooth, zeroconf, schedule, input_text, homeassistant, wake_word, climate, binary_sensor.shelly, sun, binary_sensor.fritz, timer, switch.fritz, stt, switch.esphome, light.tapo, lawn_mower, switch, scene.mqtt, light.tasmota, alarm_control_panel.mqtt, update.mqtt, fan.tasmota, sensor.mobile_app, button.shelly, cast, button.mqtt, switch.zwave_js, alarm_control_panel.zha, conversation, device_tracker.ibeacon, input_button, media_player, update.esphome, shelly, tts.cloud, camera, hardware, hassio, image, cover.mqtt, config, input_boolean, logbook, sensor.hacs, generic, update.fritz, cover.zha, mqtt, persistent_notification, api, tag, image.fritz, climate.zha, dhcp, select, binary_sensor.mobile_app, system_health, switch.mqtt, lock.mqtt, sensor.fritz, device_tracker.mqtt, esphome, fritz, number, auth, tasmota, siren.zha, default_config, sensor.systemmonitor, lock.zha, network, webhook, binary_sensor.wled, automation, sensor.statistics, image.mqtt, switch.tasmota, input_select, select.wled, alarm_control_panel, zone, number.mqtt, sensor.tapo, diagnostics, rpi_power, weather.met, analytics, binary_sensor.zwave_js, binary_sensor.tasmota, sensor.shelly, device_tracker.fritz, button, onboarding, device_tracker.mobile_app, cover.tasmota, binary_sensor.hassio, sensor.wled, ipp, tts.google_translate, light.zwave_js, scene.homeassistant, binary_sensor.tapo, select.zha, sensor.tasmota, media_source, update, binary_sensor.cloud, event.mqtt, button.zha, update.shelly, dlna_dmr, weather, water_heater.mqtt, fan, input_datetime, soundtouch, tts, google_assistant, map, number.zha, binary_sensor, update.wled, humidifier, event.zwave_js, mobile_app, sensor.sun, switch.wled, lock, button.fritz, homeassistant_alerts, switch.zha, light.wled, notify.mobile_app, humidifier.mqtt, stream, ibeacon, select.zwave_js, zwave_js, sensor.mqtt, media_player.dlna_dmr, search, sensor, radio_browser, cloud, binary_sensor.mqtt, switch_as_x, device_tracker, water_heater, event.shelly, binary_sensor.rpi_power, energy, frontend, button.zwave_js, input_number, sensor.energy, scene, logger, light.zha, light.switch_as_x, sensor.hassio, sensor.ibeacon, my, sensor.zwave_js, websocket_api, climate.mqtt, person, sensor.ipp, repairs, lovelace, lawn_mower.mqtt, yamaha_musiccast, camera.mqtt, usb, light.mqtt, http, select.mqtt, notify, number.wled, switch.shelly, hacs, light.esphome, binary_sensor.esphome, button.wled, binary_sensor.zha, recorder, siren, sensor.zha, history, text, camera.generic, vacuum, system_log, counter, switch.tapo, file_upload, blueprint, application_credentials, media_player.cast, image_upload, zha, cover.shelly, device_tracker.zha, tapo, number.zwave_js, light.shelly, light, met, sensor.esphome, trace, siren.mqtt, raspberry_pi, ffmpeg

[dmulcahey]

Sounds like something is misbehaving in your instance. Try restarting in safe mode please.

[dmulcahey]

Also, please fill out the template. Include your diagnostic file for ZHA and the complete log after restarting with debug mode enabled

[hefetopf]

ZHA Diagnostic File:
config_entry-zha-aa1a129ebd3acb179920585326af7789.json.txt

[hefetopf]

Full Log with Debug for ZHA enabled:
home-assistant_zha_2023-12-29T17-48-06.396Z.log

[hefetopf]

Sounds like something is misbehaving in your instance. Try restarting in safe mode please.

Restarted in Safe Mode did not resolve the issue.

[fhoekstra]

I had potentially the same issue when upgrading from 2023.12.3 to 2023.12.4.
Lots of Zigbee timeouts and lights went unresponsive. Rollback to 2023.12.3 resolved the issue, so the problem is likely to be introduced in this dependency upgrade:
#106147

Would it help if I provided my log and diagnostic file too?

[home-assistant]

Hey there @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)}}

[dmulcahey]

Yes

[hefetopf]

I had potentially the same issue when upgrading from 2023.12.3 to 2023.12.4. Lots of Zigbee timeouts and lights went unresponsive. Rollback to 2023.12.3 resolved the issue, so the problem is likely to be introduced in this dependency upgrade: #106147

Would it help if I provided my log and diagnostic file too?

Maybe Davids "Yes" is a response to your Question ;) @fhoekstra

[fhoekstra]

Yes that is how I understood it. I will try to do the upgrade again and gather the files. Can't promise that will be today though

[schwickster]

Same problem here. Started with .4 and reverting back to .3 fixes the problem. All ZHA devices using a Conbee 2 stick react very slow. Will look into logging and diagnostics tomorrow when reverting back to .4.

[emerycharlie]

Seeing a similar problem with Zha and sonoff plus stick. Glad it is not just me.

will be looking at rolling back to previous version but when I get round to it.

only 3 automations with aqara p1. It’s as if there is an initial 20-30s delay and haas has to wake up. After it has done so the automations are ok for a bit. If left alone it “goes back to sleep”.

[pbvdven]

Here also Conbee 2 same issue unresponsive devices since 2023.12.4.

[russ-sentient]

I have been experiencing ZHA issues after the upgrade to 2023.12.4 as well. Restarting HA will clear it for a while, then everything drops out again.

[Fonsohome]

Here also Conbee 2 same issue unresponsive devices

[puddly]

Please upload debug logs. Without logs, there isn't much that can be investigated!

[sidwin9]

Hello,
My log file
home-assistant_log.zip

[sidwin9]

There are big problems with ZHA since version 2023.12.0 and they are getting worse with the new versions which mainly followed 2023.12.4.

[Litux1516]

same issues as fhoekstra my hardware is sonoff ZBBridge with up to date tasmota.

[Litux1516]

here are my logs
homeassistantlogs.zip

[MaVeWeb]

Same issues here with ZHA and a Skyconnect. Reverting back from version 2023.12.4 to 2023.11.3 solves the issues.

[sidwin9]

Hello,
My logs over a longer period
home-assistant_log2.zip

[JohNan]

I'm experiencing similar issues. ZHA failes to initialize at startup. I have to manually trigger a reload to make it work. After an hour or two Core stops responding altogether. I have to power cycle the Yellow to get it back up running.

Here's my logs.

[Litux1516]

In my case I have to downgrade core to 2023.11.3 to get a stable system. Reverting to 2023.12.0 was working but only for 20 min. or so.

[frelew]

I first restored from 12.4 to 12.3. ZHA units non responsive. I use conbee II with zha. Restored 12.1 and now everything is snappy again. I never had 12.2 installed. I will see if I can try 12.4 again and send debug logs. For what it’s worth it affected Ikea and hue units and made the unusable.

[mbo18]

Same here since upgrading from 2023.12.3 to 2023.12.4. using a Conbee 2.
My logs are full of:

home-assistant_2023-12-30T20-31-55.342Z.log

I've also saw this:

Power sensors do not update as often as before (this is from a zigbee smart plug with monitoring)

EDIT: reverted to 2023.12.3 and my logs are clean again, no more issues.

[erkr]

This issue seems related to #105913. I have the same issues since my upgrade from 12.2 to 12.4

[dmulcahey]

If you still have issues please try the current beta

[fhoekstra]

Just opted in to the beta and update Core to the latest 2024.1 beta as well as the Supervisor update that it required. Seems to work flawlessly so far. Thanks for the quick fix @dmulcahey ❤️ !

Not sure if they'll be worth much now, but I'm still uploading my logs and diganostic file of the 2023.12.4 version.

config_entry-zha-03d7f02786e49908b5b80ed5c66e477d.json.txt
home-assistant_zha_2023-12-31T20-36-13.181Z.log

[dmulcahey]

@puddly did the heavy lifting. Glad it’s working. There is a known issue with zigbee groups that will be corrected with the next release.

[frelew]

Updated core today to 2024.1.0b4 and now the IKEA remotes at well as the Philips hue remote works perfectly fine again with my zigbee lights (ikea and hue). Thanks for the good job!

[Jessel723]

Yup my ZHA just failed. Not a single device is available and it just says initializing. Restarting doesn't do anything. Should note I just got and hooked up a new Sky Connect. I didn't choose to just start to use ZHA. But how easy is it to roll back and has this fixed people's problems?

[fhoekstra]

How easy is it to roll back?

Depends on your setup. In HA OS, you can go to settings, backups and click restore on core 2023.12.3. On Docker, you can change the image tag I guess.

Yes this has fixed the problems.

The other way to fix the problems is to roll forward to the 2024.1 beta.

But today is the first Wednesday of the month, so we should see a stable 2024.1 release in a few hours

[ChristophCaina]

we have received 3 new beta versions today ??
It might be worth to join the beta channel and test one of the recent beta versions (0b7) ... since it is likely, that the issue should already be fixed - if it is implemented in the 2024.1 final release.

or you just wait until the final release version has been built an is officially available.
Restoring a backup will also cause a loss of history data ... just keep that in mind :)

[erkr]

Yes I'm also waiting for the official release. Rolling back or installing betas, is too painful on my production system.

[dmulcahey]

The 2024.1 release had a bunch of fixes in it that should address stability. I am going to close this. If folks still have issues please open a new issue and provide full debug logs and completely fill out the issue template. Also, please don't piggy back other issues that are open unless the issue, error messages if there are any, and the hardware configuration for the coordinator are EXACTLY the same. Thanks!!

[robiecz]

I had potentially the same issue when upgrading from 2023.12.3 to 2023.12.4. Lots of Zigbee timeouts and lights went unresponsive. Rollback to 2023.12.3 resolved the issue, so the problem is likely to be introduced in this dependency upgrade: #106147

Would it help if I provided my log and diagnostic file too?

I have exactly the same issue.
RPi4, ZHA, ConBee II

[puddly]

@robiecz please open a new issue and attach ZHA debug logs for 30 minutes surrounding the failure.