C-7, zigbee radio toggling off/on (then off), no report of high load

[elykhtims]

Hardware Version C-7
First noticed when on Version 2.4.0.148, still happening on 2.4.0.151

I couldn't enable the radio in the UI.
Hub reboot via the UI brought radio back online
40+ devices on my Zigbee network. Recently moved from Z2M to Hubitat to reduce the overall complexity, disabled the Z2M radio. I excluded and factory reset everything before joining to Hubitat.

How do I troubleshoot when the logs show nothing but the 'offline' 'online' messages?
-- the offline/online messages occur over a few hours until the radio just stays off
-- unfortunately, an irregular occurrence over the past few weeks

today's log -- I ended up rebooting to get the radio on again
|manualReboot|reboot called from x.x.x.x|||1/29/2025 7:33:25.449 pm|
|zigbeeStatus|Zigbee radio is offline|offline||1/29/2025 5:30:42.503 pm|
|zigbeeStatus|Zigbee radio is online|online||1/29/2025 2:30:03.531 pm|
|zigbeeStatus|Zigbee radio is offline|offline||1/29/2025 2:29:58.705 pm|
|zigbeeStatus|Zigbee radio is online|online||1/29/2025 1:44:20.291 pm|
|zigbeeStatus|Zigbee radio is offline|offline||1/29/2025 1:44:15.513 pm|
|zigbeeStatus|Zigbee radio is online|online||1/29/2025 1:28:53.767 pm|
|zigbeeStatus|Zigbee radio is offline|offline||1/29/2025 1:28:51.152 pm|
|zigbeeStatus|Zigbee radio is online|online||1/29/2025 11:05:38.118 am|
|zigbeeStatus|Zigbee radio is offline|offline||1/29/2025 11:05:34.141 am|
|zigbeeStatus|Zigbee radio is online|online||1/29/2025 9:38:04.578 am|
|zigbeeStatus|Zigbee radio is offline|offline||1/29/2025 9:37:59.846 am|

[John_Land]

See this post for an example of a Rule to deal with the problem symptoms (the rule doesn't fix the problem). The entire thread may be of help.

Zigbee Keeps Going Offline

I started seeing the "short" Zigbee radio reboot (6-10 sec. duration) on my C7 HE after over a year of stability. I upgraded to a C8 Pro and still saw that problem. I replaced the first C8 Pro with another C8 Pro to eliminate the hub as a variable. No joy. So I rebuilt my entire Zigbee network (over 100 devices) AND moved to a different channel (from 20 to 25) and haven't seen the problem since. I strongly suspected that some Aqara devices might have been to blame (all removed from or never pai…

[John_Land]

If you implement the rule I posted, you probably need the latest version (below) AND to install the Hub Information Driver v3 AND create a virtual switch using that driver (that will enable the "VS Hub Information" value in the reboot() line of the rule).

[elykhtims]

@John_Land Thank you.

I don't use Rule Machine, I export all devices and use Node-Red, so pardon my ignorance of Rule Machine.

If I read it right, this rule restarts the entire hub if zigbee radio doesn't come on within 5 minutes, while it announces the event (not such a great idea since this has occurred in the middle of the night) and logs the same events I'm already seeing.

[RobDaBush]

The post linked above also shows a fix for your radio resets if you use Sonoff powered devices. Otherwise, it may give you some pointers to fault finding.

[John_Land]

The text in red indicates that rule command is disabled; I used the announcements only for debugging purposes.

Only actual hub reboots are notified to my phone. Short Zigbee radio crashes are just logged.

The MAIN purpose of the rule is not the logging or notifications, it's rebooting a hub that has finally stopped even trying to restart the Zigbee radio.

[elykhtims]

Well, no definitive solution, while the problem is still existing, the hub is successfully restarting the zigbee radio every time.

I do believe that it is due to a screwy zigbee device. I've not figured out which, but at least the restarts are automatically successful.