Closed KipK closed 5 days ago
@Nerivec I believe this is expected since it does not have the TC link keys, right?
It is expected indeed. ember
doesn't have devices
since app link keys are not used (hence empty).
Will backup / restore to another stick still works then?
From an EmberZNet adapter to an EmberZNet adapter, it shouldn't be a problem.
For migrating to/from other stacks, as far as I know, stacks have different internal formats for app link keys anyway.
Note: ember
currently won't let you cross-restore unless you manually change the JSON (accepting the risks that go with it). zstack
doesn't prevent it, but that's mostly because it never did and was "alone" before.
Extensive testing is still required for cross-restoring, several stacks, many firmware versions, two directions... loads of data!
I've already successfully transferred my network from Zstack to EmberZnet few months ago. However I was using the previous znp implementation, and used zigpy for that task. Haven't tested the other way back yet.
What happened?
When doing a dongle backup with ember firmware from z2m or using ember-zli, the coordinator_backup.json generated doesn't have any devices included in device object:
devices": []
So I have doubt we can restore the network using actual ember backups yet.
What did you expect to happen?
should output the paired device in devices object:
How to reproduce it (minimal and precise)
Ask for a backup in z2m , and check coordinator_backup.json
Zigbee2MQTT version
1.40.1
Adapter firmware version
ember 8.0.1 ( tested with 7.4.4 too )
Adapter
SonOff-E
Setup
z2m in lxc container
Debug log
No response