Migrating from Zigbee 3.0 USB Dongle Plus (ZHA)(SoC CC2652P) to SkyConnect, unable to re-use old dongle as router

Was using the Zigbee 3.0 USB Dongle Plus (ZHA). Got the SkyConnect, and migrated over by backing up the old dongle, swapping dongles on HA, and restoring. Everything now works on the SkyConnect, I also enabled so that I see the 2 new services (Thread & OpenThreadBorderRouter) under “Devices & Services”. So far so good!

I then wanted to re-use the old Sonoff Dongle as a router to extend my network, and here is where the issues start. First, I re-flashed it with the Zigstar Multitool with the “CC1352P2_CC2652P_launchpad_router_20221102”, and hit the button before inserting. It is detected in HA, but seems to have the same ID as the new SkyConnect, so nothing is added!
I am guessing that I have the same IEEE Address on both dongles? How can I check if this is the case? And if so, how do I fix it?

You’ll need to change the ieee on the old stick.

IIRC, I think the zigstar tool supports changing ieee, if not use cc2538-bsl.

Changed the last letter of the IEEE to from an “a” to a “b”, and it now works!

Is the IEEE the same as a MAC-address?
Seems there is one more octet in the IEEE than what the MAC has, or is that not used, since it is 00?

If it is indeed a MAC, how does one pick a new one? Or is it totally random? On other devices, the MAC will point to the manufacturer. From googling, it would seem to start with “00:12:4b” for all or most zigbee dongles, so I assume it is differently built.

Functionally the same as a mac. Not sure of any nuances of length and format.

The TI chips allow the ieee they use to be changed at will.

With the SI Labs chips the ieee can only be changed a single time and there is no going back, so you’re SkyConnect will now always have the ieee of your old dongle. Likely not an issue unless you want to migrate again at some point.

1 Like

Good to know! This might have puzzled me if I had made changes in the future!
Any idea why it can only be changed once on the SkyConnect? Seems short-sighted and stupid, looking at how people might want to play around, and might therefor cause one or more migrations!

For the CC2652 adapter see https://www.zigbee2mqtt.io/guide/adapters/flashing/copy_ieeaddr.html

1 Like

Yep, that is what I did! Used the zigstar tool! Had to re-write the firmware at the same time though, just like your reference points out! It is now connected!