Dongle-M firmware Release Notes

Dongle Series
1

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 (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 (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
ESP32_Upload_Flash_Firmware1718×1304 43.8 KB

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 (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 (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 (1.9 MB)

EFR32MG24 firmwares

Zigbee Coordinator v7.4.5 stable (factory default)

zigbee_ncp_uart_hw_donglem_v7.4.5.gbl (245.9 KB)

Zigbee Coordinator v8.2.2 beta

zigbee_ncp_uart_hw_donglem_v8.2.2.0.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
MG24_Upload_Flash_Firmware1718×1304 44.6 KB

3

image
image872×944 58 KB

image
image632×320 9.94 KB

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.

4

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.

5

Thank you for the explanation, this makes sense ! I will continue monitoring it and let you know.

6

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

7

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.

8

Please refer to Zigbee Version 8.2 Revision 2 (September 24, 2025) - Release Notes

zigbee_ncp_uart_hw_donglem_v7.4.5.gbl (245.9 KB)

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.

9

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

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.

11

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.

12

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
29c7a3739058e4079492ee73aee407c81684×1292 140 KB

14a33e7f8ce4ad82398020b17c3bb6f9
14a33e7f8ce4ad82398020b17c3bb6f91684×1293 159 KB

13

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.

14

The screenshot is from zigbee2mqtt.

15

How to enable that frontend / dashboard in the dongle-m ?

16

This is z2mqtt interface on home assistant

17

@ MichaelLearnsToCode 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
image770×724 27.7 KB

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?