Every time an update is available, the zigbee network goes offline.
For a while now I have found that the zigbee network goes offline for seemingly no reason.
Eventually I realised that it goes offline whenever there is a software update available.
The two messages always appear together. I do not ever see the zigbee network go offline without there also being an update available.
Please don't try to be helpful by telling me it is impossible. I am merely reporting what I see, and I have enough occurrences of this to rule out a different cause.
It is really irritating because I cannot rely on my automation network when it does this.
If you are not regularly on the forums or checking your hubs for updates there is a high chance at any given time you will have an update waiting. Updates can happen multiple times a week for multiple weeks after a major update. So what if just coincidentally every time the Zigbee goes offline when you log into the hub to see what is going on, there also happens to also be an update? That seems much more likely.
Or can you pinpoint the exact date/time Zigbee goes offline and correlate that with when the update was posted n the forums?
If you are not enrolled in beta at all then there should be long periods of time with no updates (while beta is being worked on, before public release). So if your Zigbee works flawlessly through that entire period, and then suddenly has issues multiple times a week (when updates come out) after the major release comes out, then you could be on to something.
Have you ever tried just rebooting the hub WITHOUT updating? To see if that brings Zigbee back?
2.4.3.131 just dropped 2 hours ago. Is your Zigbee offline?
Yeh it seems it's not the updates. Unfortunately there is no information in the logs that I could find about why the radio goes offline. It's basically impossible to debug.
I have managed to set up a rule to reboot the hub when the Zigbee radio goes offline.
This is not ideal, but it's better than having to manually reboot the hub all the time.
It would be nice if there could be some report on why the radio goes offline in the logs.
It would be nice if there were an option to restart the radio when it goes offline.
I know I am not the only one who suffers from what is a pretty serious shortcoming for a home automation system.
There should be some indication that ZB is offline in the location events section of the logs, and that should be an actionable event (sent alerts, reboot, etc.) I'm not sure you can get into MORE detail as to why from that specific log...
My initial suggestion, is to open a separate browser tab, and leave open the Settings->Zigbee Details->View log open to see if you can catch anything just before your crash (you'll likely want to disable your auto-reboots, as this log isn't persistant)
If more details is needed, either ask one of the HE support staff to look at the hubs engineering logs - And they may be able to sort out what device is the problem child (or a mesh interference issue) or if you more of a DIY sort of person, setup a Zsniffer (there are multiple threads on this), and monitor the mesh yourself, noting what's happening just before your Zigbee offline timestamp.
You probably have a rogue device that's crashing your radio or you have a hardware issue on the hub itself. I had the same problem recently and I used the zigbee map 3.0 app to troubleshoot it. After I reset the hub and the radio was up, I used the app to build a full zigbee neighbors map. Turns out that a sonoff zigbee outlet was the culprit. It was showing up as unrecognized, it was a primary router for the west end of the house, and the link quality for all of its connections was poor. We had noticed a zigbee reliability issue for devices on the west side of the house prior to the radio going offline too, and then I noticed that the Sonoff device also wasn't on the compatible device list. Replaced it with a Third Reality outlet and now the network is stable again. I'd suggest that you build the neighbors map on your own hub, then investigate unusual routers/devices that may not be reporting correctly and/or have a lot of poor link quality connections. I was actually surprised that a single rogue device could crash the zigbee network on my hub.
