So, this just started late last night. I cannot control anything via Alexa. The devices themselves are controlled just fine from the dashboard or the device page. All my automations work.
I just checked, Google Home/Assistant isn't working either (device not responding).
HE is online - I can access it via my phone when its on the cellular network.
This may not help since both assistants appear to be broken at the same time, but still worth a shot to disable and re-enable the Hubitat skill in the Alexa app. If nothing else, you might get an error message that is descriptive.
This is now happening to me on a daily basis as well. I don't have alexa, but do loose connection to Google and to the dashboard via the app. I have to reset the hub to get them working again.
Google home says that it can't find Hubitat. Everything worked fine until the latest updated. Also some rules did not run today. Cloud dashboards just give different error messages.
Hmmm .. I'm fairly sure this information would be posted somewhere here in the community, but be advised that Patrick posted to the Facebook group:
We are aware of some users reporting loss of cloud services, such as remote access to dashboards, alexa, google, etc. We are working to track down the cause, but it appears to have been introduced into 2.1.3 and if you are experiencing this, we recommend rolling back to 2.1.2 until we have a resolution. A reboot of the hub will fix it, but in our research, its likely the issue will come back until a fix is deployed.
I am on platform 2.1.3.120. This just started happening after one of the last platform updates. The Echo will lose connectivity with the hub until I manually go in and restart the hub. Then it will work fine for a little while. When I go into the Echo app settings, all the way down at the bottom, under Scheduled Jobs, the one named "getAlexaAccessToken" shows a status of "PENDING". I can't help but think that this might be why it's becoming unresponsive. I don't see anywhere to manually run this job or force it to complete. Any ideas on this?
I'm on .125 and everything is working good for several days. I have a c4 hub. Seems this mostly is a c5 problem. I did have problems with Alexa at first. I went into my Alexa app and disconnected from hubitat, uninstalled the Alexa skill in hubitat, then added Alexa skill back and in Alexa app added hubitat back in. Discovered and enabled devices and all is good.
I might be wrong, but I don't think the issue, which arose in 2.1.3.120, was a C4 vs C5 issue. Until 2.1.3.125 was released, the advice from @bobbyD was to downgrade to a 2.1.2.x platform version. Off course, the fix in 2.1.3.125 makes that unnecessary.