Hi there,
I hope this is the right category to post this in; I figure it’s more hardware than configuration related.
I’m trying to flash the Sonoff ZBDONGLE-E with EZSP to then get Zigbee2MQTT running. I’m using the Silicon Labs Flasher (v0.3.0) in HA. I think the dongle originally came with zstack installed, and I’ve since installed Multi-PAN. However, I struggled a lot with getting Multi-PAN to work, and I was told to just use a dedicated dongle for Zigbee and then I’ll get another for Thread in the future. I flashed Multi-PAN with the Silicon Labs Flasher after a huge amount of fiddling around, and honestly I’m not entirely sure what I did to make it work in the end.
Anyway, here are the logs I’m getting. This occurs with the firmware here and here. It also happens with both 460800 and 230400 baud rate.
-----------------------------------------------------------
Add-on: Silicon Labs Flasher
Silicon Labs firmware flasher add-on
-----------------------------------------------------------
Add-on version: 0.3.0
You are running the latest version of this add-on.
System: Home Assistant OS 13.2 (amd64 / qemux86-64)
Home Assistant Core: 2024.10.2
Home Assistant Supervisor: 2024.10.2
-----------------------------------------------------------
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
[16:43:50] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 460800)
2024-10-18 16:43:50.624 core-silabs-flasher universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.4', ezsp_version='7.4.4.0', ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=230400)
2024-10-18 16:43:50.624 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 460800 baud
2024-10-18 16:43:52.638 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 230400 baud
2024-10-18 16:43:57.650 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-10-18 16:44:02.659 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-10-18 16:44:06.979 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-10-18 16:44:11.298 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-10-18 16:44:15.618 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
[16:44:20] 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
I’ve also tried with the darkxst web flasher but I’m having problems there as well. When I click install it just hangs on 0.0% completed indefinitely. Using universal-silabs-flasher on my computer also doesn’t work: when I run universal-silabs-flasher --device COM25 flash ncp-uart-hw-v7.4.4.0-zbdonglee-230400.gbl it says Invalid value for '--device': COM25 does not exist. Obviously this is the correct port and it’s the one that the web flasher connects to, but for some reason USF doesn’t recognise it.
Does anyone know what could be causing my issues with Silicon Labs Flasher? And I suppose it’s related to what’s happening in the web flasher and in USF, but the addon seems to be where I make the most progress and I get the most logging, so I figure it’s best to persevere with that.
Thank you!