Hi and thank you again for helping us to move forward!
This is a good idea! I’ve tested the cable with a network tester.
It lacks shield, but all lines looks OK. I’ve already ordered some 0.9m cat-8 cables (they come with shield) so let’s see how it goes in a couple of days.
In theory, an unshielded Ethernet cable is more susceptible to interference and may be more likely to experience disconnections and packet loss.
We will wait for your new cable to arrive and continue investigating this issue after you have tested it.
Thank you for your cooperation!
Yes, In the meantime, here is the information requested from the switch:
[email protected]'s password:
swroot#show interfaces status gi1/0/6
Flow Link Back Mdix
Port Type Duplex Speed Neg ctrl State Pressure Mode
--------- ------------ ------ ----- -------- ---- ----------- -------- -------
gi1/0/6 1G-Copper Full 100 Enabled Off Up Disabled On
swroot#show interfaces counters gi1/0/6
Port InUcastPkts InMcastPkts InBcastPkts InOctets
---------------- ------------ ------------ ------------ ------------
gi1/0/6 23276134 2650587 77585 2480960089
Port OutUcastPkts OutMcastPkts OutBcastPkts OutOctets
---------------- ------------ ------------ ------------ ------------
gi1/0/6 20357977 445454456 2022769 399556643514
FCS Errors: 0
Single Collision Frames: 0
Multiple Collision Frames: 0
SQE Test Errors: 0
Deferred Transmissions: 0
Late Collisions: 0
Excessive Collisions: 0
Carrier Sense Errors: 0
Oversize Packets: 0
Internal MAC Rx Errors: 0
Symbol Errors: 0
Received Pause Frames: 0
Transmitted Pause Frames: 0
swroot#show eee gi1/0/6
Port Status: up
EEE capabilities:
Speed 10M: EEE not supported
Speed 100M: EEE supported
Speed 1G: EEE supported
Speed 2.5G: EEE not supported
Speed 5G: EEE not supported
Speed 10G: EEE not supported
Current port speed: 100 Mbps
EEE Remote status: enabled
EEE Administrate status: enabled
EEE Operational status: enabled
EEE LLDP Administrate status: enabled
EEE LLDP Operational status: disabled
Resolved Tx Timer: 30
Local Tx Timer: 30
Resolved Rx Timer: 30
Local Rx Timer: 30
swroot#show green-ethernet gi1/0/6
Energy-Detect mode: Disabled
Short-Reach mode: Disabled
Disable Port LEDs mode: Disabled
Power Savings: 52% (33.73W out of maximum 64.57W)
Cumulative Energy Saved: 17264 [Watt*Hour]
* Estimated Annual Power saving: 288756 [Watt*Hour]
Short-Reach cable length threshold: 50m
* Annual estimate is based on the saving during the previous week
NA - information for previous week is not available
Port Energy-Detect Short-Reach VCT Cable
Admin Oper Reason Admin Oper Reason Length
-------- ----- ---- ------- ----- ---- ------- ----------
gi1/0/6 off off off off
swroot#test cable-diagnostics tdr interface gi1/0/6
..
Cable on port gi1/0/6 is good
swroot#13-Apr-2026 11:31:51 %LINK-W-Down: gi1/0/6
13-Apr-2026 11:31:55 %LINK-I-Up: gi1/0/6
13-Apr-2026 11:31:59 %STP-W-PORTSTATUS: gi1/0/6: STP status Forwarding
swroot#show cable-diagnostics tdr interface gi1/0/6
Port Result Length [meters] Date
----------- ----------- ---------------- --------------------------
gi1/0/6 OK 13-Apr-2026 11:31:50
swroot#
Since you are currently waiting for the new Ethernet cable, could you please try following the tutorial to see whether it helps resolve the network instability issue?
Hi,
The new cables arrived yesterday. It is about 14 hours since I changed them and since then, no disconnections have occur.
The disconnections counter is there so I’ll be monitoring how it evolves but the conclusion at this moment is that I’ve had to use a shielded cable in order to have the Dongle-M in “stable” working conditions.
I’m not using WIFI on the Dongle-M and there is another WIFI AP a meter distance from the dongle-M, apart of that, the installation is underground so there is no interference from the outside.
At the moment, we have at least one movement ahead for better stability
We are very glad to hear that the issue has been resolved.
Please continue to observe for a while to confirm whether the issue has been completely resolved. If anything happens again in the future, feel free to contact us at any time, and we will follow up as soon as possible.
Hi @SuiKa ,
I have recently purchased a Dongle Max, and all of a sudden after running for one day, it stopped working. Its not even turning on. I am using usb c connection and getting data over wifi. What’s the best way to solve this?
Could you please confirm whether the indicator light on your Dongle-Max turns on normally after it is powered on?
The light is not turning on at all. Tried different power plugs, but still the dongle is not responding.
Could you please provide us with the SN code printed on the casing of your Dongle-Max? DM it to me will do. We will help check whether there is any issue with the product itself.
If there is indeed a hardware problem, we will replace it with a brand-new Dongle-Max for you, so please do not worry.
Is there a new EFR32MG24 filmware ready or in devolopment. Now many of us are stable could we get that experimental 8.2.2 version made official (assuming it is not) please.
I have switched from sonoff plus mg24 to the dongle max and my previously rock solid zigbee network is now fullly unstable. Devices disconnecting all the time. Z2MQTT crashing. This product really does not appear to be production ready unfortunatelly. ( Running stable V1.0.7 ) I switched back to the mg24 and everything is perfect again.
Btw, for the dongle developers here, it would be nice to have a self signed certificate to provide https, otherwise that password will always go in plain text.
You can try upgrading the firmware to 1.0.9 beta, which should resolve the issue where Zigbee2MQTT keeps crashing.
If the issue still persists after the upgrade, please provide us with the corresponding Z2M logs, and we will help identify the problem as soon as possible.
In addition, we have noted your request and will consider it for future version requirements.
We are indeed considering and developing support for a newer EFR32MG24 filmware, but this still requires some development time.
Please bear with us and kindly wait patiently.
Can you post firmware 1.0.9 here?
Here are the firmware for 1.0.9 beta: https://forum.ewelink.cc/uploads/short-url/yzithrhuKBJax4ac9laoXssjnHg.bin
Interesting firmware. After updating, dongle-m stopped working. I had to revert to 1.0.7.
What do you mean by “stopped working”? What specific symptoms are you experiencing?
And 1.0.7 works fine?
