Akiokun
(Akiokun)
July 31, 2022, 8:06pm
1
Hey friends from the HA Planet,
I got some. Questions, I know how to change and migrate my ZHA coordinator… Buuut :!!!
If I die?
I want that the step should be made easy as backup, and that it should only take 3 steps max.
I ask you all, can you please make that true?
I need that…
Think about it, if there is a better stick or a better zigbee coordinator it should help.
Best regards your friend.
I think this is very hard to do, because there actually is some information in every zigbee device that you paired which identifies the specific coordinator you used. And there is pairing information in the coordinator itself too (at least the conbee 2, even when used with ZHA) and this information cannot be updated unless by a pairing or an unpairing request…
So I do not think you can really change the coordinator without physically initiating a pairing request with every and each end device. Which is kind of good for security in fact, even if it is annoying when you have to do that.
1 Like
jerrm
(Jerrm)
August 1, 2022, 1:05pm
4
darkshippo:
No you can’t.
Yes you can.
I moved between coordinators with different chipsets without repairing, and that was before ZHA Toolkit supported backup/restore.
I followed the methods here:
Should be easier now with Toolkit.
3 Likes
Akiokun
(Akiokun)
August 1, 2022, 3:21pm
5
I know that it’s possible, that’s why I want a simple UI solution for it, it should be easy.
Because HASS should be easy to use.
jerrm
(Jerrm)
August 1, 2022, 4:03pm
6
I agree. I think it will get there.
Z2M already does it automatically for TI family adapters. I don’t think it works across other chipsets with z2m yet, which is possible with the ZHA toolchain. My ZHA move was from HUSBZB-1(Silicon Labs) to Sonoff Dongle+(TI).
1 Like
Akiokun
(Akiokun)
August 1, 2022, 4:25pm
7
Exactly. We need to be simpler in the future.
CaptTom
(Tom)
August 1, 2022, 5:19pm
8
Good to know it’s at least possible.
I agree that HA “out of the box” ought to be at least as good as Z2M. I shouldn’t have to add two new components (Z2M and MQTT) to get this kind of feature. Zigbee is an important enough protocol that it shouldn’t require add-ons. It’s not just the added complexity. It’s two more things to learn, two more things to worry about for every update, two more things to bring breaking changes and bugs to HA.
Voted.
1 Like
makai
August 1, 2022, 7:13pm
9
It’s in the works:
home-assistant:dev
← puddly:puddly/zha-network-settings
opened 11:00PM - 27 Jul 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
Add a new tab to the ZHA interface to show the current network settings to allow them to be backed up/restored.
Unmerged Core PR: https://github.com/home-assistant/core/pull/75791
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
Testing this requires ZHA to be set up with a Zigbee radio. I've included screenshots below of the various interactions (dialogs moved around with dev tools to show more elements at once):
<details>
<summary><strong>Expand screenshots</strong></summary>
<img width="735" alt="image" src="https://user-images.githubusercontent.com/32534428/181386101-0b66f7f5-a51a-49e6-9baa-1997ff648dbb.png">
<img width="561" alt="image" src="https://user-images.githubusercontent.com/32534428/181386433-34e4d002-2d7c-47e7-a255-fe38989cfa09.png">
<img width="420" alt="image" src="https://user-images.githubusercontent.com/32534428/181386493-833dfbf8-22b8-43b4-aaa2-205f3b20e068.png">
</details>
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## 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] The code change is tested and works locally.
- [x] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
home-assistant:dev
← puddly:puddly/zha-backup-restore
opened 11:49PM - 26 Jul 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Implements the websocket API for listing, creating, and restoring ZHA network backups. This also adds a ZHA backup platform, which initiates network backup whenever a HA backup is created.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## 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] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Backend code is already merged so I think that it will be released with HA 2022.9
5 Likes
Akiokun
(Akiokun)
August 1, 2022, 11:42pm
10
Great news, very nice , this community rocks.
CaptTom
(Tom)
August 2, 2022, 1:31am
11
Nice! Thanks to all who contribute!!!
atrupo
(Alessandro)
September 27, 2022, 11:46pm
12
Hi! Thanks for the update I was waiting to migrate my Conbee II!
How is the backup file supposed to look like? The JSON generates is fairly empty. Is there a tuto on how to use the function? (I checked the official page but it didn’t help much)
1 Like