Koenkk
deconz adapter/driver does not support backup and restore for ConBee/RaspBee by dresden elektronik?
deconz driver/adapter in zigbee-herdsman does not support backup and restore for ConBee/RaspBee by dresden elektronik?
Is it currently only the code for z-stack adapter/driver (for Texas Instruments ZNP adapters) in zigbee-herdsman that supports both Zigbee Coordinator backup and restore? Update 2024-09-16: Creating backups to file and backup restoring is now also supported by the ember driver/adapter (for Silicon Labs EmberZNet adapters) as well.
So the follow-up question is there any plan to implement the same type of compatible backup for the deconz driver/adapter?
@ChrisHae @manup @Haerteleric any chance one of you would be willing to take a closer look at this requested backup and restore feature/function for Zigbee network backup and restore from/to deconz adapter (ConBee/RaspBee Zigbee Coordinator adapters) inside the zigbee-herdsman framework so that both backup to file and restore of backup from file works with ConBee/RaspBee adapters for feature parity in Zigbee2MQTT?
See related discussion here with users is also asking about migrating both to and from ConBee -> https://github.com/Koenkk/zigbee2mqtt/discussions/16478
We know that is it technically possible using deconz serial protocol since the feature is avaible in zigpy-cli using zigpy-deconz:
- https://github.com/zigpy/zigpy-cli
- https://github.com/zigpy/zigpy-deconz
Support in zigbee-herdsman's deconz driver/adapter is need for Zigbee network backup to file and restore from that file backup is needed for backup and restore support + cross-hardware migration in order to allow Zigbee2MQTT users to from one adapter to another, regardless of radio type used:
- https://www.zigbee2mqtt.io/guide/faq/#how-do-i-migrate-from-one-adapter-to-another
- https://www.zigbee2mqtt.io/guide/adapters/flashing/copy_ieeaddr.html
- https://www.zigbee2mqtt.io/guide/faq/#how-do-i-move-my-zigbee2mqtt-instance-to-a-different-environment
- https://www.zigbee2mqtt.io/guide/faq/#what-does-and-does-not-require-repairing-of-all-devices
For reference; zigbee-herdsman has implemented the support for the standard "Open ZigBee Coordinator Backup Format" as an open file format for storing all information about a Zigbee network in JSON file needed to in a backup and restoring of that backup:
https://github.com/zigpy/open-coordinator-backup
zigpy-deconz radio library which also uses deCONZ Serial Protocol does support backup and backup restore to ConBee/RaspBee using this format:
https://github.com/zigpy/zigpy-deconz
https://github.com/dresden-elektronik/deconz-serial-protocol
PS: Slightly off-topic but FYI for reference, there is also a similar popular request for "Open ZigBee Coordinator Backup Format" compatible backups in dresden-elektronik's own deCONZ/Phoscon software -> https://github.com/dresden-elektronik/deconz-rest-plugin-v2/issues/12
FYI as reference, in related news @ChrisHae posted in a reply in https://github.com/dresden-elektronik/deconz-rest-plugin-v2/issues/12 that he will look into "Open ZigBee Coordinator Backup Format" export and import in the "deCONZ REST plugin" for the deCONZ/Phoscon API and application. See:
Originally posted by @ChrisHae in https://github.com/dresden-elektronik/deconz-rest-plugin-v2/issues/12#issuecomment-1434394036
This kinda slipped pass me. But yes I think this is not a big effort to implement and would be an improvement for the ConBee/deCONZ.
Note! To clarify, he only said there that he can look into it for deCONZ/Phoscon, so he did not mention that he would also look into the backup and restore feature for the deconz adapter in zigbee-herdsman and Zigbee2MQTT (or IoBroker).
PS: Again, also check out indirectly related feature request for Dresden-Elektronik's deCONZ/Phoscon:
- https://github.com/dresden-elektronik/deconz-rest-plugin-v2/issues/12
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Not stale. Still valid and should be left open.
@ChrisHae Any news about this feature?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Not having backup support in zigbee-herdsman is still an issue for ConBee and RaspBee end-users.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Any updates or feedback on this deconz adapter backup and restore features still an open issue in zigbee-herdsman?
@ChrisHae This feature request is even more relevant now that Zigbee2MQTT users want to migrate to ConBee III (ConBee 3), ex:
https://github.com/Koenkk/zigbee2mqtt/discussions/19785
Any news on ConBee III (ConBee 3) backup and restore support in zigbee-herdsman's deconz adapter driver for Zigbee2MQTT?
Summery; native migration from one ConBee/RaspBee adapter to another is currently not possible inside Zigbee2MQTT.
For that to be possible Zigbee2MQTT would first need to add support for deconz adapter backup and restore features, as the deconz adapter code in the zigbee-herdsman library which Zigbee2MQTT depends on does not yet support Zigbee network backup and restore from ConBee/RaspBee Zigbee Coordinator adapters, as such you can not simply backup your old ConBee II adapter to a file from inside Zigbee2MQTT and then just restore such backups from file to your new ConBee III adapter (as you can with Texas Instruments based z-stack adapter in Z2M because that already supports the backup and restore feature inside the zigbee-herdsman library).
https://www.zigbee2mqtt.io/guide/faq/#how-do-i-migrate-from-one-adapter-to-another
Hopefully, the deconz adapter developers will priotiríze this feature in zigbee-herdsman now that new ConBee III adapter being available(?).
PS: Note that before migration you will always need to upgrade the firmware on your old ConBee/RaspBee adapter before doing a backup!
https://flemmingss.com/how-to-update-conbee-conbee-ii-firmware-in-windows-10/
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
Still an issue that discourage the use of ConBee/RaspBee as get to backups + prevent migration to and from ConBee/RaspBee:
- https://www.zigbee2mqtt.io/guide/adapters/deconz.html
While I can only speak for myself, think I can still say that as it stands right now with important features such as backup and restore missing, many of us who are a part of the Zigbee2MQTT and overall Zigbee open source projects communities can currently not with good conscience recommend ConBee II / RaspBee II or even the ConBee III to new Zigbee2MQTT end-users.
- https://www.zigbee2mqtt.io/guide/usage/mqtt_topics_and_messages.html#zigbee2mqtt-bridge-request
Not even the ConBee3 (ConBeeIII) can be recommended for Zigbee2MQTT as long as no backup support in zigbee-herdsman.
I am in the same position. Running Z2M with a Conbee II having the new Conbee III already on my desk. But redoo all of the Z2M setup of all devices is not the way to go. Where is the problem to not be able backup/restore from old to new stick?
Where is the problem to not be able backup/restore from old to new stick?
The reason is explained in detail in the original feature request issue above (at the top ) here -> https://github.com/Koenkk/zigbee-herdsman/issues/665 but as a short summary; while the deconz serial protocol can be used to achieve backup and restore such a feature is not yet supported for deconz based adapters like ConBee/RaspBee in Zigbee2MQTT for the simple reason that no developer yet programmed support for it to the zigbee-herdsman's code for its deconz driver/adapter -> https://github.com/Koenkk/zigbee-herdsman/tree/master/src/adapter/deconz
Until this is added end-users have the option to use the unofficial third-party workaround using the zigpy-cli command line tool (which depends on zigpy-deconz) as discussed in this other thread that you can find here -> https://github.com/Koenkk/zigbee2mqtt/discussions/16478 (but please respect that end-user usage of that is off-topic here but end-users are welcome to discuss that there is you like). If you are a developer then check out the code for zigpy-cli -> https://github.com/zigpy/zigpy-cli and zigpy-deconz which it depends on -> https://github.com/zigpy/zigpy-deconz
PS: Please take note and remember that this is a free and open-source hobby project so it is mainly only worked on by volunteers.