I recently bought a ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus USB stick for my Zigbee2MQTT setup. All working pretty good, and most devices seem to be connected and working ok. I do get a LOT of red error messages inside Z2MQTT so I think it might be a good idea to reburn the firmware on my Zigbee stick to run Ember and not ESZP.
I have looked at a few Youtube videos and looked at quite a few webpages describing how to do this. I thought I was pretty tech savvy, but it seems I might be slipping a bit! Anyway, I like the webpage option a lot, the web based version ie Silabs Firmware Flasher. I tried this on two Windows 10 machines with the CP210x drivers. The web installer sees the Sonoff device on the serial port, but then finally says it cannot determine the firmware details. And looking at the log it seems like it is reading the contents of the dongle ok, but just receiving the wrong responses.
I have seen a few command line versions of the upgrade, but I am a Windows users and am not very comfortable with linux commands, to be honest. My real problem here though is that the firmware files seem to be quite different to what I think it should be, so not sure if those versions are just out of date.
The file I have downloaded and hope is the right one is
ncp-uart-hw-v7.4.4.0-zbdonglee-115200 (about 233kb)
Does anyone have any helpful tips to get me rolling on this? I have even looked to buying a new dongle with the Ember firmware already installed, but so far no luck with that. Seems like vendors should be selling these items with the current firmware.
Yeah, tried that. Just now tried the Python method, but I gave up half way thru as the video was talking about the Z-Stack drivers and I think that is for the P version, not the E version. I presume that there is another python method around somewhere, so will keep my eyes open for that.
A lot of the videos seem out of date (a few years old) and as far as I can tell, do not work any more. There is also a LOT of confusion between what firmware is required for the E version.
Add-on version: 0.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 13.1 (amd64 / qemux86-64)
Home Assistant Core: 2024.10.1
Home Assistant Supervisor: 2024.10.0
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[08:19:26] INFO: universal-silabs-flasher-up script exited with code 28
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 28
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
This is the log from the last time I ran this addon. It sees the USB stick in the Device list (on the Configuration tab) and is set to baud rate 115200 and hardware flow off. I enabled the ‘Flash USB device’ option.
This is the ZigStar Silicon Labs FW Flasher version of the addon. The version you linked to above seems to be going to the wrong version. That is the TI Z-Stacks version, which I believe is the P dongle. But at this point I am so confused I seem to be going around in circles!