-
-
Notifications
You must be signed in to change notification settings - Fork 28.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZHA shows 2 coordinators after migration #118237
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
This would be a problem and means that your Zigbee network is not in a good state. The IEEE address is rarely used in communication but if your coordinator's original address was not copied, your new coordinator is only superficially working. Any more complex device operations (e.g. joining) will cause unexpected failures. To fix this, download a backup JSON file from the ZHA config page: Update the firmware of your SkyConnect (https://skyconnect.home-assistant.io/firmware-update/) and replace all instances of the incorrect IEEE address with the address of your original coordinator. Then, perform a migration and re-configure the current coordinator. When you upload the fixed JSON, the new address will be written. |
Hi @puddly , Thank you for the troubleshooting. Will try today. For my reference:
Also, interestingly, I was able to join a device yesterday without issue (seemingly). Lastly, I'd propose an update to the documentation around migrating to a new radio. In the case of HA yellow, it's not possible to unplug the old radio, leaving one in the uncomfortable position of not knowing what the right course of action is. I'd suggest we make that part of the workflow a little clearer. Otherwise, moving network appeared to function immediately and well. Kudos! |
I actually ran into this issue today to and am sort of dead in the water. I was getting all kinds of Watchdog errors on a ZBDongle-P so I thought I would migrate to a ZBDongle-E and compare. I did my migration and it was successful but I noticed both coordinators too like in this post. I ended up deleting the old but the network on the new coordinator never really came back. I ended up trying to migrate back to the ZBDongle-P but with the same results. I actually have a ZHA backup from before I mucked with it however following the above steps cause an "Unknown error". I have flashed, re-booted, migrated, etc but everytime I go to upload the manual backup and restore I get "Unknown error". The debug logs have this:
I also see many:
Any ideas on how to successfully restore? |
For those that may run across my post...it turns out the restore works but just says unknown error. I had to reboot after the failed restore and let the stick initialize. Once it did, I just re-migrated again for good measure, and it worked fine. |
The problem
I migrated from HA Yellow built-in zigbee radio to a Skyconnect, prior to migrating from HA yellow -> Rpi (HA Yellow hardware was dying).
Everything now appears to work, but my ZHA config appears to show two 'EZSP by Silicon Labs' devices, and they both appear to be connected - impossible since I've turned off the HA yellow.
Somehow, it appears the config is split across both. Both appear to have different IEEE mac addresses.
I'm also (potentially coincidentally) having some zigbee issues, specifically Network Busy 161 errors. I have a total of 29 devices.
What version of Home Assistant Core has the issue?
core-2024.5.5
What was the last working version of Home Assistant Core?
No response
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
The text was updated successfully, but these errors were encountered: