I am at the point where I want to convert my sky connect radio back to my conbee II stick.
My question is: can I migrate back using the migration utility in home assistant given that I changed the address of the conbee II to become the address of the skyconnect stick?
Hedda
May 26, 2023, 12:41pm
2
If using ZHA integration then yes, it allows migration back and forth between supported adapters. See:
home-assistant:current ← Hedda:patch-83
opened 01:29PM - 13 Feb 23 UTC
## Proposed change
ZHA integration documenting general procedure for Zigbee C… oordinator radio migration as applies to all radio types that support backup and backup restore in ZHA, (inspired by Home Assistant SkyConnect specific process https://skyconnect.home-assistant.io/migrate-zigbee-zha-only/).
Please understand that wrote this as a step-by-step guide format for the ZHA integration because while users of other Zigbee implementations (like ex. Zigbee2MQTT, deCONZ) can refer to extensive documentation or full wikis on their respective websites, the [ZHA integration](https://www.home-assistant.io/integrations/zha) have no other official website/pages for documentation.
## Type of change
<!--
What types of changes does your PR introduce to our documentation/website?
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR.
-->
- [ ] Spelling, grammar or other readability improvements (`current` branch).
- [x] Adjusted missing or incorrect information in the current documentation (`current` branch).
- [ ] Added documentation for a new integration I'm adding to Home Assistant (`next` branch).
- [ ] I've opened up a PR to add logo's and icons in [Brands repository](https://github.com/home-assistant/brands).
- [ ] Added documentation for a new feature I'm adding to Home Assistant (`next` branch).
- [ ] Removed stale or deprecated documentation.
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- Link to parent pull request in the codebase:
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue: fixes #
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the `current` branch.
- I made a change that is related to an upcoming version of Home Assistant and used the `next` branch.
- [x] The documentation follows the Home Assistant documentation [standards].
[standards]: https://developers.home-assistant.io/docs/documenting/standards
So while they only documented for SkyConnect the ZHA migration will work regardless of adapter(s):
https://skyconnect.home-assistant.io/zigbee-migration-selection/
Worked flawlessly! Thank you!
Hedda
May 29, 2023, 6:32am
4
Great! Please consider giving a thumbs-up to pull request if you like it or give improvement feedback:
home-assistant:current ← Hedda:patch-83
opened 01:29PM - 13 Feb 23 UTC
## Proposed change
ZHA integration documenting general procedure for Zigbee C… oordinator radio migration as applies to all radio types that support backup and backup restore in ZHA, (inspired by Home Assistant SkyConnect specific process https://skyconnect.home-assistant.io/migrate-zigbee-zha-only/).
Please understand that wrote this as a step-by-step guide format for the ZHA integration because while users of other Zigbee implementations (like ex. Zigbee2MQTT, deCONZ) can refer to extensive documentation or full wikis on their respective websites, the [ZHA integration](https://www.home-assistant.io/integrations/zha) have no other official website/pages for documentation.
## Type of change
<!--
What types of changes does your PR introduce to our documentation/website?
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR.
-->
- [ ] Spelling, grammar or other readability improvements (`current` branch).
- [x] Adjusted missing or incorrect information in the current documentation (`current` branch).
- [ ] Added documentation for a new integration I'm adding to Home Assistant (`next` branch).
- [ ] I've opened up a PR to add logo's and icons in [Brands repository](https://github.com/home-assistant/brands).
- [ ] Added documentation for a new feature I'm adding to Home Assistant (`next` branch).
- [ ] Removed stale or deprecated documentation.
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- Link to parent pull request in the codebase:
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue: fixes #
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the `current` branch.
- I made a change that is related to an upcoming version of Home Assistant and used the `next` branch.
- [x] The documentation follows the Home Assistant documentation [standards].
[standards]: https://developers.home-assistant.io/docs/documenting/standards