I have a mature implementation that has had very very few changes in several months. It has been running smoothly without issues. I have a C-4 hub that is pretty much dedicated to a Schlage Lock on my shop in the basement. I have two C-7 hubs, one is for Zigbee and Lutron, the other is for Z-Wave. Z-Wave is turned off on the Zigbee hub and vice versa. All three hubs are on release 2.3.2.141.
I just came back in the house from the backyard and when I walked into my office the lights did not come on (they are on Lutron dimmer and are triggered by two SmartThings motion sensors). The dimmer works from the switch. I checked the "Zigbee Hub" and saw that Zigbee was offline. I did not see any events about either temperature or load. I rebooted the hub (from the UI) to no avail. Looking at the Zigbee page I am seeing the channel has changed to 11 and there is no PAN ID showing.
Checking the UI after hitting send on the above message and the Zigbee is back online, the channel is back on 20, and the PAN ID and Extended PAN ID are populated. I am seeing events from Zigbee devices in the logs.
Would still appreciate advice or suggestions . . .
I did a shutdown from the UI and then unplugged from the wall outlet end. Left it unplugged for about 5 minutes (while I looked for the Brother P-Touch so I could label the power cords). Plugged it back in. When it came back up it initially gave me the warning (the red "bubble") that the Zigbee network was offline but by the time I navigated to the Zigbee information page, Zigbee was up.
Open to any suggestions as I nervously watch . . . @bobbyD
Some times the hub checks the radio before the radio is fully booted and thus it triggers the Zigbee Offline message. If the message doesn't persist after a minute or so, you don't have to worry.
Bobby took a look at the logs that he has visibility into. He said he didn't see anything notable. He did let me know about an app (mine - legacy RM) that was throwing and error so I re-wrote that and deleted the old. We're just watching it now.
FWIW, I've seen enough anecdotal posts in the community here since joining that suggest the zigbee radio acts a as a canary in HE's coal mine...
If the hub is getting overrun by something (even non-zigbee related), the zigbee radio is commonly (often? sometimes?) the first thing to go... Sometimes, the subsequent recovery is super quick, other times, not so much.
But I'd suggest trying to figure out what rule, device, etc is causing the overrun -- that should help prevent another radio crash.