Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deconz adapter/driver does not support backup and restore for ConBee/RaspBee by dresden elektronik? #665

Open
Hedda opened this issue Feb 15, 2023 · 22 comments

Comments

@Hedda
Copy link
Contributor

Hedda commented Feb 15, 2023

Does deconz adapter in zigbee-herdsman not support backup and backup restore for ConBee/RaspBee by dresden elektronik?

Is it currently only the zstack adapter/driver in zigbee-herdsman that supports both Zigbee Coordinator backup and restore? And as a follow-up question is there any plan to implement the same type of compatible backup for the deconz adapter?

@ChrisHae @manup @SwoopX @Haerteleric any chance one of you guys would be willing to take a closer look at this requested feature/function of 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 and IoBroker?

See related discussion here with users are also asking about migrating both to and from ConBee -> Koenkk/zigbee2mqtt#16478

deconz adapter/driver 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 and IoBroker users to from one adapter to another, regardless of radio type used:

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 -> dresden-elektronik/deconz-rest-plugin-v2#12

@Hedda
Copy link
Contributor Author

Hedda commented Feb 17, 2023

FYI, Also see related feature request for Dresden-Elektronik's deCONZ/Phoscon -> dresden-elektronik/deconz-rest-plugin-v2#12

@Hedda
Copy link
Contributor Author

Hedda commented Feb 23, 2023

FYI, Also see related feature request for Dresden-Elektronik's deCONZ/Phoscon -> dresden-elektronik/deconz-rest-plugin-v2#12

FYI as reference, in related news @ChrisHae posted in a reply in dresden-elektronik/deconz-rest-plugin-v2#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:

dresden-elektronik/deconz-rest-plugin-v2#12

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 abd Zigbee2MQTT or IoBroker.

@github-actions
Copy link
Contributor

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 github-actions bot added the stale label Mar 26, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Mar 26, 2023

@ChrisHae any updates or feedback on this?

@github-actions github-actions bot removed the stale label Mar 27, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the stale label Apr 27, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Apr 27, 2023

Not stale. Still valid and should be left open.

@ChrisHae Any news about this feature?

@github-actions github-actions bot removed the stale label Apr 28, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the stale label May 28, 2023
@Hedda
Copy link
Contributor Author

Hedda commented May 28, 2023

Still needed

@github-actions github-actions bot removed the stale label May 29, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the stale label Jun 28, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Jun 28, 2023

Not stale

@github-actions github-actions bot removed the stale label Jun 29, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the stale label Jul 30, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Jul 30, 2023

Do not stale

@github-actions github-actions bot removed the stale label Jul 31, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the stale label Aug 31, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Aug 31, 2023

@ChrisHae any updates or feedback on this?

@github-actions github-actions bot removed the stale label Sep 1, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 1, 2023

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 github-actions bot added the stale label Oct 1, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Oct 2, 2023

Still and issue for ConBee and RaspBee users

@github-actions github-actions bot removed the stale label Oct 3, 2023
Copy link
Contributor

github-actions bot commented Nov 3, 2023

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 github-actions bot added the stale label Nov 3, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Nov 3, 2023

Not stale

@github-actions github-actions bot removed the stale label Nov 4, 2023
Copy link
Contributor

github-actions bot commented Dec 4, 2023

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 github-actions bot added the stale label Dec 4, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Dec 4, 2023

@ChrisHae any updates or feedback on this deconz adapter backup and restore features still an open issue in zigbee-herdsman?

@github-actions github-actions bot removed the stale label Dec 5, 2023
@Hedda
Copy link
Contributor Author

Hedda commented Dec 5, 2023

@ChrisHae This feature request is even more relevant now that Zigbee2MQTT users want to migrate to ConBee III (ConBee 3), ex:

Koenkk/zigbee2mqtt#19785

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

@Hedda
Copy link
Contributor Author

Hedda commented Mar 18, 2024

This feature request is even more relevant now that Zigbee2MQTT users want to migrate to ConBee III (ConBee 3), ex:

Koenkk/zigbee2mqtt#19785

Any news on ConBee III (ConBee 3) backup and restore support in zigbee-herdsman's deconz adapter driver for Zigbee2MQTT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant