-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossibile to flash on SonoZigbee 3.0 USB #107
Comments
The flasher is not getting any response from the dongle. Is this ZBdongle-E? what firmware is on it currently? |
Ho thanks, is the classic Sonoff ZigBee 3.0 dongle as far as I remember is the original firmware on it. Would using the python script bypass the issue? |
Sonoff have two different dongles, ZBDongle-E is compatible with my web flsher and these firmwares. The other one ZBDongle-P is a different chipset and requires different flasher and firmware from: Make sure you have ZBDongle-E first! |
I think problem is I have Dongle P and it says dongle P thanks a lot for your input |
Currently there are no Thread firmwares for the P dongles (that I am aware of anyway). I might release Thread firmware for these sometime in the future... For now, you can however build your own firmware from this repo: |
Hi thanks! thank very much |
Hello. |
@TarasRybak You need to use the raw link from github, otherwise its just downloading the html page. |
@darkxst |
I am having the exact same issue as Cannot flash my Sonoff ZBDongle-E with web flasher except mine is not V2 I have tried every USB port on my desktop and get the same error. I just bought this from itead less than two weeks ago. Is it possible it is already updated? How can I find out? |
@Dizzy49 Are you sure this is ZBDongle-E and not ZBDongle-P (which requires different firmware and flashing tools)? |
Yes, I ordered it from ITEAD and the item is "Zigbee 3.0 USB Dongle Plus--
ZBDongle-E"
I also verified on the back of the device.
…On Sun, Aug 11, 2024 at 5:55 PM Tim L ***@***.***> wrote:
except mine is not V2
@Dizzy49 <https:/Dizzy49> Are you sure this is ZBDongle-E and
not ZBDongle-P (which requires different firmware and flashing tools)?
—
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AXMYTO5UZIK52WN5FCDQWVDZQ72XRAVCNFSM6AAAAABK4WM47WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSHEZTCNZTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Having the same issue. Been trying to troubleshoot all night. I have the dongle-E and out of the box it was working fine. I started reading up on things and was suggested to flash with the newer firmware to use ember or whatever. Tool recognizes the dongle it looks like it connects for a second, then spins out and says cannot read firmware. Tried 3 cables, ports on both front of my PC, back of PC, some USB 2.0 and some 3.1 and 3.2. |
@Mdumas81 can you provide logs? It seems some Windows users are having trouble with web flasher recently, not sure why though, I havent been able to replicate myself. As an alternative if you have a HA box you can try use the Silabs flasher addon. |
I have a HA green and I am brand new to all this, so I will totally give that a try. |
I suppose this is causing it to fail, but not sure why...
There is a hidden setting in the silabs flasher addon (Click the button to show unused settings) that you can use to put a custom URL into. Just make sure you use the RAW url from github page. |
thank you, i think the firmware updated but i cant tell as the only way i know is to look from within z2m but z2m is now throwing errors |
Are you using |
I believe so, Ive been at this for a while now so I've messed around with a ton of things. I just reinstalled everything fresh and am trying to setup again but Im getting what appears to be one of the more common errors, but no solution has worked so far.
|
which firmware did you flash? |
ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl |
ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl seems to be flashing properly, Going to try that |
both those should work, there werent really any changes between 7.4.2 and 7.4.3. |
ok so 7.4.2 worked it looks like. Im getting a ton more info
|
can someone with the above errors, try test with this patched flasher |
Came across this issue while trying to flash my new ZBDongle-E. cp-test appears to work in that it recognizes the firmware version and provides an options to upgrade, but the install immediately fails for me. |
just came across this, as i had the same issues. Exact same logs as you mentioned. Tried to flash on https://darkxst.github.io/cp-test/ and it worked fine! Thanks so much! |
Using this tool I finally saw the update page, unfortunately, the update is not completed anyway. I've been waiting for 30 minutes but nothing happens. |
Sonoff changed the usb serial chip, the windows driver for this new chip (cp2102) has some quirks that reset device at an inconvenient time. |
Try get logs from developer tools (F12) |
Unable to identify existing default firmware with normal and cp-test flasher. Complains about the buggy macOS driver even though I'm using SiLabs. LED changes from red to green in the process. Here are the cp-test logs: |
I'm having issues with this too. Def have the zbdongle-e, when I open the web tool, it will recognize the dongle, then throw an error about not connecting. silabs_flasher (1).log can some one help, please? edit: with cp test, it seems to recognize the device, but fails at installing the firmware. |
There are known issues with the windows driver resetting device when we open serial port. Not managed to work around this yet. If you are using Home Assistant, easiest option is to use the "Silabs Flasher" addon to flash dongle. This has a hidden option to specify custom URL to flash. |
That didn't work either. "Universal-silabs-flasher-up exited code 6." |
can you paste full logs. and make sure you are using the "raw" links from github |
Silicon Labs Flasher Add-on: Silicon Labs Flasher
|
Is something else connected to dongle? make sure ZHA or Z2M dont have active connection to dongle while flashing |
I do not think I have any zigbee integrations or add ons. I did uninstall silicon labs multiprotocol. Do I need to configure the dongle on the devices page? |
yes you need to configure the dongle as device in silabs flasher addon |
Sorry for the delay, still no go. The flasher just sits there and doesn't do anything. I set the device up on the devices page and started a new network. Still nothing. Edit: I'll attach a log from the Linux web tool as soon as I get home. Edit2: I think I'm just stupid, and doing something totally wrong. Sunday, I ordered an slb-07, just in case the sonoff I bought was bad. It does exactly the same thing. Linux web flasher, and the ha based flasher, neither work. Now, with the ha based flasher, I get an error exiting code 1. And then it quits. |
EDIT: I used my wifes WIN 11 laptop and it worked just fine ... guess it's time to move to win 11 I have the same issue. Ordered the ZBDongle-E 3 with the SL chip EFR32MG21 Device Manager shows it as "Silicon Labs CP210x USB to UART Bridge (COM5)" (I installed the driver manually from slabs.com Logs: Make sure the USB port works and if you are using a USB extension cable, make sure the cable can transfer data. Unplug the Sonoff ZBDongle-E and plug it back in to reset and try again.`
|
When I try to flash using the web tool on a linux box, i get this log update: running the flashing tool from HA, I get this: [18:30:49] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 460800) Add-on: Silicon Labs Flasher
|
Now I have found this WTF does that mean? I have installed Ubuntu. There is no "settings". There is "system settings", but there is no "applications" there, only "applets", and chromium doesn't appear on that list. How do I find this setting? |
Hello there, I'm trying to flash a classic Sonoff to have Thread on it.
I tried on windows and Mac, but doesn't work.
I attach the log, I also tried with the python script but it didn't work for sure because of my poor Python Skill.
silabs_flasher.log
Any help would be highly apprecciated. Thanks
The text was updated successfully, but these errors were encountered: