Running C7. Started on 2.3.8.139. Completed upgrade to 2.3.8.140. After that Alexa integration was no longer working (device unresponsive). Reset Alexa in the Alexa app but then could not connect to hub.
Local network access was fine. Went through all the usual network troubleshooting, toggling to static and back and faffing with DNS and DNS reset and the 7 second reset button procedure. Nothing worked.
Rolled back to 139. Much the same.
Rolled back to 134 and after the button reset everything started working again.
Tried rolling forward to 139 (via diagnostics and usual upgrade steps) and 140 same problem. Rolled back again and fixed.
Noticed a few people posting about Alexa and network last night. Wonder if it’s all the same thing.
All Hubitat devices are missing from Google too as of yesterday. I don't think it's connected to the Hubitat update as I'm on a different release from you.
Ah! No they're not disconnected - if I use the Google account that linked the Hubitat and Google Home in the first place, they're all connected fine. Something is wrong with my Google Home.
Edit: Upon further research this is happening to a lot of Google Home users today so it's a Google thing and nothing relevant to this thread.
If your hub is unable to connect to the cloud, first step in the troubleshooting efforts is updating the hub's time from browser, either from hub's web interface or Diagnostic Tool, then give it a few hours to see if that resolves the connectivity issue before moving into troubleshooting potential network issues.
Yes, even via hostnames, so I am confident to some degree that the DNS settings are functional. And if it wasnt clear, when I did the upgrade, it broke, I didnt change anything else, didnt tinker with my router or firewall or anything, just the upgrade. When I roll back it works. I've just done the upgrade again to test bobbyD's suggestion, and its broke, so its pretty easy to replicate the problem.
Ive done the upgrade again to 140 (as expected its broke again). I've updated the time and will leave it until 5PM to see what happens and report back.
Left it for a couple of hours, and much the same. Also spotted that ActionTiles has stopped working, which is much the same as Alexa I suppose, so I guess thats "expected", but definitely seems to be anything cloud based that I'm struggling with.
I noticed since I updated to .140 a very similar issues. Hubitat Package Manager is not working, Alexa Speaks in not working The logs show failure to resolve network resources:
EchoApp (v4.2.4.0) | java.net.UnknownHostException: raw.githubusercontent.com: Temporary failure in name resolution on line 5464
java.net.UnknownHostException: developer-api.govee.com: Temporary failure in name resolution on line 413 (method initialize)
java.net.UnknownHostException: prod.zodiac-io.com: Temporary failure in name resolution on line 334 (method initialize)
Anything that requires name resolution is failing. My name servers are setup correctly, I've been able to resolve the problematic domains from other machines on my network using the same name servers as my C8 hub.
Additionally I have a notification on my Hubitat main interface that say "Cloud Connection is unavailable. This issue has persisted for several days now since I updated to .140 and started noticing these issues.
I believe something is broke in the .140 build with respect to apps being able to access internet resources.
