I sent you a private message to get more details.
2 Likes
Yes, clock is set correctly. Sorry I forgot to mention that earlier.
When I do this, it comes back as “failed.”
Here is what my DNS looks like:
Turn off the well known dns and click the use router provided button. Might have to reboot.
Then check things again to see if it will connect to cloud.
Could also test by only putting 1.1.1.1 to in for the DNS.
Sort of running out of ideas.
@bobbyD was able to get it connected back to my account - it looks like the local IP was missing.
Now I’m back to my original issue where the hub shows as offline when I go to my.hubitat.com even though I can access the hub through the IP address.
Any ideas on this one? It won’t let me access the hub through the app since it’s “offline” and I’m unable to link it to Google Home since Google is looking for an online hub.
Did you try my suggestion above with the DNS?
Sorry, yes I did - turned off well known and separately tried 1.1.1.1. Still showing offline though 
Is there anything else that could be causing this to show as offline beside the DNS? @support_team
Did you ever reply to the PM from @bobbyD ?
If not getting anything back I would send in an account request if you have not done that already: Account Issues – Hubitat Support . Or make sure you have replied if you have an open case already. Use other category and give them a link to this thread to show your troubleshooting so far.
Somewhere it was said they have seen this before in some cases. Maybe they have to fix something in the back end so the hub can reconnect to the cloud? Usually once you can ping a domain name it works fine, so not sure what else it could be.
If you are running and sort of firewall or domain blocking I would turn all that off so the hub has a clean internet connection.
1 Like
I was able to solve the issue thanks to help from Hubitat support.
My internet gateway is AT&T’s BWG320-500 and I have it connected to the Deco X55 mesh setup as access points. At some point, the AT&T gateway had marked the Hubitat as a blocked device so it was not allowing any non-local traffic. Once I unblocked it from the gateway end, all the issues resolved.
2 Likes
Its not very good at its job, it still lets ping and DNS through... you were able to ping both an IP and a domain. That's what made it so confusing.
Guess we need to think of an easy way to test an http call from the hub.
@bobbyD @gopher.ny would it be worthwhile to add a "Test Cloud" to the network test or somewhere, that can try the cloud https connection and give back a response of what is going on? Right now its juts a black box and no one can see what is happening.
3 Likes
