darkxst/silabs-firmware-builder

Impossibile to flash on SonoZigbee 3.0 USB

PetFra opened this issue · 44 comments

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 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

20240808_030036

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.
image

@darkxst
oh, thank you very much. it was successful!!!! I spent 4 days on all that.
image

silabs_flasher.log

I am having the exact same issue as Cannot flash my Sonoff ZBDongle-E with web flasher except mine is not V2
image

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)?

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.

silabs_flasher (5).log

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.

silabs_flasher (2).log

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?