Wrong ZHA radio migration process to a new coordinator

[mariuszpreiss]

Feedback

I believe that the process of migrating ZHA to a new device is a bit different to what is explained in step 9 of this documentation https://www.home-assistant.io/integrations/zha/#to-migrate-to-a-new-zigbee-coordinator-radio-inside-zha

I explained it in details here https://community.home-assistant.io/t/radio-migration-in-zha-should-zigbee-channel-change/762292/8?u=sierp but I believe that during the process there are 2 backups and you have to restore not the freshest (performed for a new zigbee coordinator, that will not work) but 2nd newest. You also need to fix zigbee network later, saying "I want to keep zigbee network configuration" - all details in the link above

I would create a PR but I am not 100% sure my findings are common for other coordinators as well, or maybe my case is special

Hope that helps!

URL

https://www.home-assistant.io/integrations/zha/

Version

2024.8.3

Additional information

No response

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this feedback 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 feedback. - `@home-assistant rename Awesome new title` Renames the feedback. - `@home-assistant reopen` Reopen the feedback. - `@home-assistant unassign zha` Removes the current integration label and assignees on the feedback, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information) to the feedback. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information) on the feedback.