You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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 😅
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:
Would be a more awesome feature if could also migrate from older TI chips to newer TI chips:
Would really be an awesome feature to have if could be made user-friendly for integration like ZHA!
The text was updated successfully, but these errors were encountered: