So I have the one with EFR32MG21 chip when I flash the router firmware all is fine but when I try the coordinator firmware [from here]it remains red
going nuts!!!
Wrong topic.
Beeing a Late-Adaptor 
i recently got myself two (as i want to have a Fallback System, see below) Dongle Plus. Haven’t switched to productive Usage yet, as i want to avoid any Downtime.
Now, i have some General Questions before, any Operation Experience appreciated!
In Order to control my Network with both sticks alternating (of course not concurrent), i know i have to Copying the ieee address of an adapter | Zigbee2MQTT
I tend to use cc2538-bsl for flashing, as i can run it straight through Homeassistant, and don’t need to open up the Devices.
- Will it be necessary to run both sticks on the same firmware, or rather optional? Having different FW i could face possible related Issues as well
- If i understand correctly, after Setting IEEE Adress, reflashing FW is mandatory. The Command for Setting the Adress with cc2538-bsl includes a reflashing/upgrade of the Firmware, so no need to flash a second time again, have i got that right?
- my first stick is on 20210708, while the second is brand new, so presumably on a new FW. What FW would you recommend for a most-stable productional Environment? From what i understood reading several:
-
- Z-Stack_3.x.0_coordinator_20230507 seems to have stability issues from what i read
-
- Z-Stack_3.x.0_coordinator_20221226 should be more stable, but still having some (less) Issues.
-
- Older Firmware i can’t find, are they just too unstable, or why aren’t they listed?
Happy to hear what your Experience, Opions and Recomendations are! 
1 Like
Ok it’s been driving me nuts.
Situation:
I have two Sonoff Zigbee 3.0 -P dongles. Originally I had them both as coordinators and used the ‘migration’ flashing proceedure to help test the newer firmware. I since re-flashed the second one to a Router/Repeater instead of a Coordinator but the IEEE address has stuck cloned as the same as my main Coordinator. So I think this is creating some confusion in HA when I try to ‘manage’ the repeater vs coordinator and I want to change the IEEE of my router to something different but having no luck.
So to try changing the IEEE I’ve tried:
Flash Programmer 2 - no luck, shows as if it has updated but upon read-back it shows the old IEEE
CC2538-bsl - no luck, shows as if it has updated but upon read-back it shows the old IEEE
Zigstar - no luck, shows as if it has updated but upon read-back it shows the old IEEE
I’m using a Windows 10 machine.
So has anyone actually ever got this working a second time? Obviously mine worked the first time as it cloned the IEEE from my other dongle. But seems like it is stuck. I saw a one-off comment somewhere else on the internet that Silicon Labs chips only have a write-once IEEE ability and then it’s permanent. Can anyone confirm if this impacts the Sonoff Dongle-P?
FYI, there is experimental " 20231111/20231112" firmware builds available that those with issues might want to test and give feedback on → Z-Stack_3.x.0 coordinator 20231111/20231112 feedback · Koenkk/Z-Stack-firmware · Discussion #483 · GitHub
“First start by testing 20231112, if that doesn’t work try 20231111. If 20231112 works fine, there is no need to try `20231111” Compared to 20230922/20230923 these contain the improvements based on this TI topic → SIMPLELINK-CC13X2-26X2-SDK: Firmware not stable since SDK 6.20.00.29 - Zigbee & Thread forum - Zigbee & Thread - TI E2E support forums
PS: Always remember to do a Zigbee network backup to file before upgrading firmware.
hi all! i have checked this evening and i currently have the firmware 20210708 on my Sonoff_Zigbee_3.0_USB_Dongle_Plus. i use zigbe2mqtt.
what would be the benefits to update? will the procedure make me loose access to my current network configuration?
thanks a lot,
Nicola
1 Like
You FW is old. A lot of users were on 20221226 for a long time. Currently many use 20230922 and a new might come soon due to NWK problems. If you have no issues at all, then maybe wait for the new one…
You will not loose current linked devices.
I mostly agree with @khvej8.
With zigbee I take the “if it ain’t broke, don’t fix it” stance.
If you are having issues, try 20221226, or wait for the next update. The May/23 release has issues for some folks.
Would you be able to elaborate more on this?
I found this code
SERIAL_PORT_CFG = {‘name’: “COM” + name,
on the uartlog.py and removed “COM” but the script still does not work for me?
How do you specify the port name in linux? Is it dev/ttyUSB0? USB0? 0? I tried all of those and none of them work.
You’re asking about cc2538-bsl on linux right? Here is the command as I used it:
$python3 cc2538-bsl.py --bootloader-sonoff-usb -e -w -v CC1352P2_CC2652P_launchpad_coordinator_20221226.hex
and it auto-picked /dev/tty/USB0 which in my case was correct. If you already have another USB device there, the docs say you can use the -p option to select the serial device file yourself.
No. I was talking about the step prior to this. How to use the python scrypt to enter BSL? There is a python script, uartLog.py, that enter BSL on windows without disassembling the Sonoff stick. @sshaikh managed to make it work on Linux, but I can’t seem to follow his advice to make it work. See quote below.
If you are trying to get this to work on Windows, yeah I don’t know much about that.
That is what the above mentioned sonoff specific parameter does in JelmerT’s cc2538-bsl script:
”For ITead SONOFF Zigbee 3.0 USB Dongle Plus: For the CC2652P based “SONOFF Zigbee 3.0 USB Dongle Plus” (model “ZBDongle-P”) adapter from ITead you need to invoke toggle to activate bootloader with --bootloader-sonoff-usb if you do not want to open its enclosure to manually start the bootloader with the boot button on the PCB.”
Awesome. Thanks! Here’s what did for me, if it helps anyone else.
sudo python3 cc2538-bsl.py --bootloader-sonoff-usb CC1352P2_CC2652P_launchpad_coordinator_20230507.hex
1 Like
I’ve got a new dongle on order and it was listed as having Z-Stack pre-flashed. Do I need to consider doing any flashing as mentioned in this thread before I start using it or go ahead and set things up with what it was flashed with?
It is not an absolute must but yes it is generally recommended to upgrade the firmware before you start using it the very first time (since they still ship them with a very old firmware with many known bugs that have been fixed in newer versions), …however also note the tip that it then also generally recommended to update again and again later if and when you have issues with any devices as future versions can contain bug fixes for issues with devices that have not yet been released yet, (so after the initial firmware update you can follow the rule “if it ain’t broke then don’t fix it”) see:
https://github.com/Koenkk/Z-Stack-firmware
and
https://www.zigbee2mqtt.io/guide/adapters/#flashing-cc1352-cc2652-cc2538-based-adapters
PS: Other than upgrading Zigbee Coordinator firmware the very first time, another tip is that the “if it ain’t broke then don’t fix it" rule also applies to other Zigbee devices too (for example the IKEA Trådfri Zigbee devices having problems with latest firmware so better not to upgrade firmware if not having any issues).
2 Likes
@Hedda thanks. I was able to easily use the ti-cc-tool Docker image to flash the latest Z-Stack. I got it plugged into my Raspberry Pi on and extension and got my entire Zigbee network migrated over to it with almost no effort.
1 Like
for the record : may 2024 , on a raspberry pi 5 , i stuck it in a usb 3.0 port when i got it, and put a 2 meter usb3(blue…) extension in it when i read that was the thing to do, and it works just fine. Matter o fact when i re-plugged it into 2.0 trying to fig the herdsman error for 2mqtt it seems i had to manually reconfigure the whole thing and nothing worked anymore so i plugged it back into the original 3.0 and i had to kinda manually reconfigure it again, which worked fine up until the point where i choose “keep network settings” then i get “an” error … which apparently is fixed by after that point rebooting
this really is like doing linux in the 1990s …
so stuff might need revisiing in '24 for ra-pi 5s … i dont know and im by no means an expert but it works fine in a 3.0 slot
You only have to change the port configuration when moving it between different USB ports if you have not configurated the seriel device path as /dev/serial/by-id/
So suggest changing path in the configuration from /dev/ttyUSB0 to /dev/serial/by-id/ path as that will not change if change USB ports or add other USB devices.
Do not combine USB 3.0 port with a USB 3.0 cable as you will then get EMI interference. Use either a USB 2.0 port or a USB 2.0 cable (or both) to avoid EMI interference from USB 3. In fact, do not even place it close to other USB devices or cables. See:
Which include link to
And
Just jumped into the game and have a P with 20210708 loaded. However I want to go mainly with IKEA Tradfri Switches and Plugs for the beginning.
What is the latest stable Zstack recommended which does not have trouble with IKEA ?