Cloud access not working

TBH I don't know. I've only ever used ethernet and have a DHCP reservation on my router so I've had no need to investigate the network settings.
I think people have had issues when they try to use Ethernet and wifi at the same time.
i.e. they've enabled wifi and left the Ethernet cable plugged in.

It sounds like you are not doing that so I would think that is not your issue.

1 Like

Your attempt to ping cloud.hubitat.com failed. Try to ping the IP address of 13.33.165.34 instead to eliminate the possibility of a DNS lookup error. You might as well try pinging google.com as well to prove the issue isn't isolated to only the hubitat server.

Next try to ping your home router at presumably 192.168.0.1 to see if you have a routing problem. Can you ping the hub from your laptop which would also help diagnose the problem.

how do you ping any Ip from Hubitat hub ?
next time problem happens I can try pinging cloud.hubitat.com and the 13.33.165.34 IP

Open -"Settings", select "Network Setup", and then "Network Test" in the top right corner. There is a screen image in post 14

I created a video (sorry, it's a bit long; about 4 minutes long) showing my intermittent success when using the Hubitat Ping utility. I also show my laptop on the same network with a 100% success rate pinging the same resources. Hope it is helpful.

Link to video;

YouTube Video

Regards,

-peter-

Ok. Now I don't have the issue.
I'll try this when it occurs next time.

Just reboot your router. U can get the issue at will.

I started having the issue this morning. The hub has been flawless for years. Never had this issue before. C7 on 2.3.9.158. Saw there was an update to 166 and it wouldn't update and started this mess. Tried rolling back to other FWs but nothing.

1 Like

As I already stated, there is a problem which is being ignored.
But when it is Hubitat, I am used to being ignored...
welcome to the jungle...

The last thing you said was that the issue had resolved on its own.

What are you expecting?

What exactly is the issue, as you see it?

Respectfully, I see three users that have had some kind of cloud access problem with their hubs. And very little else. That’s essentially just a symptom, and could have a million underlying causes, none of them necessarily related to one another.

The OP has acknowledged it’s intermittent and sometimes resolves on its own.

How do we even know @peterbransche and @bob20 are even dealing with the same “issue” as the OP?

well , as you said, the issue is intermittent. I don't know when or if it will happen again.
I am not comfortable. I am expecting someone from support check the issue and try to find the root cause.
It all started after a firmware update for me. Probably something about cloud access has changed. Maybe Hubitat servers uplink has changed. I don't know.
I am a network professional for more than 25 years and I know that no problem arise without a change.

Thanks for the reply! I would like to have my Hubitat router connected via Ethernet; however, that does not work for me. I have tried several times to connect via Ethernet and every time the Hub is unable to discover my two Konnecgted boards. I feel that an Ethernet connection would be more stable but, so far, have been unable configure Hubitat via Ethernet.

-peter-

Cloud connection not working is the issue. I have had an OPNSense instance set up and working for months with routers as APs running ASUS-Merlin in AP mode. I changed from those to Cisco APs and had both APs running for a few days while testing the Ciscos I removed the ASUS-Merlins and the issue started this am. The ASUSs were removed yesterday and Hubitat was running fine.

Currently ping fails or drops 1 or 2 of 3 packets to both 1.1.1.1 or any other external IP and the router 192.168.1.1. Traceroute and speed test are also hit and miss. If I try to update the hub to the latest FW it either tells me there is no update or it fails. I was finally able to update by moving the hub to another network entirely. When logging into my.hubitat.com the hub does show even on the network where it has issues. I can access the diagnostic tool and the hub ui and I have tried downgrading FW as well as soft reset and uploading a backup from well before the issue started.

Nothing in the router/firewall was changed when changing out the APs with the exception of assigning the Ciscos new IPs. But the rules, etc are all the same so I don't understand how changing out a few pieces of hardware would cause a failure to connect.

1 Like

Its not intermittant. I reported it and was ignored. Everytime i reboot the router everything works including dns but i loose cloud access. Its repeatable on one of my hubs.

For you.

But if someone else has reported an intermittent issue, does that mean it’s the same underlying problem? Or possibly different problems?

You’re a network professional, what would you suggest if someone reported a bug to you with a problem that was intermittent and had no steps to reproduce?

To me/my opinion the odds are its the same issue and if they tested by forcing their router to reboot it may be reproducable. I also expected someone to at least look at the engineering logs and see if they could isolate the issue.

I'm not sure if any of the posts above have tagged HE support so I'll do it just in case.

@support-agent @bcopeland @bobbyD any chance you can look into this or more importantly, has any changed in recent updates that could cause this issue to manifest itself.
Personally, everything is OK for me but others seem to be encountering issues.

Don't you think this would affect far more people if that were the case? Nothing in the change logs indicates that anything has been done with AWS and they're pretty transparent about that. As a network engineer myself when I see things like this, especially at the consumer level it's usually a router or a switch issue (though rarely a switch). I also see this with wifi on occasion. Now as to wifi I could never be sure if it was Hubitat or an AP with people. In the end I just recommend hard wiring it. Really if you want to diagnose fully on your own network, set up wireshark and watch what happens. You'll get a better idea of whats going on.

Have you put in a ticket?