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
Home Assistant’s ZHA integration uses this backup and restore feature by default and even support easy to use radio migration to allow migrating back and forth from one radio type to another radio type:
zigpy (and thus also Home Assistant’s ZHA integration) uses the self-developed open standard and open file format specified in the "Open ZigBee Coordinator Backup Format" project:
PS: Some zigpy radio libraries, like zigpy-znp and bellows, also have extended CLI tools to perform full NVRAM backup and restore too, as well as other functions, such as for example NVRAM reset (which can also be useful before doing a restore from backup):
The text was updated successfully, but these errors were encountered:
Hedda
changed the title
ZBOSS Zigbee network backup and network restore via zigpy radio API?
ZBOSS Zigbee network backup and network restore + radio migration via zigpy radio API?
Nov 29, 2023
Should also test possibility to migrate between different radio libraries, so go from zigpy-zboss to bellows or zigpy-znp and vice versa, for back-and-forth migration between various radio-types, or is there anything that prevents cross-platform compatibility?
zigpy's (new) radio API support unified commands for Zigbee network backup and network restore; will zigpy-zboss support this?
Home Assistant’s ZHA integration uses this backup and restore feature by default and even support easy to use radio migration to allow migrating back and forth from one radio type to another radio type:
https://www.home-assistant.io/integrations/zha/#zigbee-backup-and-restore-in-zha
https://www.home-assistant.io/integrations/zha/#migrating-to-a-new-zigbee-coordinator-adapter-inside-zha
zigpy (and thus also Home Assistant’s ZHA integration) uses the self-developed open standard and open file format specified in the "Open ZigBee Coordinator Backup Format" project:
https://github.com/zigpy/open-coordinator-backup
Zigbee network backup to file and restore is also an important feature because it allows network migration to and from different radios.
Reference:
zigpy/zigpy-cli#2
zigpy/zigpy#1006
zigpy/zigpy-cli#13
zigpy/zigpy-znp#97
zigpy/bellows#445
zigpy/zigpy-deconz#172
zigpy/zigpy-zigate#117
PS: Some zigpy radio libraries, like zigpy-znp and bellows, also have extended CLI tools to perform full NVRAM backup and restore too, as well as other functions, such as for example NVRAM reset (which can also be useful before doing a restore from backup):
https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#nvram-backup
https://github.com/zigpy/bellows/blob/dev/README.md#nvram-backup-and-restore
PPS: In addition suggest check out the unofficial “zha-toolkit” which adds additional services to ZHA (including for backup):
https://github.com/mdeweerd/zha-toolkit
https://community.home-assistant.io/t/zha-toolkit-a-big-set-of-zigbee-commands-on-top-of-zha-zigpy/373346
The text was updated successfully, but these errors were encountered: