For a few weeks I'm having a strange behave on my hubitat C4. Occasional a random device will drop of (apparently). At first (as I have only ZigBee and Lan devices) I thought that was an issue with that device falling of the network, changed batteries (end up changing all batteries from all devices). Restarted the router and all would work fine. A few days later another device would drop (not necessarily the same device). Repair, restart router and the same thing, would happen ok for a few days.
Fed up when a new device dropped again and on a rush when this happen I went on and just restarted the router and decided that I would troubleshoot when I was back home. To my surprise when I come back everything was working without repairing the devices. (Odd at least).
Since than it happened a few times.
Logs don't show any errors. Just that a device stop reporting events.
How can I troubleshoot this? The strange thing is that this has been happening for a few weeks now. My mesh was rock solid until 2.08.1xx than since than I'm having this issue.
I'm assuming you are talking about your wifi router (because the hubitat is not a router). If this is the case, then you likely have your wifi on the same frequency as your zigbee network and that is causing interference. You need to adjust your wifi and zigbee channels so that they aren't on the same frequency.
99% of the zigbee devices are xiaomi. But they are not the only ones dropping.
Besides its not a matter of them just dropping.
If you read my post careful i explained why this is not your normal drop. Sometimes all i need is to restart the hub and the logged events from the apparent dropped devices are populated on the event table of specific dropped device.
Additionally sometimes that device needs to be rapaired after the reboot of the hub, others it just start working on his own.
My best guess at the moment is that for some reason the hub is caching the events at the entry point of hub, but that makes no sense at all for a simple reason. If the hub is acknowledging those events and doing nothing with them would be because something would be breaking the code logic, however if thats the case why is not a constant breaking? Whu does it works for a large couple days and than the cycle repeats itself?
So this make my assumption flawed.
Also to note the mesh, number of devices, rules, etc has not changed for large weeks. So there is no new code addition (besides the firmware updates). To note as well that this exact setup was working flawless for months.
So im a standstill. I had avoided posting here as it seems that in this forum there is a holy magical solution that is to blame Xiaomi devices for everything. For me that is plain BS. I understand that they are not behaving within the expected standard behaviour but that does not make them the culprit of everything.
For me that is like you saying that all tattoed persons are criminals just because they are different and have tattoes and do not comform with the norm of not having tattoes.
Talking like that will probably not attract that much help from anyone.
I ended up removing all Xiaomi devices from my network. They are all sitting in a drawer somewhere unused (I did this all before even switching to Hubitat). Xiaomi truly are crap and caused me nothing but trouble.
Like what? I haven't offended anyone. I just mentioned a true fact the Xiaomi devices are always a escape goat. In my particular case how can this be a Xiaomi fault?! It's the hub that's bogging down and not processing the events.
You don't like the Xiaomi devices don't use it, simple.
I know this is not Xiaomi specific. But as I fear "Xiaomi is crap, remove them" rant started straight away.
I was avoiding reset the hub to factory default as I will loose, all devices paired and will need to repair, redo all rules and automations, it makes me loose the will to do it.
A Soft Reset does not cause any Zigbee or z-wave devices to lose their pairing with their respective radios. It is more of a Database Reset, which you can then simply restore from a backup taken just prior to the reset. No automations are lost.
I’m not certain what improvements a soft reset results in... others have reported it helps sometimes.