I think I'd like to test for a zigbee radio reboot, the ~10 second kind.
I was thinking, reboot if duration between zigbee radio off and on is more than 10 seconds.
Maybe have two rules: the first triggered on radio off and put the time into a hub variable
The second triggered on radio on, put that into a hub variable, compare the two values, and then act on it if the difference is more than 10 seconds, or so.
Am I on the right track, or would there be another way to accomplish this?
I noticed that Location events are not accessible in Conditions, just Triggers.
This is what I have.
I also have a reboot for a zwave crash...which I think is persistent thing, unlike the zigbeeOn and Off.
My thinking is I don't have to think about low memory, just persistent radio outages.
But, I suppose low memory also can slow things down without taking down the meshes?
Curious about this. I have had 28 Zigbee radio restarts on my C7 since I started tracking this on May 20. None of them have ever been more than 7 seconds. Are your outages really greater than 10-15 seconds?
I am more concerned that the restart is happening than duration. I have been monitoring the Zigbee logs to determine which devices are more chatty than others by dumping these logs into a MariaDB via NodeRed listening to the Zigbee log socket and reporting from there. I have removed several devices including 2 Environmental Sensors and one Third Reality Temp/Humidity sensor (which I know you use) as they were top three devices by several thousand entries over the others. Zigbee radio restarts have slowed down as a result.
They've generally been between 7 and 8 seconds. I feel that I shouldn't reboot the hub for those radio reboots, only for a more serious, longer term radio outage.
I have 5 of them.
I had no zigbee radio reboots when there were no repeaters, and all the battery devices were talking directly to the hub.
Since I've put 12 of the new Sengled plugs in a couple days ago, I've had three. Not blue sky, because one plug was acting up, I was trying to pair it etc.
They're just idling now, with no load and no apps. I'm gonna see if I get more and, kind of, document it on my 'Experiment' thread.
I am trying to figure out if my C7 is failing as Bobby looked at my engineering logs and there is nothing at the times of my zigbee radio restarts. This hub should have minimal load so this very odd. The only recent devices I have added are Third Reality branded outlets (2 of them) and the Temp/Humidity sensor. Back in May I added a few Inovelli Blue dimmers but I don't see them spamming the network and no traffic at the time of the reboot. I pulled the batteries on the temp/humidity sensor to see if things improved and I just got alerted of yet another radio restart so it is not it.
I have 108 zigbee devices and 44 of them are mains powered repeaters so the mesh should be pretty strong. Super strange this radio restart happened so much recently.
It looks fine but honestly I don't know that you need it. I haven't had to reboot my Zigbee hub because of the radio restart, only if the memory gets super low.
I am not sure what to think. I have never had a ZigBee outage show up in my logs, except for the one day I had 2.3.5.145 installed which broke ZigBee on C5/7s. However, I have weird issues. Today, all my ZigBee motion sensors worked perfectly. They detect motion instantly, just as expected. Other days, I can literally dance 5 feet away from a motion sensor and 30 seconds might pass before it reports motion. I cannot figure out what's going on.
I also have very similar issues with ZWave devices.
Also, sometimes a Rule Machine rule fails to trigger properly.
Sometimes I have weeks where everything works perfectly. Other times I have days where nothing works reliably at all.
I have no idea why my stuff won't work the way it should...
I haven't seen a direct coorelation yet but it is more common to happen. I had more frequent restarts when the memory was lower. After doing a soft reset on my hub recently the memory is much higher and restarts are also less frequent.
I have a C8 sitting in a box and have been holding off migrating to it given things I have read on the community. My next move is to migrate my Zigbee hub to it and see if that solves the problem. This will prove whether my C7 hub has a hardware problem.
