I have as C7 that was running 2.3.8.139 (but I have observed this for ~2 months, so on earlier releases, too.) Also, I think this started when I moved the hub to a new location further from the Wifi router, so likely that is the trigger (and, yes, I will try moving it back to my less-preferred location, but my question is more about how to figure out why it's failing and not fixing itself.)
My C7 is using wifi (for years now) with mostly success. I moved the hub upstairs, further from the wifi. It works fine, but has started (either after the move or perhaps due to a platform change) to occasionally just disappear, as in I cannot connect to it from my network (all my other devices trying to reach it fail to do so, and I cannot connect to either the UI or diagnostic port.) I eventually have to power-cycle it, and it comes up ok.
The logs are full of errors from my apps, all showing that it cannot reach devices by IP. But, e.g., the logs for zigbee devices show they continued working fine (like even though the hub was unreachable for two days, the temperature sensors kept processing temperature events the whole time.)
I was away from home in this case during the two days, and the only thing I could do remotely was restart my wifi network, which did NOT help.
I don't see anything else in the logs about why the hub stopped being able to communicate over the IP network. (Also, my wifi is a Google one that has even less diagnostic ability, so I get nothing from that.)
As I said, I am going (sadly) to try moving it back to see if that "fixes" it, but this seems like something I would love to investigate. If there were a reasonable hook available, I would even wire up my own dead-man's switch that caused the hub to reboot after a long enough time unable to communicate with my network.
Hubitat folks, is there any hidden logging you or I can see to figure out what triggers it, why it doesn't detect the problem and reconnect, etc?
thanks!
Dan
