Hedda
August 6, 2022, 9:15am
42
Suggest asking in the dedicated thread for that Blueprint or its GitHub reposiroty instead as kind of off-topic from the original post here which really just a feature request for ZHA devs to add this and not a support thread for workarounds.
Hedda
August 19, 2022, 7:25pm
43
FYI, Display ZHA network settings and allow downloading backups by puddly · Pull Request #13415 · home-assistant/frontend · GitHub supersedes ZHA network settings and backup/restore interface by puddly · Pull Request #13295 · home-assistant/frontend · GitHub as the initial frontend UI part, and ZHA backup/restore config flow by puddly · Pull Request #77044 · home-assistant/core · GitHub will adds network formation options to ZHA’s config flow, (that will give you several different options to let you “decide how to handle network information when setting up ZHA”):
home-assistant:dev ← puddly:puddly/zha-download-backup
opened 05:59PM - 19 Aug 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.
-->
This supersedes #13295 and provides a way to download backups. The websocket API is currently in Core so this is fully functional, there is just no way to restore network backups yet (https://github.com/home-assistant/core/pull/77044). A future PR will add a second button to change the radio type and/or migrate radios.
<img width="457" alt="image" src="https://user-images.githubusercontent.com/32534428/185678920-a2267161-ce2c-4187-95dc-8fdca94e12c1.png">
## 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
## 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-new-config-flow
opened 05:14PM - 19 Aug 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.
-->
Adds network formation options to ZHA's config flow. This lets you decide how to handle network information when setting up ZHA:
- Erase network settings and form a new network.
- Restore an automatic backup.
- Upload and restore a manual backup (frontend PR allows backup downloads).
- Continue with the existing settings on your stick.
## 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.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] 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
Hedda
September 8, 2022, 8:02pm
44
2 Likes
alsFC
November 17, 2022, 7:59am
46
Unfortunately that doesn’t keep your custom device and entity id naming and area relations:
Hello guys,
Any update on the issue on the issue that user defined entity id naming is lost after zigbee radio migration? I migrated to the yellow yesterday and migrated the radio from ConBee II to the internal chip and as others reported here: entity ids and names are set to default and area relation is gone. With ~60 devices and ~350 entities this is just not the way to go. So I switched back to ConBee for the moment which restored custom naming after restoring a HA backup.
Hedda
November 17, 2022, 11:42am
47
Not if restoring/migrating from third-party Zigbee solutions like Zigbee2MQTT (or IoBroker) to the ZHA integration , however it should keep it if the backup is made from the ZHA integration and migration is only from one supported Zigbee Coordinator adapter to a different supported Zigbee Coordinator adapter.
As in the current valid use-case is for a scenario when you are restoring/migrating from a backup made inside the ZHA integration from using for example an older CC2530/CC231 based Zigbee Coordinator adapter to a newer Zigbee Coordinator adapter like for example Home Assistant SkyConnect USB Stick or ITead’s “Sonoff Zigbee 3.0 USB Dongle Plus” (model “ZBDongle-P”) . See → https://www.home-assistant.io/integrations/zha#zigbee-backup-and-restore-in-zha
If that do not work then report ZHA integration issue to https://github.com/home-assistant/core/issues
alsFC
November 17, 2022, 11:51am
48
I backed up ZHA with ConBee II and restored to ZHA on internal chip in the Yellow. It didn’t keep custom naming as others report in this thread:
Hi,
After receiving a doom-laden email yesterday suggesting customs charges and UK VAT (Brexit - the gift they keeps giving
1 Like
Hedda
November 17, 2022, 12:00pm
49
Ah, that must be a bug that you need to report to → https://github.com/home-assistant/core/issues
alsFC
November 17, 2022, 12:32pm
50
Ok! Thanks! I will do that!
jjnj
February 2, 2023, 11:04pm
51
I’m slowly migrating from Domoticz to Home Assistant and loving it so far!
Hedda
February 3, 2023, 2:10pm
52
Not yet (but perhaps in the distant future you could convince Dresden-Dlektronik’s developers), and the reason for is that Dresden-Elektronik’s deCONZ/Phoscon software does not (yet) use the same “Open ZigBee Coordinator Backup Format ” that most of the open-source Zigbee implementations now support, (including; Home Assistant’s ZHA integration, Zigbee2MQTT, IoBroker, Jeedom, and the Zigbee Plugin for Domoticz). You can read and post feedback to Dresden-Dlektronik’s developers in this request → https://github.com/dresden-elektronik/deconz-rest-plugin-v2/issues/12
1 Like
