Open PetFra opened 3 months ago
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: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_3.x.0/bin
Make sure you have ZBDongle-E first!
I think problem is I have Dongle P This is mine: https://amzn.eu/d/0d47x3yq
and it says dongle P So I need to understand if I can make thread over it
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: https://github.com/TexasInstruments/ot-ti/commits/main
Hi thanks! I’ll look into it!
thank very much
Hello. @darkxst, look at my logs too, please. for some reason it does not want to connect to Windows 11, Chrome or Edge. I installed universal drivers on 07/19/2024. CP210x Universal Windows Driver v11.4.0. silabs_flasher (1).log
i tried to update locally. on a Proxmox machine. on a home assistant. installed venv, installed the flasher. tried two versions 7.4.2 and 7.4.3. but i have another problem.
@TarasRybak You need to use the raw link from github, otherwise its just downloading the html page.
@darkxst oh, thank you very much. it was successful!!!! I spent 4 days on all that.
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?
except mine is not V2
@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://github.com/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 https://github.com/darkxst/silabs-firmware-builder/issues/107#issuecomment-2282931735, or unsubscribe https://github.com/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...
2024-08-27 01:18:49 emscripten bellows.ezsp[42] DEBUG Resetting EZSP
2024-08-27 01:18:49 emscripten bellows.uart[42] DEBUG Resetting ASH
2024-08-27 01:18:49 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e'
2024-08-27 01:18:50 emscripten bellows.uart[42] DEBUG RSTACK Version: 2 Reason: RESET_POWER_ON frame: b'c102029b7b7e'
2024-08-27 01:18:50 emscripten bellows.ezsp[42] INFO NCP entered failed state. No application handler registered, ignoring...
2024-08-27 01:18:54 emscripten bellows.uart[42] DEBUG Connection lost: None
2024-08-27 01:18:54 emscripten bellows.uart[42] DEBUG Closed serial connection
I have a HA green and I am brand new to all this, so I will totally give that a try.
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
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 ember
backend in Z2M? it should work fine with my 7.4.x firmwares
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.
[2024-08-27 01:43:19] error: z2m: Error while starting zigbee-herdsman
[2024-08-27 01:43:19] error: z2m: Failed to start zigbee
[2024-08-27 01:43:19] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-08-27 01:43:19] error: z2m: Exiting...
[2024-08-27 01:43:19] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:746:19)
at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1758:24)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:127:29)
at Zigbee.start (/app/lib/zigbee.ts:63:27)
at Controller.start (/app/lib/controller.ts:139:27)
at start (/app/index.js:154:5)
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
Starting Zigbee2MQTT without watchdog.
[2024-08-27 02:11:16] info: z2m: Logging to console, file (filename: log.log)
[2024-08-27 02:11:16] info: z2m: Starting Zigbee2MQTT version 1.39.1 (commit #unknown)
[2024-08-27 02:11:16] info: z2m: Starting zigbee-herdsman (0.55.3)
[2024-08-27 02:11:17] info: zh:ember: Using default stack config.
[2024-08-27 02:11:17] info: zh:ember: ======== Ember Adapter Starting ========
[2024-08-27 02:11:17] info: zh:ember:ezsp: ======== EZSP starting ========
[2024-08-27 02:11:17] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-08-27 02:11:17] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2024-08-27 02:11:17] info: zh:ember:uart:ash: Serial port opened
[2024-08-27 02:11:17] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-08-27 02:11:18] info: zh:ember:uart:ash: ======== ASH connected ========
[2024-08-27 02:11:18] info: zh:ember:uart:ash: ======== ASH started ========
[2024-08-27 02:11:18] info: zh:ember:ezsp: ======== EZSP started ========
[2024-08-27 02:11:19] info: zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.
[2024-08-27 02:11:19] info: zh:ember: Adapter version info: {"ezsp":13,"revision":"7.4.2 [GA]","build":0,"major":7,"minor":4,"patch":2,"special":0,"type":170}
[2024-08-27 02:11:19] info: zh:ember: [STACK STATUS] Network up.
[2024-08-27 02:11:19] info: zh:ember: [INIT TC] Adapter network does not match config. Leaving network...
[2024-08-27 02:11:20] info: zh:ember: [STACK STATUS] Network down.
[2024-08-27 02:11:20] info: zh:ember: [INIT TC] No valid backup found.
[2024-08-27 02:11:20] info: zh:ember: [INIT TC] Forming from config.
[2024-08-27 02:11:20] info: zh:ember: [INIT FORM] Forming new network with: {"panId":28037,"extendedPanId":[230,91,206,189,106,92,214,131],"radioTxPower":5,"radioChannel":11,"joinMethod":0,"nwkManagerId":0,"nwkUpdateId":0,"channels":134215680}
[2024-08-27 02:11:20] info: zh:ember: [STACK STATUS] Network up.
[2024-08-27 02:11:20] info: zh:ember: [INIT FORM] New network formed!
[2024-08-27 02:11:20] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1247ms until next broadcast.
[2024-08-27 02:11:20] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
[2024-08-27 02:11:20] info: z2m: zigbee-herdsman started (reset)
[2024-08-27 02:11:20] info: z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":2,"revision":"7.4.2 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2024-08-27 02:11:20] info: z2m: Currently 0 devices are joined:
[2024-08-27 02:11:20] info: z2m: Zigbee: disabling joining new devices.
[2024-08-27 02:11:21] info: z2m: Connecting to MQTT server at mqtt://192.168.1.4:1883
[2024-08-27 02:11:21] info: z2m: Connected to MQTT server
[2024-08-27 02:11:21] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-08-27 02:11:21] info: z2m: Started frontend on port 8099
[2024-08-27 02:11:22] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-08-27 02:11:22] info: z2m: Zigbee2MQTT started!
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x6c5cb1fffe992e53/connection_state/config', payload '{"device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"device_class":"connectivity","entity_category":"diagnostic","name":"Connection state","object_id":"zigbee2mqtt_bridge_connection_state","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"payload_off":"offline","payload_on":"online","state_topic":"zigbee2mqtt/bridge/state","unique_id":"bridge_0x6c5cb1fffe992e53_connection_state_zigbee2mqtt","value_template":"{{ value_json.state }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x6c5cb1fffe992e53/restart_required/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"device_class":"problem","enabled_by_default":false,"entity_category":"diagnostic","name":"Restart required","object_id":"zigbee2mqtt_bridge_restart_required","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x6c5cb1fffe992e53_restart_required_zigbee2mqtt","value_template":"{{ value_json.restart_required }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/button/1221051039810110150109113116116_0x6c5cb1fffe992e53/restart/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","command_topic":"zigbee2mqtt/bridge/request/restart","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"device_class":"restart","name":"Restart","object_id":"zigbee2mqtt_bridge_restart","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"payload_press":"","unique_id":"bridge_0x6c5cb1fffe992e53_restart_zigbee2mqtt"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/select/1221051039810110150109113116116_0x6c5cb1fffe992e53/log_level/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","command_template":"{\"options\": {\"advanced\": {\"log_level\": \"{{ value }}\" } } }","command_topic":"zigbee2mqtt/bridge/request/options","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"entity_category":"config","name":"Log level","object_id":"zigbee2mqtt_bridge_log_level","options":["error","warning","info","debug"],"origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x6c5cb1fffe992e53_log_level_zigbee2mqtt","value_template":"{{ value_json.log_level | lower }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x6c5cb1fffe992e53/version/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"entity_category":"diagnostic","icon":"mdi:zigbee","name":"Version","object_id":"zigbee2mqtt_bridge_version","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x6c5cb1fffe992e53_version_zigbee2mqtt","value_template":"{{ value_json.version }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x6c5cb1fffe992e53/coordinator_version/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:chip","name":"Coordinator version","object_id":"zigbee2mqtt_bridge_coordinator_version","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x6c5cb1fffe992e53_coordinator_version_zigbee2mqtt","value_template":"{{ value_json.coordinator.meta.revision }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x6c5cb1fffe992e53/network_map/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"enabled_by_default":false,"entity_category":"diagnostic","json_attributes_template":"{{ value_json.data.value | tojson }}","json_attributes_topic":"zigbee2mqtt/bridge/response/networkmap","name":"Network map","object_id":"zigbee2mqtt_bridge_network_map","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/response/networkmap","unique_id":"bridge_0x6c5cb1fffe992e53_network_map_zigbee2mqtt","value_template":"{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x6c5cb1fffe992e53/permit_join_timeout/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"device_class":"duration","entity_category":"diagnostic","name":"Permit join timeout","object_id":"zigbee2mqtt_bridge_permit_join_timeout","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x6c5cb1fffe992e53_permit_join_timeout_zigbee2mqtt","unit_of_measurement":"s","value_template":"{{ iif(value_json.permit_join_timeout is defined, value_json.permit_join_timeout, None) }}"}'
[2024-08-27 02:11:27] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/1221051039810110150109113116116_0x6c5cb1fffe992e53/permit_join/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","command_topic":"zigbee2mqtt/bridge/request/permit_join","device":{"hw_version":"EmberZNet 7.4.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x6c5cb1fffe992e53"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"icon":"mdi:human-greeting-proximity","name":"Permit join","object_id":"zigbee2mqtt_bridge_permit_join","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"payload_off":"false","payload_on":"true","state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x6c5cb1fffe992e53_permit_join_zigbee2mqtt","value_template":"{{ value_json.permit_join | lower }}"}'
I suppose this is causing it to fail, but not sure why...
2024-08-27 01:18:49 emscripten bellows.ezsp[42] DEBUG Resetting EZSP 2024-08-27 01:18:49 emscripten bellows.uart[42] DEBUG Resetting ASH 2024-08-27 01:18:49 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e' 2024-08-27 01:18:50 emscripten bellows.uart[42] DEBUG RSTACK Version: 2 Reason: RESET_POWER_ON frame: b'c102029b7b7e' 2024-08-27 01:18:50 emscripten bellows.ezsp[42] INFO NCP entered failed state. No application handler registered, ignoring... 2024-08-27 01:18:54 emscripten bellows.uart[42] DEBUG Connection lost: None 2024-08-27 01:18:54 emscripten bellows.uart[42] DEBUG Closed serial connection
can someone with the above errors, try test with this patched flasher https://darkxst.github.io/cp-test/
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.
I suppose this is causing it to fail, but not sure why...
2024-08-27 01:18:49 emscripten bellows.ezsp[42] DEBUG Resetting EZSP 2024-08-27 01:18:49 emscripten bellows.uart[42] DEBUG Resetting ASH 2024-08-27 01:18:49 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e' 2024-08-27 01:18:50 emscripten bellows.uart[42] DEBUG RSTACK Version: 2 Reason: RESET_POWER_ON frame: b'c102029b7b7e' 2024-08-27 01:18:50 emscripten bellows.ezsp[42] INFO NCP entered failed state. No application handler registered, ignoring... 2024-08-27 01:18:54 emscripten bellows.uart[42] DEBUG Connection lost: None 2024-08-27 01:18:54 emscripten bellows.uart[42] DEBUG Closed serial connection
can someone with the above errors, try test with this patched flasher https://darkxst.github.io/cp-test/
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! Out of curiosity, what changed?
can someone with the above errors, try test with this patched flasher https://darkxst.github.io/cp-test/
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! Out of curiosity, what changed?
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.
Out of curiosity, what changed?
Sonoff changed the usb serial chip, the windows driver for this new chip (cp2102) has some quirks that reset device at an inconvenient time.
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.
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: silabs_flasher (1).log
Solved ! I was able to update the firmware using Secure CRT on windows10. The official instructions do not explain exactly how to start the boot phase and then press the key 1. The most important step! Once the device is connected you need to remove it and reinsert it into the USB port again while holding down the boot key on the device. At this point in SecureCRT you need to press the reconnect button and then release the boot button. Only in this way the menu appear that allows you to update the firmware.
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 silabs_flasher.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 Info Documentation Configuration Log Silicon Labs Flasher s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service banner: starting
s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [19:51:38] INFO: universal-silabs-flasher-up script exited with code 6 s6-rc: warning: unable to start service universal-silabs-flasher: command exited 6 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 s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service banner: starting
s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [19:51:42] INFO: universal-silabs-flasher-up script exited with code 6 s6-rc: warning: unable to start service universal-silabs-flasher: command exited 6 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 s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service banner: starting
s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [19:53:22] INFO: universal-silabs-flasher-up script exited with code 6 s6-rc: warning: unable to start service universal-silabs-flasher: command exited 6 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
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?
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: `Connection failed The running firmware could not be detected.
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.`
2024-10-18 21:11:58 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-10-18 21:11:58 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (115200 baudrate)
2024-10-18 21:11:58 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x15be540>
2024-10-18 21:11:58 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'3'
2024-10-18 21:12:00 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:00 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC at 460800 baud
2024-10-18 21:12:00 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (460800 baudrate)
2024-10-18 21:12:00 emscripten webserial_transport[42] DEBUG Closed serial port
2024-10-18 21:12:00 emscripten universal_silabs_flasher.common[42] DEBUG Connection made:
/<webserial_transport.WebSerialTransport object at 0x1aab508>
2024-10-18 21:12:00 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:00 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:00 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'x'
2024-10-18 21:12:00 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x00'
2024-10-18 21:12:01 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 1 of 4)
2024-10-18 21:12:01 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x80'
2024-10-18 21:12:01 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xf8\x00x\x80\x00\x80\x00\xf8\xf8\x80\xf8\xf8x\xf8'
2024-10-18 21:12:01 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to parse buffer bytearray(b'\xf8'): ValueError('Invalid flag')
2024-10-18 21:12:01 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:01 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:02 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 2 of 4)
2024-10-18 21:12:02 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:02 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:03 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 3 of 4)
2024-10-18 21:12:03 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:03 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:04 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
2024-10-18 21:12:04 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:04 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC at 115200 baud
2024-10-18 21:12:04 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (115200 baudrate)
2024-10-18 21:12:04 emscripten webserial_transport[42] DEBUG Closed serial port
2024-10-18 21:12:04 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1c4c278>
2024-10-18 21:12:04 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:04 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:04 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x11'
2024-10-18 21:12:05 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 1 of 4)
2024-10-18 21:12:05 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x1a'
2024-10-18 21:12:05 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xc1\x02\x02\x9b{~'
2024-10-18 21:12:05 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to parse buffer bytearray(b'~'): ValueError('Invalid flag')
2024-10-18 21:12:05 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:05 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:07 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 2 of 4)
2024-10-18 21:12:07 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:07 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:08 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 3 of 4)
2024-10-18 21:12:08 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:08 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:09 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
2024-10-18 21:12:09 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:09 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC at 230400 baud
2024-10-18 21:12:09 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (230400 baudrate)
2024-10-18 21:12:09 emscripten webserial_transport[42] DEBUG Closed serial port
2024-10-18 21:12:09 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x18b6c30>
2024-10-18 21:12:09 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:09 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:09 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x06'
2024-10-18 21:12:09 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xe0'
2024-10-18 21:12:10 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 1 of 4)
2024-10-18 21:12:10 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x98'
2024-10-18 21:12:10 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xe0\x06\x18\x18\x9e\xf8\x9e\x86\xfe'
2024-10-18 21:12:10 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to parse buffer bytearray(b'\xfe'): ValueError('Invalid flag')
2024-10-18 21:12:10 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:10 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:11 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 2 of 4)
2024-10-18 21:12:11 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:11 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:12 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 3 of 4)
2024-10-18 21:12:12 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2024-10-18 21:12:12 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2024-10-18 21:12:13 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
2024-10-18 21:12:13 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:13 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.EZSP at 115200 baud
2024-10-18 21:12:13 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (115200 baudrate)
2024-10-18 21:12:13 emscripten webserial_transport[42] DEBUG Closed serial port
2024-10-18 21:12:13 emscripten bellows.ezsp[42] DEBUG Resetting EZSP
2024-10-18 21:12:13 emscripten bellows.uart[42] DEBUG Resetting ASH
2024-10-18 21:12:13 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e'
2024-10-18 21:12:14 emscripten bellows.uart[42] DEBUG RSTACK Version: 2 Reason: RESET_POWER_ON frame: b'c102029b7b7e'
2024-10-18 21:12:14 emscripten bellows.ezsp[42] INFO NCP entered failed state. No application handler registered, ignoring...
2024-10-18 21:12:18 emscripten bellows.uart[42] DEBUG Connection lost: None
2024-10-18 21:12:18 emscripten bellows.uart[42] DEBUG Closed serial connection
2024-10-18 21:12:18 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.EZSP at 230400 baud
2024-10-18 21:12:18 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (230400 baudrate)
2024-10-18 21:12:18 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:18 emscripten webserial_transport[42] DEBUG Closed serial port
2024-10-18 21:12:18 emscripten bellows.ezsp[42] DEBUG Resetting EZSP
2024-10-18 21:12:18 emscripten bellows.uart[42] DEBUG Resetting ASH
2024-10-18 21:12:18 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e'
2024-10-18 21:12:23 emscripten bellows.uart[42] DEBUG Connection lost: None
2024-10-18 21:12:23 emscripten bellows.uart[42] DEBUG Closed serial connection
2024-10-18 21:12:23 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.SPINEL at 460800 baud
2024-10-18 21:12:23 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (460800 baudrate)
2024-10-18 21:12:23 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:23 emscripten webserial_transport[42] DEBUG Closed serial port
2024-10-18 21:12:23 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x18a9970>
2024-10-18 21:12:23 emscripten universal_silabs_flasher.spinel[42] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02')
2024-10-18 21:12:23 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~'
2024-10-18 21:12:23 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'x'
2024-10-18 21:12:23 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x00'
2024-10-18 21:12:24 emscripten universal_silabs_flasher.spinel[42] DEBUG Failed to send SpinelFrame(header=SpinelHeader(network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02'), trying again in 0.10s (attempt 1 of 4)
2024-10-18 21:12:24 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x80'
2024-10-18 21:12:24 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xf8\x00x\x80\x00\x80\x00\xf8\xf8\x80\xf8\xf8x\xf8'
2024-10-18 21:12:25 emscripten universal_silabs_flasher.spinel[42] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02')
2024-10-18 21:12:25 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~'
2024-10-18 21:12:26 emscripten universal_silabs_flasher.spinel[42] DEBUG Failed to send SpinelFrame(header=SpinelHeader(network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02'), trying again in 0.10s (attempt 2 of 4)
2024-10-18 21:12:26 emscripten universal_silabs_flasher.spinel[42] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02')
2024-10-18 21:12:26 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~'
2024-10-18 21:12:27 emscripten universal_silabs_flasher.spinel[42] DEBUG Failed to send SpinelFrame(header=SpinelHeader(network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02'), trying again in 0.10s (attempt 3 of 4)
2024-10-18 21:12:27 emscripten universal_silabs_flasher.spinel[42] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02')
2024-10-18 21:12:27 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~'
2024-10-18 21:12:28 emscripten universal_silabs_flasher.spinel[42] DEBUG Failed to send SpinelFrame(header=SpinelHeader(network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x02'), trying again in 0.10s (attempt 4 of 4)
2024-10-18 21:12:28 emscripten webserial_transport[42] DEBUG Closing serial port
2024-10-18 21:12:28 emscripten webserial_transport[42] DEBUG Closed serial port
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) 2024-10-15 18:30:49.943 core-silabs-flasher asyncio DEBUG Using selector: EpollSelector Error: '/root/firmware.gbl' does not appear to be a valid firmware image: ValueError('Unknown firmware image type') [18:30:50] INFO: universal-silabs-flasher-up script exited with code 1 s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1 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 s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service banner: starting
s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [18:32:28] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 460800) 2024-10-15 18:32:29.252 core-silabs-flasher asyncio DEBUG Using selector: EpollSelector Error: '/root/firmware.gbl' does not appear to be a valid firmware image: ValueError('Unknown firmware image type') [18:32:29] INFO: universal-silabs-flasher-up script exited with code 1 s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1 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 s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service banner: starting
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[19:54:06] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 460800)
2024-10-18 19:54:06.622 core-silabs-flasher asyncio DEBUG Using selector: EpollSelector
2024-10-18 19:54:06.623 core-silabs-flasher universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.4', ezsp_version=None, ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2024-10-18 19:54:06.623 core-silabs-flasher universal_silabs_flasher.flash DEBUG Probing app type ApplicationType.CPC first
2024-10-18 19:54:06.623 core-silabs-flasher universal_silabs_flasher.flash DEBUG Probing with 460800 baudrate first
2024-10-18 19:54:06.623 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 460800 baud
2024-10-18 19:54:06.623 core-silabs-flasher zigpy.serial DEBUG Opening a serial connection to '/dev/ttyUSB0' (baudrate=460800, xonxoff=False, rtscts=False)
2024-10-18 19:54:06.626 core-silabs-flasher universal_silabs_flasher.common DEBUG Connection made: SerialTransport(<_UnixSelectorEventLoop running=True closed=False debug=False>, <universal_silabs_flasher.gecko_bootloader.GeckoBootloaderProtocol object at 0x7f66251780d0>, Serial
Now I have found this "For ubuntu, you have to allow chromium to acces your usb devices: Settings > Apps > Chromium Web Browser > Permissions > Access USB Hardware directly"
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?
I've been trying to troubleshoot the issue for the past week, and up until yesterday, I was still unable to flash the firmware. But this morning, when I tried again on the website(https://darkxst.github.io/silabs-firmware-builder/), it just worked! Then I plugged in my other ZBDongle-E to test, and it also succeeded! Did you fix it? @darkxst
This is the information of my device:
Here is the success logs: ZBDonglee_success_silabs_flasher.log
Did you fix it? @darkxst
No, I havent changed anything in main site.
- And the driver version of CP2102N is 6.7.0.0.
Was there a driver update recently perhaps?
EDIT: That seems to be an older driver version, perhaps from before the reset bug was introduced in the driver.
Did you fix it? @darkxst
No, I havent changed anything in main site.
- And the driver version of CP2102N is 6.7.0.0.
Was there a driver update recently perhaps?
EDIT: That seems to be an older driver version, perhaps from before the reset bug was introduced in the driver.
Yes, I uninstalled the original 11.x version of the Windows driver and then installed the driver named CP210x VCP Windows from the Silabs website. After the installation was complete, I checked and found that the driver version had changed to 6.7.0.0, and then I was able to flash the firmware through the web tool.
To confirm that it was a driver issue, I reinstalled the previous 11.x version driver, and sure enough, I encountered an error when flashing the firmware.
If someone encounter the same issue, check your driver version, and try this:
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