This problem has happened twice in less than a week. My C-8 and ZigBee network has been working fine for months and just recently, events won't be captured and triggers won't fire. It is almost like the devices (buttons, switches, etc), aren't even seen on the network anymore. However, it might be something clogging up the pipe since if events do work during that problem time, they are VERY delayed.
Is there a way to see better logs about what is actually going on during those times? The hub is responsive through the web interface, but the devices on the ZigBee network don't trigger events. I can't pinpoint what the culprit is. The last thing I (think I) did was add a Nest Thermostat with Matter to the Hub, but nothing is for controlling or trigger anything with that device.
I'm happy to provide logs as needed. I've had to shutdown and leave the device powered off for the network to become responsive again. A regular reboot didn't seem to resolve it.
Look at your Live Logs/Past Logs when you have an event w/your Zigbee devices and see if you notice any "Warn" or "Error" notices in your logs. Since your thermostat is the only recent change you can filter on it in your past logs to see if it is throwing any errors or logging repeatedly/excessively.
Also look at your Device Stats and App Stats and see if there are any devices that stand out in terms of high levels of activity.
That device is a ThirdReality ZigBee Plug. It is constantly reporting power since the driver doesn't seem to be able to disable it. However, it hasn't been a problem till recently.
That's a lot of % of free/busy...I think @rlithgow1 is familiar w/these devices. Rick - this look normal/acceptable for the plug? I know there was a lot of conversation about the excessive reporting.
Pretty easy to test if it's the root or part of the root...replace it in your automations w/a place-holder virtual device using Settings> Swap Apps Device and then remove the plug from your hub and reboot and keep an eye on things.
I see I forgot to show the absolute time. It is shown. It doesn't seem to be that busy in real time. I'm not sure that is the root problem, though. That plug was working fine for months.
Have a look at the Zigbee details page under settings. You can sort by the « messages » column. The TR plugs will be up there but maybe you’ll see some other clues.
You are on an older version of the hub platform...there are updates and fixes in later 2.3.8.x versions that you should run to see if they impact your issue. You can always fall back to 2.3.7.145 if the udpate to 2.3.8.123 wasn't better for you. So I'd update to the current platform version first.
Updated to latest (2.3.8.123). Upon upgrading, the unit still is in a bad state. It's like messages to ZigBee devices are just stuck in a queue and not being sent. A simple on command from a device page isn't working.
Sorry, meant to include this in my suggestion about the update. Also do a shutdown of your hub, go to settings and select shutdown, wait for the red LED appear on the hub, then pull power. Wait about 30 seconds and then plug it all back in.
If everything is completely unresponsive right after an update to a new platform version, then it's definitely not a memory issue. After an update and reboot your memory will start out fresh at its fullest state.
There is some other issue going on here.
After the shut down\restart, go to your Zigbee details page and confirm that the ZigBee radio is enabled.
Show a screenshot of Zigbee details sorted by message count, highest first.
You can try having a look at the Zigbee logs (from the same page) but it’s not easy to parse unless you are familiar with Zigbee cluster IDs.
For the TR plug, try changing to the system driver (generic Zigbee outlet) and reset and re-pair (hold the button for at least 30s with the device is plugged in).
The long power off reboot did work. If/when this does happen again, I will provide the screenshots you requested. Everything was reset after that shutdown.
