I have had this happen at the beginning of of the month, after an update. Thought I cured it but it resurfaced today, after updating to .174. Probably just coincidence but thought I would share.
What weird is the hub is online. The hub can ping cloudflare as well as cloud.Hubitat.Com but nothing can get to the hub through the Hubitat Cloud.
I forgot to mention, there is a band aid way you can try to keep the hub online / on cloud. Using the Hub Info v3 driver you can setup a cloud check where it will ping a cloud dashboard or maker API url and report the status as an attribute. You could then setup a rule to reboot he hub if the cloud check stays failed for a while.
Thanks for posting the screenshots. This is exactly what I am seeing on my C5. It seemed to start with 2.3.9.166. I will have to watch and see if it's happening when my router does it's scheduled reboots.
Please grab 2.3.9.177... we've narrowed down those cloud issues to DNS misconfigurations, and that version has some additional logic to straighten those out within a minute of occurence.
Thats not my issue if yot look at my posts u will see dns is working fine when i have no cloud access. Its boggles my mind why you REFUSE to look at my engineering logs when i can induce a loss of cloud access at will
Mine rebooted on its own last night too. Is this the new internal behavior when loosing cloud connection? I.did a reboot and restore as was worried about corruption.
@gopher.ny I had this happen twice now recently, once on .177 and again on .180, this is on my main hub and I have been keeping it off beta versions as of late, just main releases.
I have been having some issues with my cable modem also, had to restart it a few times in the last few weeks, not sure if its coinciding with that. All other devices have been coming back online without issues.
I do not realize the hub lost the cloud until someone tries to use Alexa and it wont work, otherwise everything else in the house is pretty much controlled locally. Hub works perfectly normal except the cloud API is dead. Reboot brings it right back up.
I begrudgingly setup the cloud check in Hub Info driver and just need to setup a rule now to alert me if it goes offline. Have never had this problem before until 2.3.9
I think this happened to me 3x now, all in the past few months.
The first time this happened, I thought the Alexa integration broke.
I realized that I could use my web browser and go to the hubitat IP Address, login and control my zigbee and zwave devices from the hubitat page, but Alexa couldn't control them.
But after rebooting the hubitat by unplugging it, everything started working again and didn't think much of it.
About a month later, it happened a 2nd time. Once again, I only noticed when asking Alexa to control my hubitat devices doesn't work. The Hubitat App on my phone worked while on my home wifi, but disconnecting my wifi, the Hubitat App didn't work while on my cell network. Unplugged the hubitat and everything started working again. It's like Alexa or the App couldn't connect to hubitat from the internet/cloud, only locally.
This just happened to me again today and I realized there are some threads on this forum with people with similar issues. The hubitat is on Ethernet and I have a static IP assigned from the router, the hubitat is using the default network settings. Nothing has changed in the past year on my router/network, yet this problem just started 2 or 3 months ago.
I am currently on .174 and I'm updating to .180 at the moment to see if that's any better.
Did you use the shutdown option from the settings menu before unplugging the hub? You run a small risk of database corruption by just pulling the plug. Most people have been able to get the hub talking again by rebooting from the settings menu.
