Skip to content
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

[REQUEST] Feature for "backup and restore" to migrate from one Zigbee coordinator HW adapter to other hardware? #19

Closed
Hedda opened this issue May 11, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@Hedda
Copy link
Contributor

Hedda commented May 11, 2020

This idea came from developer discussion between @Adminiuga & @puddly in #10

Would it be possible to script a "backup and restore" migration feature/function built into zigpy radio libraries that allow users to relatively easily migrate from one Zigbee coordinator hardware adapter to a other Zigbee coordinator hardware adapter if use same radio library and maybe even if they are not using the exact same hardware MCU chip model/module?

Migrations such as these could become common as new more powerful adapters become available:

  • LAUNCHXL-CC26X2R1 development board -> ZZH (Zig-a-zig-ah!) CC2652R based adapter
  • LAUNCHXL-CC1352P-2 development board -> ZZH (Zig-a-zig-ah) CC2652R based adapter
  • ZZH (Zig-a-zig-ah) CC2652R based adapter -> ZZH-P (Zig-a-zig-ah "P") CC2652P based adapter
  • LAUNCHXL-CC26X2R1 development board -> LAUNCHXL-CC1352P-2 development board
  • Any CC2652R based adapter hardware -> Any CC2652P based adapter hardware
  • Any CC2652R based adapter hardware -> Any CC1352P based adapter hardware

Would be a more awesome feature if could also migrate from older TI chips to newer TI chips:

  • Any CC2530 based adapter hardware -> Any CC2652 or CC1352 based adapter hardware
  • Any CC2531 based adapter hardware -> Any CC2652 or CC1352 based adapter hardware
  • Any CC2538 based adapter hardware -> Any CC2652 or CC1352 based adapter hardware

Would really be an awesome feature to have if could be made user-friendly for integration like ZHA!

@puddly
Copy link
Collaborator

puddly commented May 13, 2020

This should be possible between all Z-Stack 3/4 radios by just running my script from the linked issue.

The limiting factors for all other migrations will probably be whether or not your old network was Zigbee PRO, if there is a way to extract all of the required information from non-volatile storage, and what you need to do to the extracted data to get it to be compatible with each radio.

I'll add my migration script to this package when I finish working through the other more important issues. Cross-vendor migrations are definitely cool but I don't really want to spend the time to work on it 😅

@Hedda
Copy link
Contributor Author

Hedda commented May 14, 2020

Cool! Do you think that your script could then be implemented as a UI feature in Home Assistant ZHA?

@puddly puddly added the enhancement New feature or request label May 16, 2020
@puddly
Copy link
Collaborator

puddly commented May 29, 2020

I've implemented backup and restore as runnable modules in 42b14f9, see the README for instructions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants