# Dongle-M firmware Release Notes **URL:** \ **Category:** Dongle Series\ **Created:** [February 10, 2026, 10:38am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603 "2026-02-10T10:38:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![MichaelLearnsToCode](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/michaellearnstocode/32/1668_2.png) [@MichaelLearnsToCode](https://forum.ewelink.cc/u/MichaelLearnsToCode)\ **Post date:** [February 10, 2026, 10:38am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/1 "2026-02-10T10:38:55Z")
# ESP32-D0WDR2-V3 firmwares ## v1.0.6 beta 1. Ping RTT (Round Trip Time) over Wi-Fi is reduced from 100ms to about 10ms. 2. UART over TCP data forwarding efficiency has been significantly improved. 3. Several bug fixes. [donglem\_esp32\_beta\_1.0.6\_115200.bin](https://forum.ewelink.cc/uploads/short-url/oggDb3nl6bJ0t0bCvH5Odjy9FZZ.bin) (2.2 MB) ## v1.0.7 beta 1. Bug fix: Static IP doesn’t funtion properly when DHCP server is unavailable. 2. Bug fix: Changing the AP password doesn’t take effect when the AP is disabled. [donglem\_esp32\_beta\_1.0.7\_115200.bin](https://forum.ewelink.cc/uploads/short-url/bc36AhHxeaXwK9cvR0a3Q91aioK.bin) (2.2 MB) _Note: to manually update the firmware of ESP32-D0WDR2-V3, please go to `Dongle-M Web UI -> firmware -> ESP32-D0WDR2-V3 -> Upload & Flash Firmware`._ ![ESP32_Upload_Flash_Firmware](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/9/918f5a92eb4bc4fc8d82dfadd992444935b8d111.png) ## v1.0.8 beta 1. UART over TCP connection stability has been significantly improved. 2. Bug fix: Static IP automatically changes to Smart IP after reboot when Static IP is not within the IP range of the DHCP service. [donglem\_esp32\_beta\_1.0.8\_115200\_ota.bin](https://forum.ewelink.cc/uploads/short-url/nvnF9a9jrfdVDwpXtDfHtdiaSqu.bin) (1.9 MB) ## v1.0.9 beta 1. Add support for modifying AP SSID. 2. Add support for modifying Hostname which also modifies mDNS name. 3. When multiple routers use the same SSID, connect to the one with the strongest signal. 4. Some other minor improvements. [donglem\_esp32\_beta\_1.0.9\_115200\_ota.bin](https://forum.ewelink.cc/uploads/short-url/yzithrhuKBJax4ac9laoXssjnHg.bin) (1.9 MB) ## v1.0.10 beta 1. Support more AP configuration options: Hide SSID, IPv4 Address, Operating Frequency. 2. Support more Notification message types and deleting all messages. 3. Bug fix: WireGuard Endpoint doesn’t work with domain name. [donglem\_esp32\_beta\_1.0.10\_115200\_ota.bin](https://forum.ewelink.cc/uploads/short-url/ukGzysODBZ0RPLwrFPOyrhlUUPN.bin) (1.9 MB) * * * # EFR32MG24 firmwares ## Zigbee Coordinator v7.4.5 stable (factory default) [zigbee\_ncp\_uart\_hw\_donglem\_v7.4.5.gbl](https://forum.ewelink.cc/uploads/short-url/xpoAcAdJLxbujbp7uSVCT2TsiE4.gbl) (245.9 KB) ## Zigbee Coordinator v8.2.2 beta [zigbee\_ncp\_uart\_hw\_donglem\_v8.2.2.0.gbl](https://forum.ewelink.cc/uploads/short-url/vtrvlrTk0zAEOyCDJ2RVifHVu6g.gbl) (230.1 KB) _Note: to manually update the firmware of EFR32MG24, please go to `Dongle-M Web UI -> firmware -> EFR32MG24 -> Upload & Flash Firmware`._ ![MG24_Upload_Flash_Firmware](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/b/bfd89ab327e3b30b7c940570b3e9b9d96e13bdae.png) ---
**Author:** ![MichaelLearnsToCode](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/michaellearnstocode/32/1668_2.png) [@MichaelLearnsToCode](https://forum.ewelink.cc/u/MichaelLearnsToCode)\ **Post date:** [February 10, 2026, 10:46am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/2 "2026-02-10T10:46:39Z")
---
**Author:** ![Derex](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/derex/32/9475_2.png) [@Derex](https://forum.ewelink.cc/u/Derex)\ **Post date:** [March 29, 2026, 7:28pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/3 "2026-03-29T19:28:18Z")
![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/8/8b65b1137622ffd603121ed3887d09f304801a1d.png) ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/9/95e14e58b30d51f11644019efaff97fc4c9688a1.png) Hi @MichaelLearnsToCode , just wanted to ask, is my firmware on the latest stable versions ? I noticed i do get randomly new ip assigned without doing anything. ---
**Author:** ![MichaelLearnsToCode](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/michaellearnstocode/32/1668_2.png) [@MichaelLearnsToCode](https://forum.ewelink.cc/u/MichaelLearnsToCode)\ **Post date:** [March 30, 2026, 8:26am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/4 "2026-03-30T08:26:54Z")
Hi, your Dongle-M is running v1.0.7 stable firmware, the latest beta is v1.0.8. You can update Dongle-M to v1.0.8 beta. IP `169.254.232.8` is a Link-local address which is automatically assigned to host (Dongle-M) when host’s DHCP requests fails. But host will retry, so you can see a normal LAN IP `192.168.1.123` is assigned later. We will look into it to see if there is anything wrong with the firmware. ---
**Author:** ![Derex](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/derex/32/9475_2.png) [@Derex](https://forum.ewelink.cc/u/Derex)\ **Post date:** [March 30, 2026, 9:08am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/5 "2026-03-30T09:08:06Z")
Thank you for the explanation, this makes sense ! I will continue monitoring it and let you know. ---
**Author:** ![rnizametdinov](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@rnizametdinov](https://forum.ewelink.cc/u/rnizametdinov)\ **Post date:** [May 21, 2026, 5:56pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/6 "2026-05-21T17:56:58Z")
> [@MichaelLearnsToCode](#): > > ## Zigbee Coordinator v8.2.2 beta Any changelog for this update? And how get back to factory fw, there to download, want make it through web interface. I dont want use **SONOFF Dongle Flasher** (my Dongle-M connected by POE ethernet, so only web interface usable for update ) Can you post direct link for all actual EFR32MG24 firmwares ---
**Author:** ![Derex](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/derex/32/9475_2.png) [@Derex](https://forum.ewelink.cc/u/Derex)\ **Post date:** [May 26, 2026, 12:30pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/7 "2026-05-26T12:30:44Z")
Hi @MichaelLearnsToCode , i would like to report some issues with the Sonoff Dongle-M in router mode. I have a home assistant server with a Home Assistant ZBT-2 as the main coordinator using Zigbee2MQTT. And i had setup the Sonoff Dongle Max in zigbee router mode, and it does not work to connect 3rd party devices through it. For example i am trying to connect some Aqara Window sensors , but it does not work through the Dongle M. I also have some Sonoff S60ZBTPF plugs which works perfectly as routers in my system. Just the Dongle M does not work as a router. I had tried the stable firmware 1.0.7 and does not work, and i had also tried 1.0.10 beta firmware and same issue. ---
**Author:** ![MichaelLearnsToCode](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/michaellearnstocode/32/1668_2.png) [@MichaelLearnsToCode](https://forum.ewelink.cc/u/MichaelLearnsToCode)\ **Post date:** [May 27, 2026, 1:22pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/8 "2026-05-27T13:22:01Z")
> [@rnizametdinov](#): > > Any changelog for this update? Please refer to [Zigbee Version 8.2 Revision 2 (September 24, 2025) - Release Notes](https://docs.silabs.com/zigbee/8.2.2/sisdk-zigbee-release-notes/#zigbee-version-8-2-revision-2-september-24-2025-release-notes) > [@rnizametdinov](#): > > And how get back to factory fw, there to download, want make it through web interface. [zigbee\_ncp\_uart\_hw\_donglem\_v7.4.5.gbl](https://forum.ewelink.cc/uploads/short-url/xpoAcAdJLxbujbp7uSVCT2TsiE4.gbl) (245.9 KB) > [@rnizametdinov](#): > > Can you post direct link for all actual EFR32MG24 firmwares. For Dongle-M, we currently only have v7.4.5 and v8.2.2 beta available. We plan to provide v8.2.3 with 115200, 460800, 921600 baudrate ASAP. ---
**Author:** ![MichaelLearnsToCode](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/michaellearnstocode/32/1668_2.png) [@MichaelLearnsToCode](https://forum.ewelink.cc/u/MichaelLearnsToCode)\ **Post date:** [May 27, 2026, 1:30pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/9 "2026-05-27T13:30:08Z")
> [@Derex](#): > > For example i am trying to connect some Aqara Window sensors , but it does not work through the Dongle M. What do you mean by it does not work? - Do you mean that Dongle-M as a Zigbee router could not be added to your Zigbee network managed by Zigbee2MQTT? - Or Dongle-M can be added to Zigbee2MQTT but is not labeled as a Zigbee router? - Or it all looks good for Dongle-M in Zigbee2MQTT, but no other Zigbee devices are connected to Dongle-M (as a Zigbee router) in Zigbee2MQTT’s network topology? ---
**Author:** ![Derex](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/derex/32/9475_2.png) [@Derex](https://forum.ewelink.cc/u/Derex)\ **Post date:** [May 27, 2026, 3:46pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/10 "2026-05-27T15:46:25Z")
Hi @MichaelLearnsToCode . The issue is the 3rd variant: it all looks good for Dongle-M in Zigbee2MQTT, but no other Zigbee devices are connected to Dongle-M (as a Zigbee router) in Zigbee2MQTT’s network topology. Also when i press “Permit join” in Zigbee2Mqtt and i select Dongle-M, the end device does not connect. If i select for example another router like sonoff plug, or coordinator, that device connects. ---
**Author:** ![Derex](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/derex/32/9475_2.png) [@Derex](https://forum.ewelink.cc/u/Derex)\ **Post date:** [May 27, 2026, 4:42pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/11 "2026-05-27T16:42:07Z")
I had sorted out now, i had re-flashed Zigbee router firmware and factory reset dongle-m and i was able to add the devices after that. ---
**Author:** ![SuiKa](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/suika/32/8656_2.png) [@SuiKa](https://forum.ewelink.cc/u/SuiKa)\ **Post date:** [May 28, 2026, 1:03pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/12 "2026-05-28T13:03:05Z")
We tried to reproduce the issue. When using **-M** with the **V1.0.7 stable** firmware, we were able to add end devices successfully. ![29c7a3739058e4079492ee73aee407c8](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/5/57fd16cd59da63118bea2d825be5aac5e49ed064.png) ![14a33e7f8ce4ad82398020b17c3bb6f9](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/0/06c5b9a5ea05c46414e4d9763211b3b753dcb63d.png) ---
**Author:** ![ayun](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@ayun](https://forum.ewelink.cc/u/ayun)\ **Post date:** [May 28, 2026, 2:09pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/13 "2026-05-28T14:09:49Z")
What is the tool / site that you use in your screenshots, which can show device recent activity in the first image and can show legend in the second image ? I am not familiar with it, I am sure that: it is not the dongle-m zigbee2MQTT web interface. ---
**Author:** ![SuiKa](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/suika/32/8656_2.png) [@SuiKa](https://forum.ewelink.cc/u/SuiKa)\ **Post date:** [May 28, 2026, 2:24pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/14 "2026-05-28T14:24:26Z")
The screenshot is from zigbee2mqtt. ---
**Author:** ![ayun](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@ayun](https://forum.ewelink.cc/u/ayun)\ **Post date:** [May 28, 2026, 5:42pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/15 "2026-05-28T17:42:24Z")
How to enable that frontend / dashboard in the dongle-m ? ---
**Author:** ![rnizametdinov](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@rnizametdinov](https://forum.ewelink.cc/u/rnizametdinov)\ **Post date:** [May 28, 2026, 10:34pm UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/16 "2026-05-28T22:34:10Z")
This is z2mqtt interface on home assistant ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [June 15, 2026, 8:50am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/17 "2026-06-15T08:50:38Z")
@ [MichaelLearnsToCode](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/10 "Load parent post") I’ve noticed something in the firmware update panel and wanted to ask for clarification. Wouldn’t it make sense to remove the beta release notes once a stable firmware with the same version number is published? Right now the interface still shows the beta notes even though the corresponding stable version is already available. ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/f/f193f368d78a17624e38a37f0cf95dbef79db000.png) From a user’s perspective this doesn’t seem to serve any practical purpose, and it can even create confusion about which changes actually apply to the stable release. Is there a specific reason for keeping the beta notes visible? ---
**Author:** ![SuiKa](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/suika/32/8656_2.png) [@SuiKa](https://forum.ewelink.cc/u/SuiKa)\ **Post date:** [June 16, 2026, 5:55am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/18 "2026-06-16T05:55:12Z")
Thank you very much for your suggestion. We will take the old beta version offline as soon as possible. ---
**Author:** ![mikerocklewitz](https://avatars.discourse-cdn.com/v4/letter/m/6de8d8/32.png) [@mikerocklewitz](https://forum.ewelink.cc/u/mikerocklewitz)\ **Post date:** [September 3, 2026, 12:21am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/19 "2026-09-03T00:21:29Z")
Its obvious that the dongle max has issues over tcp/ethernet/wifi…apparently usb even > **[Bad experience with the Sonoff Dongle-M (Dongle Max)](https://community.home-assistant.io/t/bad-experience-with-the-sonoff-dongle-m-dongle-max/961105/262)** > > I did some test (helped with claude) @humingchun Subject: Dongle-M as network coordinator: NCP floods host with repeated identical ASH frames → BUSY / failed interviews — reproduced on 7.4.5, 8.2.2 AND 9.1.0 Setup SONOFF Dongle-M... I have weird issues as well with mine. So my question is simple…can we get a firmware for esp32 + zigbee ncp that eliminates all the extra junk? Make the esp32 a tcp bridge only. Me personally, i dont need a web page. I dont even want wifi to work. I just want poe, DHCP gives static ip based on router rules. None of the stuff that it is now. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 3, 2026, 8:46am UTC](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603/20 "2026-09-03T08:46:33Z")
> [@mikerocklewitz](#): > > I have weird issues as well with mine. I think the HA thread you linked is worth looking at, but I would distinguish between two things. I have actually been using the Dongle-M for many months. I received it for testing even before its official release, so I have used it with several different firmware versions over a fairly long period of time. I did have some issues during the early period, but nothing resembling the failure described in that HA thread. I have never seen the repeated ASH frames / ACK loop followed by `ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT`, `ASH_NCP_FATAL_ERROR` and a TCP disconnect. I’m using my Dongle-M over Wi-Fi with ZHA, so architecturally I’m still using the same TCP path. If this particular failure were happening in my setup, I would expect ZHA/zigpy to show coordinator/adapter communication errors, timeouts or eventually loss of the NCP connection. But I see none of that in my logs. The Dongle-M has been running normally, and ZHA is not reporting anything resembling the failure described in that thread. So I agree that the ESP32/TCP side deserves scrutiny - especially given SONOFF’s own statement that firmware 1.0.8 significantly improved UART-over-TCP connection stability. But I don’t think the linked HA thread proves that every Dongle-M user has a general TCP/Wi-Fi problem. The minimal ESP32 TCP ↔ UART bridge idea is certainly interesting as a troubleshooting experiment. It could reduce the number of moving parts, but I would see it as a way to isolate the problem rather than proof that the Web UI, MQTT, eWeLink-Remote, etc. are actually causing the ASH failures. [Next page](https://forum.ewelink.cc/t/dongle-m-firmware-release-notes/207603.md?page=2)