Sonoff ZigBee devices always falling off the network - what can I do?

Same here. I have two SONOFF ZigBee 3.0 USB Dongle Plus (EFR32MG21) configured with Zigbee2MQTT.

The SNZB-01 (button) seemed to have worked fine while testing it in the shop for a couple of weeks. Then I moved it to the house and it worked fine. The next day I noticed it disappeared. Re-added and then again the next day it was gone. Tried many new batteries, forced removed and restarted Zigbee2MQTT, re-add and still the same thing. LQI is over 190.

Now the same thing happens when added back to the shop’s Zigbee2MQTT. Odd that it worked out of the box but no longer after adding to a different network.

I also have 1 of 5 SNZB-03 (Motion) that started to do the same :frowning:

Anyway, I just thought I would share my experience so far.

1 Like

Mine buttons havent worked over two days only one or less, they always dissapear from zigbe2mqtt.
How long is the length og the usb extender? Have been informed that it should be between 50-100 cm.
I will try to buy a shorter usb kable , else i have thought to buy the sonoff bridge insteed.

Hi,
Anyone figured out the issue?
I have the same experience with Sonoff Zbdongle-E.
All switches go offline after a couple of hours.

Earlier today I noticed in one of the guides that with dongle E you are supposed to add an additional property in the yaml:
serial:
adapter: ezsp

It actually seems to help.
Half day passed and all seems to be working, but… jury is still out.
I’ll leave it till tomorrow and update.

Over the last few days, I have lost 4 of 5 motions sensors (SNZB-03) and 3 of 5 contact sensors (SNZB-04). And still no love for the button.

Setting the adpater to ezsp was certainly something that help me originally when I started a month ago. I also read that these adapters are experimental (https://www.zigbee2mqtt.io/guide/adapters/#experimental).

My cable in the shop is about 10 feet and at the house it is 3 feet. Both on Raspberry Pis also running zwave2mqtt.

I also updated zigbee2mqtt to the latest release from a few days ago.

For me, I have:

But, like you I have disconnections, and for SONOFF battery sensors (SNZB-04 and SNZB-01), disconnections are daily. Sometimes, but more rarely, the other types of elements also disconnect.
it’s quite annoying I must say.
Everything is new and the batteries are at 100% and good connections of > 190 LQI.

For a beginning of home automation and investment, I am rather disappointed for the moment not being able to trust the system.
I hope that the cause and an explanation of its disconnection will be found soon and especially a solution found!

Notes :
The “ZBDongle-E” is with the original firmware (not flashed).

  • how to control the firmware version ? OK, I find here:
    Sélection_380

  • Currently the version proposed online by SONOFF is: ncp-uart-sw_EZNet6.10.3_V1.0.1.gbl
    So I have a version 6.10.3.0 build297 installed and a version 6.10.3_V1.0.1 online…

In view of the versions … is it necessary to flash the Dongle?

Infos:

  • Zigbee2MQTT version : 1.28.4-1

My button has been ok the last couple days. I changed the “max rep interval” from 62000 to 7200. This was from a solution on GitHub (https://github.com/Koenkk/zigbee2mqtt/issues/13600#issuecomment-1283827935 ). There are many other logged issues about devices disappearing. It’s worth doing a search on the open issues.

I just changed one of my motion sensors and will see if it stays online.

2 Likes

Since a few days now, I have no more disconnection on the following elements:
SNZB-04, ZBMINI-L, ZBMINI, Xiaomi RTCGQ11LM
On the other hand the “SNZB-01” buttons always disconnect during the day or night, even using the modification method that iAutom8 has found.

My button is still going. It still works but now shows as “Interview Failed”. The motions sensors are still going as well. This was done by reducing the “max rep interval” from 62000 to 7200. I’ll head over to the GitHub repo and see if there is anything new on the previously reported similar issues.

I am experiencing the same with SNZB-04. I tried with max rep interval but it still falls out of the network.
Did anyone find a fix?

Just to add that I solved my problem with this fix, one week without falling from network

1 Like

I went from a VM hosted on my work computer to a HAOS installed on an Ultra Mini PC (Lenovo M73 USFF) and with the “max rep interval” modification turk from 62000 to 7200.
And since then, I haven’t had any disconnections for 10 days now. :slight_smile:
Thank you, I could never have done it without all the help from the community.

2 Likes

I thought I would report that a fix has been applied to zigbee2mqtt. During pairing of the device the min and max will be set to 3600/7200. This fix is currently only available in the Dev branch.

https://github.com/Koenkk/zigbee2mqtt/issues/13600#issuecomment-1369590325

Shouldn’t this be on the release branch now?

I am on the lates version and still lose my SNZB-04s and SNZB-03s within one day after pairing…

I have been facing the same issue for months now.

I have a Sonoff Dongle-P and 9 Sonoff door sensors as well as 2 Tuya plug sockets acting as routers.

I first added all my devices using ZHA after flashing the lastest version of ZStack on my dongle and my devices started becoming unavailable at random times.

I then switched to Zigbee2MQTT, thinking that it might fixed it since it’s made by the same dev as the ZStack firmware but the issue is still there.

At first I thought it was a range issue so I bumped the transmit power to 9dB instead of the 5dB it’s set by default, but even the sensor that is a meter away from the antenna goes unavailable. And if I set it to 20dB, then the sensors are connected directly to the coordinator instead of the routers that at physically closer.

It also seems like devices become unavailable in the order that they were paired. If I reconfigure a device that became unavailable, another one that was working fine then becomes unavailable.

That dongle should be able to work with 25 devices without any problem, so I doubt that adding more routers will fix the issue.

I’m starting to thing that this dongle is doing something sketchy internally.

Zigbee sounds nice on paper, but my 20+ wifi devices works flawlessly, making Zigbee (or at least Sonoff products) look bad.

Hoping this could help, as a lot of us are facing this issue

2 Likes

Any non-Sonoff end devices to test?

My Dongle-P based net is solid. The only device that goes unavailable is a door sensor on an exterior gate at a range I’m surprised it ever works at all, and one Aqara temp sensor I’ve had to repair twice in the past year or so (no issues at all with the other 6 Aqara temp sensors).

But… I only have one Sonoff end device - the SNZB-01 button and it has been stable. I had tried the door and motion and returned them early on.

I did have an issue for a short time when I had a Sonoff S40 zigbee plug in the mix, gave it two strikes and replaced with a Sengled plug and issues went away.

Unfortunately I don’t, I chose SonOff because it was cheap and I thought that buying everything from the same brand meant that it would work without any issues.

I have 10 door sensors (SNZB-04) and 2 motion sensors (SNZB-03) and they eventually became unavailable at some point.

Maybe SonOff end devices just suck, but 12 out of 12, that’s very unlikely. The common denominator here is the dongle.

Who knows what is even happening since no logs appears either in HA or Z2M

And a common core firmware for the twelve devices.

You’ve enabled zigpy debug logs in HA or zigbee-herdsman debug in z2m?

Fair play.

I’ll look into enabling debug for Z2M since I’m not using ZHA anymore.

I’ve got 24 sonoff snzb-04 and 02, and many silently get out of the zigbee network, again and again.
The only way to get them back is to re-pair them, which is a hassle.
Some of them fail several times a day and are completely unreliable, even when they’re just next to the supervisor (like, 2 meters away…).
My other zigbee devices work flawlessly on this network.

I use the ZBDongle-E (plugged on the front-top of the machine, not at the back), HAOS over Proxmox, and Zigbee2MQTT.

There is no log related to these disappearances. I don’t know how to fix this.
Can anyone help me on this ?

Hey @steveoriol,

I have also experienced the same issue with my Sonoff Dongle E since I installed it in December 2022. Last week, I updated my firmware from this repository: zigbeeFirmware/ncp-uart-sw_6.10.3_115200.gbl at fb955a14dae0e7e5f84dd0c0a81d4b736cfc5d83 · xsp1989/zigbeeFirmware · GitHub. The release was committed on January 31, 2022. Since then, it has been working fine for me and my Sonoff devices are always connected.

I advise you to follow this tutorial to update your firmware: Update the Sonoff Zigbee Dongle-E Easily - How To - YouTube.

I hope this can help all of us.

PS : my serial adapter has the value : ezsp

2 Likes