ZBT-1 to ZBT-2 -- z2m migration to z2m

Community Guides
, ,
22

It seems the IEEE was not cloned properly from ZBT-1 to ZBT-2
frame_counter and hashed_tclk also differ, but I can’t find any info if that’s a problem.

Thoughts?

coordinator_backup.json.old :

{
  "metadata": {
    "format": "zigpy/open-coordinator-backup",
    "version": 1,
    "source": "[email protected]",
    "internal": {
      "date": "2026-04-26T16:51:34.359Z",
      "ezspVersion": 9
    }
  },
  "stack_specific": {
    "ezsp": {
      "hashed_tclk": "7cbb476bc68a4798305bf1c18e902af3"
    }
  },
  "coordinator_ieee": "bc026efffed196f7",
  "pan_id": "da95",
  "extended_pan_id": "0251180ace3c3677",
  "nwk_update_id": 0,
  "security_level": 5,
  "channel": 11,
  "channel_mask": [
    11,
    12,
    13,
    14,
    15,
    16,
    17,
    18,
    19,
    20,
    21,
    22,
    23,
    24,
    25,
    26
  ],
  "network_key": {
    "key": "f5696ae8e06ac0355f1aa5ab3b3cbd41",
    "sequence_number": 0,
    "frame_counter": 37955871
  },
  "devices": []
}

coordinator_backup.json :

{
  "metadata": {
    "format": "zigpy/open-coordinator-backup",
    "version": 1,
    "source": "[email protected]",
    "internal": {
      "date": "2026-04-26T19:59:35.103Z",
      "ezspVersion": 13
    }
  },
  "stack_specific": {
    "ezsp": {
      "hashed_tclk": "80eebe6b778fa75c9227f5545ab268ce"
    }
  },
  "coordinator_ieee": "f796d1feff6e02bc",
  "pan_id": "da95",
  "extended_pan_id": "0251180ace3c3677",
  "nwk_update_id": 0,
  "security_level": 5,
  "channel": 11,
  "channel_mask": [
    11,
    12,
    13,
    14,
    15,
    16,
    17,
    18,
    19,
    20,
    21,
    22,
    23,
    24,
    25,
    26
  ],
  "network_key": {
    "key": "f5696ae8e06ac0355f1aa5ab3b3cbd41",
    "sequence_number": 0,
    "frame_counter": 4688
  },
  "devices": []
}
Failed ZBT-1 to ZBT-2 migration on Z2M. How to recover lost devices?
23

I’m not so much an expert, but I was expecting the devices list to contain the list of devices already paired… that’s why I thought you didn’t have any devices showing. But since this list is empty in the original coordinator_backup, then an empty device list must not be the problem.

24

Thanks @wmaker. I think it’s time for a new topic :slight_smile: :frowning:

25

I saw exactly the same thing. The coordinator_ieee address was reversed (order of digits) after cloning with the universal-silabs-flasher. I even tried it again, and got this message:

 universal_silabs_flasher.flasher INFO Device IEEE address already matches, not overwriting

So I went back to my old Sonoff dongle and restored from backup.

Maybe I’ll try flashing it with the address reversed and see if that works…

26

If anyone experience issues with instability after migration, make sure you’ve written the IEEE address correctly from the old adapter to the new one.

In “coordinator_backup.json” the “coordinator_ieee” is written in reverse, so when you’re writing the IEEE address to the new adapter you need to reverse it.

If the address is written as “hhggffeeddccbbaa” in the backup file, you need to write it as “aabbccddeeffgghh” to the new adapter.

For example:
universal-silabs-flasher --device /dev/serial/by-id/usb-Nabu_Casa_ZBT-2_441BF684C0A8-if00 write-ieee --ieee aabbccddeeffgghh

Also make sure that if you’re rewrite the IEEE address of the old adapter if you’re planning to use it as a Thread adapter. I used the new adapters “old” IEEE address on the old adapter.