-
Notifications
You must be signed in to change notification settings - Fork 40
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
Conbee II as ZHA coordinator: can't make a backup #98
Comments
Zigpy-znp does backups of znp based radios only. It is not applicable to ConBee stick, because it is different. |
If you're not migrating between two coordinator sticks, there's no need to perform a backup. The relevant network settings are stored on your stick. Just migrate the contents of If you're trying to migrate from a Conbee II to a TI coordinator (e.g. CC2652), follow the instructions in this PR: zigpy/zigpy-cli#2 |
Actually what puddly said. I missed you are just changing the hosts, and not the sticks. |
@puddly is it works if i use Conbee II stick as ZHA coordinator? All devices and entities stored in zigbee.db, and if i copy configs and db from RPi's platform (OS, Supervisor, Docker) to HA Core on x86 all works?
|
Yes. If you are using the same coordinator, there's no need to run anything or do anything else besides copying |
@puddly - Thank you! Will try |
Sorry for offtopic, but after transfer zha.storage, zigbee.db and merging configuration.yaml i can see Conbee II stick as ZHA coordinator, but all device names and entities reset names to factory names. Is it any lifehack to transfer device and entities names to new host? |
The goal to transfer all zigbee devices from RPI with ConbeeII dongle (used as ZHA coordinator) to x86 host.
Try to backup devices with command
Steps are:
docker exec -it homeassistant bash
python -m zigpy_znp.tools.network_backup /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2456090-if00 -o network_backup.json
And get timeout
What i'm doing wrong? Any chance to solve it?
The text was updated successfully, but these errors were encountered: