backup between bellows and znp

[pipiche38]

I have a question, coming from the Domoticz user community on the possibility to backup on bellows and restore on znp ?

From what I see in the bellows backup is that the file produced is totally different than the ZNP one. I understood that we get only a kind of hash code on bellows, where on ZNP we have all nwkid, ieee and important information.

[Hedda]

It is supported and vice versa, the files produced by zigpy-cli should not be different so maybe a bug or user error? Both use same format:

https://github.com/zigpy/open-coordinator-backup

however I do not think wiki and readme has been updated how-to use zigpy-cli for backup and restore since the new radio API?

https://github.com/zigpy/zigpy/wiki/Coordinator-Backup-and-Migration

https://github.com/zigpy/zigpy-cli/blob/dev/README.md

zigpy/zigpy-cli#2

zigpy/zigpy-cli#13

#1006

[Hedda]

So could you confirm that it works because tested ?

Yes, backup image from bellows restored to zigpy-znp and vice versa tested by many so there have even been popular videos on YouTube.

It is quite common to see people posting in Home Assistant community forum about backing up older TI CC2530/CC2531 and restore to newer Silabs EFR32MG12/EFR32MG13/EFR32MG21, or other people backup older Silabs ETRX35x and restoring to newer TI CC2652/CC1352

[puddly]

That's the bellows command line utility. Use zigpy-cli or the backup interface and write the write-once coordinator EUI64, I've done it many times.

[pipiche38]

Thanks indeed much aligned with what is given by ZNP.

[Hedda]

FYI, puddly has now submitted patches for ZHA to Home Assistant core and frontend/GUI for backup + restore features/settings, see:

home-assistant/core#75791

and

home-assistant/frontend#13295

[Hedda]

write the write-once coordinator EUI64

Note and be warned that Silicon Labs EFR32 apparently only supports write-once for coordinator EUI64.