Flashing the Sonoff ZBDongle-E to enable Matter, Thread and Zigbee on Home Assistant | Dialedin

[utterances-bot]

Flashing the Sonoff ZBDongle-E to enable Matter, Thread and Zigbee on Home Assistant | Dialedin

Discover the latest in home automation for 2023, Matter and Thread are about to revolutionise smart home tech. In this blog post, learn how to flash your Sonoff ZBDongle-E or EasyIot ZB-GW04 with a RCP MultiPAN firmware to set up a Zigbee network, while providing simultaneous support for Thread. Stay ahead of the game and explore the possibilities of these innovative protocols.

https://dialedin.com.au/blog/sonoff-zbdongle-e-rcp-firmware

[OriginalResponsibleUser]

This seemed to have worked perfectly. Thanks! I specifically bought the Sonoff ZB-Dongle-E because it was similar to the Home Assistant Yellow radio, and this is the first I've seen anyone have success with flashing the firmware from the itead Zigbee firmware to a multiprotocol firmware. Great job.

[timlunn447]

@OriginalResponsibleUser Thanks for the feedback!

We have now updated firmware links to the most recent v4.2.3 firmware release. You can even upgrade to the new firmware directly from this blog post using the newly added web flasher support, note that the baudrate has been updated to 460800 for these ZBDongle-E builds.

[Hedda]

Suggest you credit darkxst as well and not just Nabu Casa since use https://github.com/darkxst/sl-test

[darkxst]

@Hedda Thanks! I wrote this blog post... I didn't even think to credit my other self!

[Hedda]

@Hedda Thanks! I wrote this blog post... I didn't even think to credit my other self!

haha, I missed that, sorry

[golgoth73]

Hi, thanks for you post ! Is it possible to use the web flasher to update a EFR32MG13 dongle (Zigbee Popp) ? My sonoff dongle_e-R is flashed as a router and not a coordinator. Or can I flash the sonoff with zigbee router and thread ?

[darkxst]

Is it possible to use the web flasher to update a EFR32MG13 dongle (Zigbee Popp) ?

If you can find a suitable GBL firmware file, you can upload it to the webflasher and flash it to your device. However I dont recall seeing any RCP builds for this device. Would need further info such pinouts to add it to the firmware builder.

Edit: This is a rebrand of Elelabs ELU013, for which you may find firmware.

Or can I flash the sonoff with zigbee router and thread ?

No its not possible for these two functions to co-exist.

[Hedda]

Or can I flash the sonoff with zigbee router and thread ?

No its not possible for these two functions to co-exist.

@golgoth73 I suspect that you really meant to ask if it supports flashing a Zigbee Router firmware image or a Thread firmware image, (and not asking if there is a single firmware image that supports Zigbee Router and Thread in the same firmware image).

I understand that the terminology can be confusing with a "Zigbee Coordinator" being a controller similar to "Thread Border Router" functionality, while a Zigbee Router" is just a Zigbee device (like a mains-powered smart lightbulb) that act as a repeater in a Zigbee network mesh but have no controller functionality at all. Suggest that you read through this introduction to Zigbee:

https://www.home-assistant.io/integrations/zha#introduction

To clarify, there are firmware images that support concurrent multiprotocol (meaning they support several protocols to run simultaneously at the same time) with the combination of Zigbee Coordinator (NCP or RCP) and Thread (RCP for Thread Border Router), but there are currently no firmware images that support concurrent multiprotocol the combination of Zigbee Router and Thread, at least not with both protocols running simultaneously at the same time, and likely there never will as it does not really make commercial sense, (we can only speculate it might be products in the future that support Zigbee Router and Thread in the base firmware image but not enable both to run at the same time, meaning it will lock to only using the specific protocol that it is initially paired with).

So, there are currently no existing firmware images that feature both Zigbee Router and Thread. Your choices today is to use:

• Zigbee Router device firmware image to make it a dedicated Zigbee signal repeater.
• Zigbee NCP firmware image which is standard to make it a dedicated Zigbee Coordinator (or a dedicated Zigbee sniffer).
• OpenThread NCP firmware image to make it a dedicated Thread Border Router (running Thread features on the SoC).
• OpenThread RCP firmware image to make it a dedicated Thread Border Router (running Thread features on host computer).
• RCP Multi-PAN = Zigbee RCP + OpenThread RCP combination firmware image make it Zigbee Coordinator and Thread Border Router with both protocols running as daemons/services on the host computer (e.g. Silicon Labs multiprotocol add-on for Home Assistant which require the Zigbee gateway application to communicate with the Silabs daemon using a TCP/IP socket).
• Zigbee NCP + OpenThread RCP combo firmware image to make the Zigbee Coordinator NCP on the SoC which makes that part compatible with traditional Zigbee gateway application like Zigbee2MQTT and Thread Border Router on the host computer.

https://openthread.io/platforms/co-processor

The fact is there today exist these types of community firmware images for Silicon Labs EFR32MG21 based devices listed below:

• Zigbee Router = Mains-powered Zigbee Router Device (ZED) that act as a dedicated Zigbee Signal Repeater.
  • https://github.com/itead/Sonoff_Zigbee_Dongle_Firmware/tree/master/Dongle-E/Router
  • https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/Zigbee3.0_Dongle-NoSigned/RouterForDongle
• Zigbee NCP = The standard NCP (Network Co-Processor) design has Zigbee features on the SoC and runs the application layer on a host computer.
  • https://github.com/itead/Sonoff_Zigbee_Dongle_Firmware/tree/master/Dongle-E/NCP
  • https://github.com/NabuCasa/silabs-firmware/tree/main/EmberZNet
  • https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/Zigbee3.0_Dongle-NoSigned/EZSP
  • https://github.com/grobasoz/zigbee-firmware/
  • https://github.com/skgsergio/silabs-multiprotocol-firmware-zbgw04-usb/tree/main/firmware/ncp
• Thread NCP = The standard NCP (Network Co-Processor) design has Thread features on the SoC and runs the application layer on a host computer.
  • No community images for this yet I believe?
• Thread RCP =RCP (Radio Co-Processor) design where the core of OpenThread lives on the host computer with only a minimal MAC layer "controller" on the SoC with the Thread radio.
  • https://github.com/NabuCasa/silabs-firmware/tree/main/OpenThreadRCP
• RCP Multi-PAN = RCP (Radio Co-Processor) design with multi-protocol radio where the core of Zigbee and Thread is running on host computer with only minimal MAC layer "controllers" on the SoC with the radio capable of Zigbee Thread at the same time.
  • https://github.com/NabuCasa/silabs-firmware/tree/main/RCPMultiPAN
  • https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/Zigbee3.0_Dongle-NoSigned/RCPMultiPAN
  • https://github.com/skgsergio/silabs-multiprotocol-firmware-zbgw04-usb/tree/main/firmware

@golgoth73 again, there is currently no single firmware image from anyone in the that supports acting as a Zigbee Router and Thread device at the same time and I do not believe that is something that Silicon Labs EmberZNet SDK currently supports, however, if I had to guess then that might be something that could perhaps be added to Silicon Labs EmberZNet SDK in the future, or at least it is not technically impossible, even though it is not possible in practice if there is no support for in Silabs EmberZNet SDK.

[Hedda]

Is it possible to use the web flasher to update a EFR32MG13 dongle (Zigbee Popp) ?

You can find firmware images for Elelabs ELU013 and POPP ZB-STICK (701554) in GBL file format on Elelabs GitHub repository:

https://github.com/Elelabs/elelabs-zigbee-ezsp-utility/tree/master/data/EFR32MG13

POPP ZB-STICK (701554) is a white-label (rebranded) version of Elelabs ELU013 that is made by Elelabs based on EFR32MG13P

Older variants of Elelabs adapters did however ship with EBL (Ember Bootloader) and if that is the case then you can not flash those yet with the webflashing as it does so far not suppose EBL parting. More info here -> https://github.com/NabuCasa/universal-silabs-flasher/pull/11

[shirou93]

Hi, migrate from sonoff P to E in homeassistant will drop devices on zigbee2mqtt? I have many changed entity names etc. When zigbee2mqtt drop devices they will disappear on HA GUI or change to unavailable? I dont't want reconfigure all names in HA. Thanks for advice.

[timlunn447]

@shirou93, Migration to the -E is not officially supported in Zigbee2MQTT yet. There are probably workarounds to make it work, but not likely well tested or documented anywhere.

It is possible to keep your existing network in Zigbee2MQTT using the -P, and then create a new network with the Multiprotocol addon and ZHA on the -E. These can then co-exist and you can use the new network for testing. We would recommend this route over migrating your production network at this stage.

However back to the migration, keeping in mind we have not tested any of this. So make to sure to backup your coordinator.json file before trying anything!

Normally switching to a new (different type) coordinator in Zigbee2MQTT requires repairing all devices.

Migration from Zigbee2MQTT to ZHA is possible but you will almost certainly loose your entity names in this case https://skyconnect.home-assistant.io/migrate-zigbee-zha/

It is probably possible to use zigpy-cli to restore a backup of your existing network onto the new -E dongle, clone the IEEE address (both these are done automatically in the above step). Then point Zigbee2MQTT to the new adaptor which if you are using the multiprotocol addon is covered here. That should keep all your existing names intact, but again not something we have tested.

[Hedda]

migrate from sonoff P to E in homeassistant will drop devices on zigbee2mqtt

Wrong place to ask, suggest instead ask in this Zigbee2MQTT discussion -> https://github.com/Koenkk/zigbee2mqtt/discussions/16478

[asmiller]

Or can I flash the sonoff with zigbee router and thread ?

No its not possible for these two functions to co-exist.

So if I want to support both Thread and Zigbee devices, I still need two adapters - one to flash as a router for Zigbee and one to flash as a router for Thread?

[timlunn447]

So if I want to support both Thread and Zigbee devices, I still need two adapters

You can have both Thread and Zigbee Coordinator on the one adapter, at the same time. A Zigbee Router is a different device that is used to extend your Zigbee mesh network.

[Hedda]

I still need two adapters - one to flash as a router for Zigbee and one to flash as a router for Thread?

@asmiller That question was already asked and answered above so I updated my reply to make it more clear -> https://github.com/DialedIn-Aus/blogComments/issues/3#issuecomment-1562711493

Again I believe you guys are confusing "Zigbee Router" with "Zigbee Coordinator" because name of "Thread Border Router". Read:

https://www.home-assistant.io/integrations/zha#introduction

ZHA integration is a Zigbee gateway implementation that follows the standard Zigbee 3.0 specification (and earlier revisions). In Zigbee, there are three different device types: Zigbee Coordinator (ZC), Zigbee Router (ZR), and Zigbee End Device (ZED). A Zigbee network always has one (and no more) Zigbee Coordinator, however, a Zigbee network can have multiple Zigbee Routers and multiple Zigbee End Devices.

A Zigbee Coordinator is the central device in a Zigbee network that manages and controls the network. It acts as a physical interface for the Zigbee wireless protocol, as well as being responsible for maintaining the Zigbee network topology and ensuring secure and efficient communication between Zigbee devices. Zigbee Router devices are mains-powered and will act as Zigbee signal repeaters within the Zigbee network mesh to extend its range and improve coverage, while Zigbee End Device devices are usually battery-operated sensors that will not act as Zigbee signal repeaters.

In the case of ZHA, the Zigbee Coordinator is a radio adapter or hardware module, that contains a microcontroller that runs the Zigbee protocol stack which the ZHA integration uses to manage and communicate with a Zigbee network and its devices.

Before installing the ZHA integration, you will need to buy and connect a Zigbee Coordinator radio adapter or hardware module, those usually come in the form of a USB dongle that plugs directly into the computer that is running the Home Assistant installation. The ZHA integration can work with many different “Zigbee Coordinator” adapters, however, be sure to read the respective sections below about compatible Zigbee radio adapters and hardware modules.

Once ZHA has been set up and the Zigbee Coordinator radio adapter or module is configured, you will be able to directly join/pair any Zigbee device to the Zigbee network; regardless of the manufacturer and brand of that Zigbee-based product. Note, that while it is generally recommended to buy Zigbee 3.0 compliant devices as those should, in theory, offer greater interoperability, be sure of the sections about which devices are supported and exception handling.

[clowg]

Do you have to do something special to get the Sonoff-E to show up in the SilLabs Multiprotocol add-on Configuration page? I have the dongle plugged into a USB port on my HA server, and I have rebooted the system. I am running HA 2023.7.2 on HAOS 10.3 on X64. However, I only see the 4 /dev/tty devices in the Config page.

[darkxst]

@clowg Nothing special required, it should show up in the config page even it has the incorrect firmware on it.

What type of HA install are you running? If running in a VM (or Docker) you will need to pass the serial device through to the VM.

[clowg]

I flashed the multi protocol firmware on to it using my Windows PC first. That all went fine.

Geoff

---

From: Tim L @.> Sent: Monday, July 17, 2023 1:41:06 PM To: DialedIn-Aus/blogComments @.> Cc: Geoff Clow @.>; Mention @.> Subject: Re: [DialedIn-Aus/blogComments] Flashing the Sonoff ZBDongle-E to enable Matter, Thread and Zigbee on Home Assistant | Dialedin (Issue #3)

@clowghttps://github.com/clowg Nothing special required, it should show up in the config page even it has the incorrect firmware on it.

— Reply to this email directly, view it on GitHubhttps://github.com/DialedIn-Aus/blogComments/issues/3#issuecomment-1637272121, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEZ6NGKKSPW54GKTVHG7M7TXQSJ3FANCNFSM6AAAAAAXWULIKI. You are receiving this because you were mentioned.Message ID: @.***>

[darkxst]

The config page doesnt know anything about firmware. It should show any serial devices connected to your server. If you are running in a VM, check that serial device is passed through.

If you have the HA terminal addon you can run lsusb and check for the following ID ID 1a86:55d4

[clowg]

Thanks Will check that command.

My HA install is HAOS on x64 bare-metal.

Geoff ____ From: Tim L @.> Sent: Monday, July 17, 2023 2:24:19 PM To: DialedIn-Aus/blogComments @.> Cc: Geoff Clow @.>; Mention @.> Subject: Re: [DialedIn-Aus/blogComments] Flashing the Sonoff ZBDongle-E to enable Matter, Thread and Zigbee on Home Assistant | Dialedin (Issue #3)

The config page doesnt know anything about firmware. It should show any serial devices connected to your server. If you are running in a VM, check that serial device is passed through.

If you have the terminal addon you can run lsusb and check for the following ID ID 1a86:55d4

— Reply to this email directly, view it on GitHubhttps://github.com/DialedIn-Aus/blogComments/issues/3#issuecomment-1637293303, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEZ6NGOMENV4JXDUFKSVV53XQSO5HANCNFSM6AAAAAAXWULIKI. You are receiving this because you were mentioned.Message ID: @.***>

[clowg]

mmm... that device doesn't appear.

I wonder if it needs to be plugged into a USB2 port? That's the only thing I can think of that I can change.

[clowg]

[darkxst]

I wonder if it needs to be plugged into a USB2 port?

It is recommended to use a USB2 port and USB extension cable to help avoid interference, but that wont have any impact on the device showing up or not.

Are you running HAOS in a VM or on bare metal?

[clowg]

It’s on bare metal

[darkxst]

It’s on bare metal

Very strange, the USB Device should just show up as soon as its plugged in. All I can think of is a connection issue (not plugged in fully?) or a dead USB port. Maybe try some other USB device and see if that gets detected?

[clowg]

Fixed it. Removed dongle and put into USB2 socket. Appeared straight away! Thanks for you help.

[Hedda]

FYI, the ITead's Sonoff dongles are known to have extremely a short USB plug design so may therefore not work in all USB-ports because it does not get a physical connection due to its very short USB plug, as in it does not plug all the way into the port to make proper connection.

Workaround is to try to use USB extension cable as most of those have a longer USB port that will make a proper connection, An alternative is to try to connect the ITead's Sonoff dongle without its enclosure as that give you a another millimetre or so.

Another alternative to that some peaple done is to modify the computer chassi of the comouter by cutting away a piece around the USB port so that the Sonoff dongle can be plugged further in.

[Dwouglaz]

Thank you very much! everything worked perfectly, very simple and straightforward, just plug it in and update, I was surprised that the firmware and all the information already appeared, thank you very much for your work

[clowg]

Do you have to re-pair your zigbee devices after updating the firmware to the latest version?

[darkxst]

@clowg if your just updating to the latest version of the multipan firmware there is no need to re-pair any devices.

Only on first install when migrating from EZSP zigbee firmware to multipan you might need to re-pair (ZHA can handle this migration though, Z2M is complicated...)

[Hedda]

Do you have to re-pair your zigbee devices after updating the firmware to the latest version?

Normally not, sometimes you may need to power-cycle some devices if they do not reconnect automatically within a few hours (usually mains powered devices become available again within minutes while battery-powered devices can take longer unless a state change is forced), but it is highly recommended to make a backup by upgrading firmware.

If using ZHA then backups are always made automatically. If using Zigbee2MQTT then it currently only supports backup + restore for Texas Instruments Z-Stack/ZNP based adapters and not yet EZSP (though there is a zigbee-herdsman developer that has started to look at it recently).

You can use zigpy-cli to perform manual backups if you stop your Zigbee implementation -> https://github.com/zigpy/zigpy-cli

[clowg]

Thanks guys. The firmware upgrade went well, and rather than waiting I power-cycled my few devices - then the zb map came up quickly.

[clowg]

I've been having problems with my Tuya M100 mmWave presence sensor. It stops changing from Away to Home - even though other data points are changing (lux and Target distance). Thought I better get the latest firmware as part of the troubleshooting process. I'm using Z2M and the SilLabs Multiprotocol addon with HA.

[phenates]

Hi, i am encoutering a problen during the zigbee2mqtt add-on start. All the previous step seem's to be ok. HA run on VM, the ZBDongle-E flashed with the web flasher and is correctly reconized by HA, Silabs Multiprotocol add-on start without error, but i have a error (Error while starting zigbee-herdsman) during the start of zigbee2mqtt. For information, with the factory firmware there is no error on zigbee2mqtt.

Silabs Multiprotocol log:

s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[14:24:43] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
s6-rc: info: service cpcd successfully started
s6-rc: info: service zigbeed: starting
s6-rc: info: service otbr-agent: starting
s6-rc: info: service zigbeed successfully started
[14:24:43:569942] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[14:24:43:570119] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch: 
[14:24:43:570123] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[14:24:43:570131] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[14:24:43:570322] Info : Reading cli arguments
[14:24:43:570336] Info : /usr/local/bin/cpcd 
[14:24:43:573931] Info : Reading configuration
[14:24:43:573952] Info :   file_path = /usr/local/etc/cpcd.conf
[14:24:43:573955] Info :   instance_name = cpcd_0
[14:24:43:573957] Info :   socket_folder = /dev/shm
[14:24:43:573959] Info :   operation_mode = MODE_NORMAL
[14:24:43:573961] Info :   use_encryption = false
[14:24:43:573963] Info :   binding_key_file = /etc/binding-key.key
[14:24:43:573965] Info :   stdout_tracing = false
[14:24:43:573966] Info :   file_tracing = false
[14:24:43:573968] Info :   lttng_tracing = false
[14:24:43:573970] Info :   enable_frame_trace = false
[14:24:43:573971] Info :   traces_folder = /dev/shm/cpcd-traces
[14:24:43:573973] Info :   bus = UART
[14:24:43:573975] Info :   uart_baudrate = 460800
[14:24:43:573977] Info :   uart_hardflow = false
[14:24:43:573978] Info :   uart_file = /dev/ttyACM0
[14:24:43:573980] Info :   fu_recovery_pins_enabled = false
[14:24:43:573982] Info :   fu_connect_to_bootloader = false
[14:24:43:573984] Info :   fu_enter_bootloader = false
[14:24:43:573986] Info :   restart_cpcd = false
[14:24:43:573987] Info :   application_version_validation = false
[14:24:43:573989] Info :   print_secondary_versions_and_exit = false
[14:24:43:573991] Info :   use_noop_keep_alive = false
[14:24:43:573993] Info :   reset_sequence = true
[14:24:43:573994] Info :   stats_interval = 0
[14:24:43:573996] Info :   rlimit_nofile = 2000
[14:24:43:573998] Info : ENCRYPTION IS DISABLED 
[14:24:43:574032] Info : Starting daemon in normal mode
[14:24:43:600319] Info : Connecting to Secondary...
[14:24:43:682644] Info : RX capability is 256 bytes
[14:24:43:682674] Info : Connected to Secondary
[14:24:43:685953] Info : Secondary Protocol v4
[14:24:43:694952] Info : Secondary CPC v4.3.1
[14:24:43:698150] Info : Secondary bus bitrate is 460800
[14:24:43:706038] Info : Secondary APP vUNDEFINED
[14:24:43:706287] Info : Daemon startup was successful. Waiting for client connections
[14:24:44] INFO: Starting zigbeed...
[14:24:45] INFO: Setup OTBR firewall...
[14:24:46:044452] Info : New client connection using library v4.3.1.0
[14:24:46:053404] Info : Opened connection socket for ep#12
[14:24:46:054303] Info : Endpoint socket #12: Client connected. 1 connections
[14:24:47] INFO: Starting otbr-agent...
otbr-agent[313]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[313]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[313]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[313]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[313]: [NOTE]-ILS-----: Infra link selected: enp0s3
otbr-agent[313]: 49d.17:12:33.053 [C] Platform------: mCpcBusSpeed = 115200
otbr-agent[313]: 00:00:00.123 [N] RoutingManager: BR ULA prefix: fd4e:acfd:aa69::/48 (loaded)
otbr-agent[313]: 00:00:00.125 [N] RoutingManager: Local on-link prefix: fd12:2f1b:5381:31b6::/64
otbr-agent[313]: 00:00:00.234 [N] Mle-----------: Role disabled -> detached
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[14:24:48:079534] Info : New client connection using library v4.3.1.0
[14:24:48:084121] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[313]: 00:00:00.418 [N] Platform------: [netif] Changing interface state to up.
Listening on port 9999 for connection...

Accepting connection.

[14:24:50] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
otbr-agent[313]: 00:00:27.163 [N] Mle-----------: RLOC16 8c00 -> fffe
otbr-agent[313]: 00:00:27.169 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[313]: 00:00:27.851 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[313]: 00:00:34.354 [N] RouterTable---: Allocate router id 35
otbr-agent[313]: 00:00:34.354 [N] Mle-----------: RLOC16 fffe -> 8c00
otbr-agent[313]: 00:00:34.363 [N] Mle-----------: Role detached -> leader
otbr-agent[313]: 00:00:34.364 [N] Mle-----------: Partition ID 0x5de8bc14
otbr-agent[313]: 00:00:35.227 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[313]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d449:3ff:fe98:9eaf/vethc3d7d80/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d449:3ff:fe98:9eaf/vethc3d7d80/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d449:3ff:fe98:9eaf/vethc3d7d80/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d449:3ff:fe98:9eaf/vethc3d7d80/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d449:3ff:fe98:9eaf/vethc3d7d80/33
Accepted connection 7.

Restarting
[14:26:32:752838] Info : Endpoint socket #12: Client disconnected. 1 connections
[14:26:32:752920] Info : Client disconnected
[14:26:33:758907] Info : New client connection using library v4.3.1.0
[14:26:33:765141] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.

Socket connection has been closed, restarting...

Listening on port 9999 for connection...

Accepting connection.

zigbee2mqtt log:

[14:26:01] INFO: Preparing to start...
[14:26:02] INFO: Socat not enabled
[14:26:06] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-09-23 14:26:31: Logging to console and directory: '/config/zigbee2mqtt/log/2023-09-23.14-26-31' filename: log.txt
Zigbee2MQTT:info  2023-09-23 14:26:31: Starting Zigbee2MQTT version 1.33.0 (commit #unknown)
Zigbee2MQTT:info  2023-09-23 14:26:31: Starting zigbee-herdsman (0.18.5)
Zigbee2MQTT:error 2023-09-23 14:26:46: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-09-23 14:26:46: Failed to start zigbee
Zigbee2MQTT:error 2023-09-23 14:26:46: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-09-23 14:26:46: Exiting...
Zigbee2MQTT:error 2023-09-23 14:26:47: Error: Failure send version:{"type":"Buffer","data":[1,0,1,0,0,12]}
    at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:562:23
    at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)

Thanks for your help.

[darkxst]

Accepted connection 7.

That looks like something connected, is perhaps ZHA also trying to connect to Silabs Multiprotocol?

Also can you post the Z2M Configs?

[phenates]

Thanks for your response. ZHA was previously installed and used with another zigbee dongle, but i have uninstall it.

Z2M conf:

[darkxst]

I'm not sure what else could be wrong everything else looks ok above.

[sapstar]

The darkxst flashing process was really simple and thanks for building this great too. I flashed my Sonoff Dongle E today with the multi pan firmware and was able to migrate my ZHA network and import it back. Everything was working for a few mins. After that the ZHA lost connection to the coordinator and would never connect even after restarts of HA.

I see these errors in the multi protocol addon. Would someone be able to help me resolve this?

MULTI PROTOCOL ADDON LOGS:
[09:57:27:999848] Info : Connecting to Secondary...
[09:57:30:000035] Info : Failed to connect, secondary seems unresponsive

HOME ASSISTANT LOGS:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 209, in async_initialize
    await self.application_controller.startup(auto_form=True)
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 201, in startup
    await self.shutdown()
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 406, in shutdown
    await self._dblistener.shutdown()
  File "/usr/local/lib/python3.11/site-packages/zigpy/appdb.py", line 187, in shutdown
    await self._set_isolation_level(None)
  File "/usr/local/lib/python3.11/site-packages/zigpy/appdb.py", line 205, in _set_isolation_level
    await self._db._execute(lambda: setattr(self._db, "isolation_level", level))
  File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 126, in _execute
    raise ValueError("Connection closed")
ValueError: Connection closed
2023-10-04 09:56:46.035 ERROR (MainThread) [zigpy.application] Couldn't start application
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 197, in startup
    await self.connect()
  File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 141, in connect
    await ezsp.startup_reset()
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 159, in startup_reset
    await self.reset()
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 185, in reset
    await self._gw.reset()
TimeoutError

[Hedda]

@sapstar that is off-topic here to, please stick to your existing thread instead of shutgun spamming this is all placed that is even slighly related on a tangent -> https://community.home-assistant.io/t/migrating-zigbee-devices-from-sonoff-dongle-e/621863

[Hedda]

@darkxst FYI, thought it might interest you to know that Aeotec Zi-Stick (model “ZGA008”) and SMLIGHT SLZB-07 are two new EFR32MG21 + CP2102N based adapters on the market (and SMLIGHT SLZB-07 is currently being sold at a low promotional price)

[LightMoon]

How can set it up not to run as a root?

[darkxst]

You don't need to worry about that, its running in its own container, so doesnt have root for entire system.

[tirreni8a]

Hope someone of you can help me on this. I have installed the "CH343SER" drivers on my Windows pc, then rebooted. when trying to use the webflasher https://darkxst.github.io/silabs-firmware-builder/ , the popup with mydongle appears, allow the connection but then it remains stuck on the connection.... What do you suggest to do ? consider I have already restarted many times, re-installed drivers many times... Hope someone have some idea to solve it thanks!

[darkxst]

Do you have anything that would block download of javascript files, such as pihole or privacy extensions?

EDIT: Actually seems to be some other issue with the webflasher currently, looking into it.

[LightMoon]

Hope someone of you can help me on this. I have installed the "CH343SER" drivers on my Windows pc, then rebooted. when trying to use the webflasher https://darkxst.github.io/silabs-firmware-builder/ , the popup with mydongle appears, allow the connection but then it remains stuck on the connection.... What do you suggest to do ? consider I have already restarted many times, re-installed drivers many times... Hope someone have some idea to solve it thanks!

Internet Download manager was in way on mine. Try Incognito mode with no extensions enabled.

[darkxst]

Its something different this time! Need to wait for this to be fixed. https://github.com/NabuCasa/sl-web-tools/issues/11

[tirreni8a]

Hi @darkxst thanks for the fix. it worked now. But I've realized that if I flash the Router firmware then the webflasher doesn't recognize it anymore... To let recognize it, I have to flash it with the Coordinator firmware with the SONOFF's way...

Thanks

[darkxst]

The webflasher doesnt recognise the router firmware, but you can use universal-silabs-flasher directly to force bootloader reset and flash (without disassembly)

universal-silabs-flasher --device /dev/ttyACM0 flash --firmware <file.gbl> --sonoff-reset

[Loky31]

Hello, the web flash does not work for me :(

2024-02-15 21:44:56 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-02-15 21:44:56 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (115200 baudrate) 2024-02-15 21:44:56 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1b9e310> 2024-02-15 21:44:56 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xf0' 2024-02-15 21:44:56 emscripten universal_silabs_flasher.gecko_bootloader[42] DEBUG Parsing State.WAITING_FOR_MENU: bytearray(b'\xf0') 2024-02-15 21:44:56 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'3' 2024-02-15 21:44:58 emscripten webserial_transport[42] DEBUG Closing serial port 2024-02-15 21:44:58 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC at 460800 baud 2024-02-15 21:44:58 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (460800 baudrate) 2024-02-15 21:44:58 emscripten webserial_transport[42] DEBUG Closed serial port 2024-02-15 21:44:58 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1bdc670> 2024-02-15 21:44:58 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-02-15 21:44:58 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-02-15 21:44:59 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'x' 2024-02-15 21:44:59 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x00' 2024-02-15 21:44:59 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-02-15 21:45: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-02-15 21:45: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-02-15 21:45:00 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x80' 2024-02-15 21:45:00 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xf8\x00x\x80\x00\x80\x00\xf8\xf8\x80\xf8\xf8x\xf8' 2024-02-15 21:45:00 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to parse buffer bytearray(b'\xf8'): ValueError('Invalid flag') 2024-02-15 21:45: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 2 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45: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 3 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45: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 4 of 4) 2024-02-15 21:45:03 emscripten webserial_transport[42] DEBUG Closing serial port 2024-02-15 21:45:03 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC at 115200 baud 2024-02-15 21:45:03 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (115200 baudrate) 2024-02-15 21:45:03 emscripten webserial_transport[42] DEBUG Closed serial port 2024-02-15 21:45:03 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x134ce08> 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45:03 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x11' 2024-02-15 21:45: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 1 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45:04 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x1a' 2024-02-15 21:45:04 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xc1\x02\x02\x9b{~' 2024-02-15 21:45:04 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to parse buffer bytearray(b'~'): ValueError('Invalid flag') 2024-02-15 21:45: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 2 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45:06 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-02-15 21:45:06 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-02-15 21:45:06 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-02-15 21:45: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 4 of 4) 2024-02-15 21:45:07 emscripten webserial_transport[42] DEBUG Closing serial port 2024-02-15 21:45:07 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC at 230400 baud 2024-02-15 21:45:07 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (230400 baudrate) 2024-02-15 21:45:07 emscripten webserial_transport[42] DEBUG Closed serial port 2024-02-15 21:45:07 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1b9eea0> 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45:07 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x06' 2024-02-15 21:45:07 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xe0' 2024-02-15 21:45: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 1 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45:08 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x98' 2024-02-15 21:45:08 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xe0\x06\x18\x18\x9e\xf8\x9e\x86\xfe' 2024-02-15 21:45:08 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to parse buffer bytearray(b'\xfe'): ValueError('Invalid flag') 2024-02-15 21:45: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 2 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45: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 3 of 4) 2024-02-15 21:45: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-02-15 21:45: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-02-15 21:45: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 4 of 4) 2024-02-15 21:45:11 emscripten webserial_transport[42] DEBUG Closing serial port 2024-02-15 21:45:11 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.EZSP at 115200 baud 2024-02-15 21:45:11 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (115200 baudrate) 2024-02-15 21:45:11 emscripten webserial_transport[42] DEBUG Closed serial port 2024-02-15 21:45:11 emscripten bellows.ezsp[42] DEBUG Resetting EZSP 2024-02-15 21:45:11 emscripten bellows.uart[42] DEBUG Resetting ASH 2024-02-15 21:45:11 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e' 2024-02-15 21:45:13 emscripten bellows.uart[42] DEBUG RSTACK Version: 2 Reason: RESET_POWER_ON frame: b'c102029b7b7e' 2024-02-15 21:45:13 emscripten bellows.ezsp[42] INFO NCP entered failed state. No application handler registered, ignoring... 2024-02-15 21:45:17 emscripten bellows.uart[42] DEBUG Connection lost: None 2024-02-15 21:45:17 emscripten bellows.uart[42] DEBUG Closed serial connection 2024-02-15 21:45:17 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.SPINEL at 460800 baud 2024-02-15 21:45:17 emscripten zigpy.serial[42] DEBUG Opening a serial connection to '/dev/webserial' (460800 baudrate) 2024-02-15 21:45:17 emscripten webserial_transport[42] DEBUG Closing serial port 2024-02-15 21:45:17 emscripten webserial_transport[42] DEBUG Closed serial port 2024-02-15 21:45:17 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1b7b230> 2024-02-15 21:45:17 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-02-15 21:45:17 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~' 2024-02-15 21:45:17 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'x' 2024-02-15 21:45:17 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x00' 2024-02-15 21:45:18 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-02-15 21:45:18 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-02-15 21:45:18 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~' 2024-02-15 21:45:18 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\x80' 2024-02-15 21:45:18 emscripten universal_silabs_flasher.common[42] DEBUG Received data b'\xf8\x00x\x80\x00\x80\x00\xf8\xf8\x80\xf8\xf8x\xf8' 2024-02-15 21:45:19 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-02-15 21:45:19 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-02-15 21:45:19 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~' 2024-02-15 21:45:20 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-02-15 21:45:20 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-02-15 21:45:20 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'~\x83\x02\x02\xe65~' 2024-02-15 21:45:21 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-02-15 21:45:21 emscripten webserial_transport[42] DEBUG Closing serial port 2024-02-15 21:45:21 emscripten webserial_transport[42] DEBUG Closed serial port

Don't know at which point it went wrong and why... any idea?

[darkxst]

It may be a permission error, if you are on Linux you need to add your user to the dialout group.