ZHA does not work anymore after update to 2024.10.1

[brxxm]

The problem

Today I upgraded to 2024.0.1, previously 2024.9.3.

After the update everything worked except Zigbee. The Coordinator was found (SLZB-06M) and configured correctly it seemed. However ZHA did not initialize and no devices were recognised. I could not find any clue in the logs (did not really know where to look). So I completely deleted ZHA, rebooted HA and started again. It was not possible to configure ZHA, no matter what I tried. I don't know what to do now.

What version of Home Assistant Core has the issue?

2024.10.1

What was the last working version of Home Assistant Core?

2024.9.3

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

No response

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

[puddly]

Can you restore a backup where ZHA is still installed and enable ZHA debug logging to collect a debug log? Without logs, there's little that can be done.

Also, try to unplug your coordinator and plug it back in.

[progl0r]

The problem

Today I upgraded to 2024.0.1, previously 2024.9.3.

After the update everything worked except Zigbee. The Coordinator was found (SLZB-06M) and configured correctly it seemed. However ZHA did not initialize and no devices were recognised. I could not find any clue in the logs (did not really know where to look). So I completely deleted ZHA, rebooted HA and started again. It was not possible to configure ZHA, no matter what I tried. I don't know what to do now.

### What version of Home Assistant Core has the issue? 2024.10.1

What was the last working version of Home Assistant Core?

2024.9.3

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Same over here.

[brxxm]

I did try unplug the coordinator and plug it back in, a numer of times, to no avail. Rebooting the coordinator also did not help.

I m ready to restore the back up, but since this would be the first time for me I m a bit insecure.

Can I just restore the files from 'data' and the .storage hidden folder to the config folder, as suggested here? https://community.home-assistant.io/t/guide-home-assistant-core-restoring-a-backup/626347

I run HA on a VM, HAOS based so a full install on a virtual machine (on QNAP)

[darth-hp]

I have this error with socket also every now and then, probably since 2024.7.0 when I switched from Conbee USB to ZigbeePro socket. To bad you can't reload the integration but have to restart HA completely

[brxxm]

Took the plunge and reverted to 2024.9.3. Turned out I could do that from the UI, and it worked.

After HA came back on there was a message under 'Settings' (actually there were two more but those are irrelevant):

Clicked and saw this:

Clicked the first option (to restore back up settings) and after a while this appeared:

And everything works as before.

So I am not sure how to proceed. Which logs could be useful?

[puddly]

@brxxm now that ZHA is functional again, can you upgrade to the latest release and enable debug logging for the ZHA integration? Let it fail to load a few times and then disable debug logging, it'll generate a debug log file.

[brxxm]

@puddly I will try tomorrow, it's evening here. Thanks so far.

[WladyTee]

Dear Brxxm, I experienced the same behaving when I upgraded from 2024.08 to 2024.09 and it didn't get it fixed with 2024.10. I actually use an old NUC (x86) with CONBEE II.

The only way I found to fix the UNKNOWN ERROR OCCURRED after a correct recognition of my ZIGBEE USB DONGLE is very simple: I removed all settings from my CONFIGURATION.YAML concerning ZHA.

I put # on the beginning of each line and rebooted my NUC to make it work properly.

#####################################################################################################
# ZHA: ZigBee Home Assistant
#####################################################################################################
#zha:
#  database_path: zigbee.db
#  enable_quirks: true   #default true
  #custom_quirks_path: /config/zha/custom_zha_quirks/
#  zigpy_config:
#    ota:
      #It's enabled by default
#      enabled: true
#      extra_providers:
#        type: 
#          ikea
#          sonoff
#          tuya
      #Periodically send out a network-wide (including end devices!) image notification
#      broadcast_enabled: true
#      broadcast_initial_delay: 14400
#      broadcast_interval: 14400

I would suggest you to try this procedure and disable all ZHA lines in your CONFIGURATION.YAML. I hope it helps!

[brxxm]

@puddly

I just re-installed 2024.10.1. Just like yesterday ZHA came back with an error and reconfiguring failed, I have attached the log. home-assistant_zha_2024-10-10T18-17-11.126Z.log

While I was at it I decided to try WladyTee's solution mentioned earlier in the thread. I commented out the zha: section in my config file and restarted and guess what - it worked. Here's another log: home-assistant_zha_2024-10-10T18-21-31.855Z.log

Next step: uncomment the zha: section in the config.yaml, and restart HA. After the restart, the problem returned. Logfile #3: home-assistant_zha_2024-10-10T18-28-24.736Z.log

Next and final step: again comment out the zha: section in config.yaml, restart HA. Everything OK.

Hope this helps.

zha section in my config:

# Zigbee Home Automation (ZHA) settings
 zha:
   custom_quirks_path: /config/zha/custom_quirks/
   zigpy_config:
      ota:
        extra_providers:
          - type: ikea
          - type: sonoff

[brxxm]

@WladyTee as you can read I tried your solution and can confirm it solved the problem. Thanks a lot!

[WladyTee]

@WladyTee as you can read I tried your solution and can confirm it solved the problem. Thanks a lot!

I'm very happy that you fixed that issue too! I spent 5 weeks in struggling about it, I erased all the configuration in order to start from a clean status and I tested all USB ports but it was not working at all.

If I can say more, I had additional troubles with COMPANION APP very slow or no connection: again I modified CONFIGURATION.YAML in the HTML group and all Android smartphones reconnected immediately. I believe that 2024.09 and 2024.10 are not properly parsing CONFIGURATION.YAML and it causes multiple unforecastable issues.

Cheers from Milan! :-) Happy Home Assistant again! :-)

[darth-hp]

Mh. No solution for me. I need the custom_quirks_path

[brxxm]

TBH I don't consider it a solution, because it does not fix the bug. It's a work-around. You can try removing everything except the custom quirks path and see if that works. I did not spend time finding out which part of the settings caused the error.

[dmulcahey]

TBH I don't consider it a solution, because it does not fix the bug. It's a work-around. You can try removing everything except the custom quirks path and see if that works. I did not spend time finding out which part of the settings caused the error.

We agree and it will get fixed