There is a new driver for the Dongle-E, but it requires flashing new firmware and possibly re-pairing your devices.
May have to do that.
I am re-pairing 20+ devices a week anyway.
There are two stages to re-pairing after an outage.
The first is re-pairing 5-10 devices that are showing unavailable for two hours after a full reboot.
The second is for the devices that are talking to the coordinator and appear to be working but don’t report motion anymore, or temp/humidity/ or don’t respond to commands - open/close blind.
This is another 10 odd devices that only become clear when automated lighting stops working.
So re pairing 145 devices won’t be too bad but will have to wait when I can spare a day or two to do it.
I must admit I am concerned by the ‘experimental’.
Is there another coordinator that will be more reliable?
My wife is getting pretty pissed off about it.
The only coordinators that are not ‘experimental’ in Zigbee2MQTT are the TI-based ones, eg. CC2652, like the Dongle-P
1 Like
Actually - I’ll try rebooting Home Assistant every day during the night and see if things stabilise.
I am really enjoying using Home Assistant, I have been building home automation for 30 years form X10 onwards and Home Assistant is the best Home Automation Hub I have used so far.
Many thanks for you replies!!
I have a Sonoff Zigbee Dongle Plus (P?) you recommend I switch to that?
I got an E because it was recommended I use that for Home Assistant - before I just used zigbee2MQTT and MQTT and Node Red.
I moved to Home Assistant at Christmas to reduce the amount of time I had to spend maintaining it.
But so far Home Assistant seems to need a great deal of ‘mothering’ to keep the wheels on
Worth the try.
1 Like
The P fixed all my connectivity issues I had with the E. There are quite a few opinions on the matter, but I thought I’d share my personal experience with both devices.
Guys, there are a ton of topics on intermittent connection issues.
This topic is to dicuss the following (not hardware-related) issue:
Some (always the same set of) zigbee devices become not availbale in HA, immediately after a HA restart. However, they show as available in Z2M. Furthermore, actions on them can successfully be triggered via the Z2M interface.
This has nothing to do with hardware and is not a connectivity issue per se.
I wouldn’t pass the issue off as normal. There appears to be a recent connectivity issue between MQTT and Z2M with the recent brightness MQTT changes which would fall under the this thread.
If you use the mosquitto add-on, the suggestion is usually to downgrade to a version that contains mosquitto 2.0.16
As for HA Supervised I always prefer the mosquitto message broker available from the Debian Repositories (2.0.11 by the time of this writing) over the mosquitto add-on available from the HA Add-on store.
Having the broker installed on the OS level doesn’t render HA to “Unsupported” or “Unhealthy”.
Together with the Sonoff P Dongle as the coordinator on Z2M I never experienced connectivity problems so far (except if LQI < 30) on different HA installations.
I attempted to use everything vanilla in Home Assistant to increase chance of it being supported / compatible.
So Home Assistant and all its components are installed and managed by Home Assistant on the VM.
I am using the Mosquito Broker 6.4.0 that it said I was to install for zigbee2MQTT
I currently have ~20 devices reporting <30 despite 8 Ikea zigbee relays and 81 powered devices, 8 of the poor signals are mains powered devices.
The funny thing is devices that report unavailable still respond to commands then become available.
The Hue Hub had no issues with a full load of 50+ lightbulbs but I migrated them to Home Assistant to reduce the number of zigbee networks in the house.
I have shutdown almost all the other zigbee networks.
I am left with one Hue Hub to control the ~20 lights in the lounge, I reluctant to add more devices to Home Assistant right now.
And then there is the Smart Meter zigbee network which I do not have any control over at all.
this issue has not happened here anymore for the past ~3-4 months.
I keep HA and the Z2M addon up-to-date, so maybe a new version fixed the issue for me. 
On build number 19 now.
zigbee2MQTT runs for ~12 days then devices fall of the zigbee network and between 10-20% of devices need re-pairing.
The remainder are incredibly slow or unresponsive getting to a point for another rebuild.
On this rebuild I have wipe a Home Assistant Green restored to Factory and carried out vanilla installs for MQTT and zigbee2MQTT.
Did notice by default the config for zigbee2MQTT is yo enforce v4 of MQTT protocol, there is no v4 and the default MQTT Mosquito only supports 3.1, 3.1.1, and 5.0.
If you change the MQTT version in the zigbee2MQTT UI then it is not persistent and requires diving into the configuration.yaml to make it stick.
Not sure if that was a contributing issue, but on Day 2 of the rebuild, got CORE functionality back up - now lets see if it still works in 10-14 days 
I am extremely hopeful.
1 Like
I have a very similar problem but it seems to be not exactly the same:
Sometimes after HA restarts (especially when doing multiple restarts in a short time), but also sometimes randomly after days or weeks of usage the devices are reported as available and online but they are no longer controllable.
Sometimes this also happens when i move a device so that it has to connect to another router device.
Humidity/Temp devices are still sending periodic humidity/temperature information, but it is always the same.
Popp (danfoss ally) thermostat does report its actual state/temperature correctly but i am no longer able to change any setting of the thermostat.
The only working solution is to delete and repair the devices. Sometimes it helps to remove the batteries from the thermostates.
I am using a Sonoff Dongle-P. I already tried a Dongle-E, but this did not change anything. This issue annoys since two years…
1 Like
Last Sunday zigbee2MQTT dumped all its devices again.
Rebuilt zigbee2MQTT again for the 19th time this year I have got really very good at pairing devices.
Even created an automation for this devices that require multiple on offs to start pairing
Not going into it here, extensively covered elsewhere - it is just a persistent problem across different instances and factory resets of Home Assistant .
I did get it stable for three weeks then it imploded.
So have now reduced the number of devices on it 50 router and 9 end devices and hope it stabilise on this version
I have same case after upgrade Z2m to version 2.0.x
with z2m 1.x.x it waorks fine.
Symptoms:
After upgrade 2 pilots stop working.
From time to time one pilot from time to time stops working.
Investigation:
At Setting - devices - there is no action when buttons are pressed.
In z2m - device is on-line and awailable.
z2m logs - it shows actions, when buttons are pressed.
I opened mqtt client and check msg in mqtt - there are topics with actions from the pilots.
It looks like some issue with communication beatween mqtt and HA.
It is not a problem with devices, as it show up after upgrade z2m v. 2.0.x.
I have backup and when I restore previous z2m (1.x.x) - everything is working fine.
Maybe there were some changes in topics?
but thing is quite strange.
I have 3 of such pilots.
1 pilot is working fine.
2 pilots stop working after upgrade z2m to version 2.0.x and are not working all the time.
I have also 4 ikea’s circle pilots.
3 are wokrking fine but 1 stop working for 5 minutes (3-4 days after upgrade) and when I wanted start my investigation - it works again.
z2m change formating?
or mqtt - ha issue
Good day @all
I use Z2MQTT with a SLZB-06P7 coördinator, SLZB-06P7 as router and a few Sonoff E dongles as repeater and placed them at several places in the house to cover the range but still have issues with losing some of the zigbee modules.
I also have paired the zigbee devices to the nearest repeater.
Anyone having a tip for me what to check and what to take care of?
Don’t think the issue is with dongle. MQTT messages are normally broadcasted. In fact, if I rename the device in z2mqtt web UI the device comes back immediately. Just plain frustrating to do this every day.