Reset the network, and disconnected 4 of the 13 presence sensors I have. Note i had no issues with these sensors being connected for about a month, and other devices are working fine. But I'm willing to try anything. This is the data after 2 hours.
So yeah most active sensor is the kitchen and its sending about 1 message every 10ish seconds. Others are sending about 1 message every 20sh seconds. Also air gaped all switches to see if i can see how long before disconnect
Yea I don’t have any other zigbee except for the Inovelli 2-1s and fan switches. Zigbee stops reporting after a period of time every day. I have to air go each day to regain control. Rule machine still tries to run but no responses or control.
Everything at the same time or just certain devices?
If restarting the zigbee radio does not fix it and you have to air gap the device, I would suspect it is a problem with the device.
The important question is, is it impacting EVERY single zigbee devices on the mesh, or only certain devices? You clearly have other devices on the mesh besides those switches, are they still working / reporting when the switches stop working?
Unfortunately I’m not away of how to get this information. I can say that I’m not having to intervene to get my other devices to work. I have not experienced any issues with them, but that doesn’t mean they aren’t going offline. I feel like something is causing a hiccup with the zigbee network and all the other devices are recovering but for some reason the blues are needing to be air gaped in order to reconnect
Just look at some of the other devices in the event tab, see if they are still reporting events when the switches go offline. It is possible the switches are repeaters though so having those down might muck up the entire mesh.
Yes you are correct the devices should be able to recover on their own. IMO that would be a device issue. You should reach out to Inovelli for sure.
It could be something else on the mesh, such as those sensors, causing the disruption.
Either way, I do not think it is something on the hub side.
I am going to edit the topic title, maybe some people with the blue switches will have more insight. I see there are two people on here with issues but both seem to be about the Inovelli switches.
So looking I found the following from last night. Looks like the blues are reporting their power level every hour. I see in the logs for two devices that they check in at 3:43 am, then do not check in again until i woke up and started testing to see if events would trigger. Looks like all the devices died at this time. Also looks like ikea blinds stopped reporting around the same time. I feel like around 4am something is happening with the zigbee network, like it reboots/refreshes something and the invoelli devices are not reconnecting when ever that happens, while all the other devices are.
I did find this just now which is interesting. I'm also having trouble with my ikea blinds, but they have been an ongoing hassle. I have a rule that is set to repeat until they all report as closed (they are closing just not reporting correctly). Apparently my catch failed last night and kept sending the commands to close from basically sunset until 4am then stopped... which happens to be same time that the inovelli switches stopped reporting, then started reporting again when my open command started initiating.
I suspect something related to the Blues's reports are crashing your mesh - regardless of device, power-related reports are always the usual suspect there.
Aside from that, I've never found my Blues to be reliable or strong repeaters -- I admittedly have no hard evidence to support that; it's just my own N=1 experience. I rely on other zigbee devices to carry the backbone of my zigbee mesh, and my 9 Blue 2-1s are working well as part of all that.
I do not have any power reports set up on any of my Blues - I simply have no need for that.
The Engineers may have found an issue. Due to the lack of "keep alive" cluster support on Hubitat platform, it forces the Inovelli's to rejoin every 12 hours. The rejoining process can cause errors and prevent from rejoining. Inovelli's feature rich firmware includes keep alive cluster support and may have to be removed or modified in order to support Hubitat's lack of support. It should be an easy fix if confirmed.
Interesting... I wonder why it affects only some users - I've had some issues with my Blue 2-1s since the original launch (all resolved now AFAICT), but dropping offline hasn't been one of them
I'm just relaying what was found; are you saying the Hubitat platform does support the keep alive cluster? If so, I can relay it back to the FW Engineer.
Will do! I'm sure they're monitoring; I will also update the Inovelli post as well to ping the Engineers.
Unfortunately there's two people with the same issue (at least one this post). If it was just me, then I would just blow out the configuration. The hub and switches have worked great over the past year so it's just weird it all stops working at 12 hours. It's repeatable (all devices stop responding around the 12 hour mark) and my zigbee network has been down for over two weeks since first noted.
interesting, I'm sure there are more than three people using these devices, so if the issue of these devices dropping was due entirely to Hubitat, then I would think the issue would effect all blue users...
Interested in what Inovelli has to say about this.
Absolutely interesting. If the issue was strictly a Inovelli 2-1 issue (not on any new beta firmware), you'd think ST, HA, and Echo users would also be seeing similar issues. I know there was an issue identified above for C8 hubs, but I'm a C7 hub user.