I would like to report some feedback on latest beta firmware 1.0.10 of Sonoff Dongle Max dongle.
I Have 2 Dongle Max devices, one of them i use it as a Zigbee Router mode, and the second one i use it as Thread RCP Mode. Both of them are on the latest beta firmware, and both of them are connected to different routers via Ethernet cable.
I have checked the logs and both of them keep disconnecting and connecting back.
Stop to blame the router connection,is a common problem,disconnect and connect on this zigbee dongle over tcp,solve the problem by fixing the firmware.I have the same problem and i think in the future i wil go with other brands,your software is not so stable.
I’ve been using the Dongle-M for over a year and, honestly, I’m seeing the opposite: it has been very stable. The occasional issue I’ve encountered was related to the Wi-Fi/mesh connection rather than the Zigbee firmware itself. After a Wi-Fi restart, the dongle can sometimes associate with a less-than-ideal mesh access point. Recent firmware has actually improved this behaviour. So I’m not sure I’d be quite as quick to declare the software “not so stable” based on a connection problem that can have several causes.
And I have to admit, I rather enjoyed the “in the future I will go with other brands” part. That’s quite a dramatic career change for a Zigbee dongle. Hopefully the next brand will also come with a magical abilities
From the first time the dongle was connecting and disconnecting,used with ethernet cable.If you will analyze te log you will see random conecting and disconnecting,yes is the last firmware.
In my case, since i had switched to stable 1.0.10 , then i had assigned a static ip to the dongle and reserved the ip in my router ip table, and I did not had significand issues since. I have 2 Dongle-M, one is in Thread RCP mode via ethernet, used as a OTBR router in Home Assistant, and the second one i am trying to use it as a Zigbee Router (repeater). Indeed like @jam3 said, most of the problems were because of the mesh network, i have asus routers in mesh mode (ethernet backhaul), anyway from 200+ iot devices i have and testing, Dongle-M was the only one creating issues. Looking forward for the next firmware update to fix remaining issues (mdns issues and ip allocation issues).
“Low LQI”, “far from interference”, “center position”, “frequent disconnects”… That’s quite a collection of technical-sounding words, but I’m still not sure what the actual problem is.
Which LQI is low? Wi-Fi or a particular Zigbee link? Which device? What are the actual values? And how exactly does that relate to the TCP disconnects?
The fact that your old USB dongle worked better is certainly interesting, but without comparable conditions it’s hardly a scientific experiment. And “Far from interference” is also an interesting statement. How did you establish that? Spectrum analyser? Radio measurements? Channel utilisation data? Or did you just lick your finger, hold it up in the air and conclude that the RF conditions looked good?
At this point I’m less convinced that the Dongle-M is unstable and more convinced that it has somehow become the main character in your personal networking drama.
far for inteference mean in a room without routers or computers ,conected by ethernet cable,low lqi (zigbee signal of devices)mean under 70,before was high than 100,considering that usb dongle was near PC and this has2 antena,no wifi activated conected by wire,update at last firmware,messages of disconnect -connect plus the problem at installation when i was been log out after a few seconds and this is not only me speaking,if you look on the forums you will see that this are common problems,no drama from me,some one tell me don’t flash the usb dongle as router because of the problems of this dongle,first to make sure is stable
i understand you are fan sonoff but lets be correct when you give reviews for a product,maybe at you is working perfectly,you are lucky,but the inrternet say that this is not stable.
Plus, am observat ca aceasta firma inceapa sa scoata pe piata produse cu soft-uri problematice la inceput,cum a fost si cu bridge ultra,dupa un update nu mai aparea in ewelink + altele(multe plangeri si pentru acela la incpeut cand utilizatori trebuiau sa-l restarteze pana cand au reusit sa scoata un update).
And for your knowledge now i try to use more shelly device and less sonoff,shelly have implemented allready what they try to do with open edge,mqtt,local management,mJs -script motor running inside the device,independent from cloud and so more features like websocket,http and api, but they do not have a zigbee hub.
I’m not a Sonoff fan. I simply don’t confuse “my device has problems” with “the product is unstable”, and I don’t consider two cropped error messages and “the internet says so” to be a diagnosis. The Internet says “NO”
I’m sad to say but from my last experiences with Sonoff i will try other brands(my favorite Shelly),that have software more flexible and ready from the box,no waiting for new release to improve stability and so.Sonioff is cheap but other companies(A LITLE EXPENSIVE) offer more flexibility and control of devices you buy.Of course no company is perfect.