zigpy
[REQUEST] Feature for "backup and restore" to migrate from one Zigbee coordinator HW adapter to other hardware?
This idea came from developer discussion between @Adminiuga & @puddly in https://github.com/zha-ng/zigpy-znp/issues/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:
- Any CC2530 based adapter hardware -> Any other CC2530 based adapter hardware
- Any CC2531 based adapter hardware -> Any other CC2531 based adapter hardware
- Any CC2538 based adapter hardware -> Any other CC2538 based adapter hardware
- LAUNCHXL-CC26X2R1 development board -> Zig-a-zig-ah (ZZH) CC2652R1 based adapter
- LAUNCHXL-CC1352P-2 development board -> Zig-a-zig-ah (ZZH) CC2652R1 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 CC2531 based adapter hardware
- Any CC2531 based adapter hardware -> Any CC2538 based adapter hardware
- Any CC2530 based adapter hardware -> Any CC2652 or CC1352P based adapter hardware
- Any CC2531 based adapter hardware -> Any CC2652 or CC1352P based adapter hardware
- Any CC2538 based adapter hardware -> Any CC2652 or CC1352P based adapter hardware
Would really be an awesome feature to have if could be made user-friendly for integration like ZHA!
@sanyatuning if you are interested then suggest following the discussion in https://github.com/JelmerT/cc2538-bsl/issues/97