I am troubleshooting an issue where it appears that services outside of my network (e.g., Alexa, OwnTracks) are unable to talk to my hub (C.7, 2.3.9.139 but also 2.3.9.136). I first noticed an issue when commands spoken to Alexa get device failed to respond for everything. From the hub, there was an alert about cloud connection failed. A check for update failed to detect that an update was indeed available.
Meanwhile, Web Pinger on the hub was happily pinging google.com and I was able to access the console with no issue. No Internet connectivity issues anywhere else on my local network. The IP address of the hub is reserved and the IP address isn't changing.
Here's the thing: Rebooting the hub fixed it. After a reboot, everything started working again. It found an update to .139 which I took and rebooted again.
About 12 hours later, we noticed it was back in failure mode with the same symptoms. I didn't get an alert about cloud not available, but a check for update did not detect that .141 was available). Alexa got device failed to respond for everything, and OwnTracks wasn't providing updates. After a reboot of the hub, everything working again, and it detected update to .141 available. I'll apply that and reboot.
What should I look for next time failure mode occurs?
I have (possibly had) a similar issue with 136 on c7. Google reported Hub was unavailable so I tried reauthenticating last night but got an error. I glanced at the logs but nothing was jumping out at me. It didn't occurred to me to reboot until I just read your message. The reboot appeared to fix. After it came back it showed that there was an upgrade to 141 available. I just performed the upgrade and Hubitat is still available via Google. We'll see how long it lasts.
As an active check for cloud connectivity I have the Hub Information Driver v3 go out and request a cloud connected dashboard or a MakerAPI authorized device - usually faster than waiting on the hub to raise the flag on it on its own.
OK, thanks. I used to run this but removed it when I was cleaning things up a few years ago. But it happens that I was looking for a hub reboot so I could put it on a dashboard for my spousal unit, and I know this can help me with that as well.
Fair enough. That's easy enough to rule in or out. Can you elaborate on what you think the issue could be? Keep in mind that the hub was talking bidirectionally with things on the Internet. In fact, I was hundreds of miles away VPNed in to a PC bringing up the console to troubleshoot.
This problem started about 3 weeks ago for me. I only noticed it when HD+ said it couldn't connect to the hub when I was out. Everything else worked except cloud connections (Alexa etc). I have since added a reboot if it fails to ping my cloud dashboard link for 10 times. A reboot has always solved the problem and automations continue to performed correctly.. It has happened twice while I was home as I now have the hub text me on Signal when cloud connections stop working . Texting to Signal never stopped working.
I think it is most likely due to an upgrade, but haven't verified that.
I have had an issue very similar to yours on two different C7s during the 2.3.9.x beta. In my case, only inbound connections through the Hubitat cloud would fail (remote admin, maker api or cloud endpoint URLs, some integrations). Like you, other things worked fine.
At first I thought it was due to a platform update, but then realized a simple reboot fixed it. However with the last occurence I discovered a simple cable pull was enough. See also : Cloud connection stops working - #21 by rylatorr
Not sure Victor has tracked it down yet, which is why I tagged him.
RESOLVED: Strangely enough, rebooting my Orbi RBR750 router resolved my networking problems with Hubitat upgrades, Alexa and webcore. I had no network issues other than with Hubitat services. My hub is networked with wifi and ethernet using DHCP. Hub network tests including ping of cloud.hubitat.com were successful. Multiple hub reboots did not solve the problem. Maybe I should connect the hub wifi to the Orbi "IoT" SSID or possibly remove wifi.
I have the same problem that The Alexa skill stopped working. I deleted the app, and tried to enable the skill again. I authenticate, select my hub then get "unable to link account with Alexa". This used to work when things broke last week.. I am also having problems with the webcore dashboard not connecting either.
I think I have tried that. A week or more can go by before it happens again. It would be hard to know it it had been fixed by a router reboot. The last time it happened I was doing a number of rule clones and edits. I think it is possible that preceded the time before it went down. Before I had setup the "cloud down" text,, the cloud could have been down for hours while I home was using it as all non-cloud connections continued to work (web etc). All I know for certainty is, I didn't have the problem before and it infrequently continues and others have complained about it.
