I am a brand new Hubitat owner (C7). I have tried to get my Alexa app to connect but it keeps failing. Then I noticed in my Hubitat portal, I see a message that says "Cloud Connection Unavailable". Is this my issue with Alexa, and if so, how do I fix it? I have registered my device and I set the IP to static using in the Hubitat network settings.
That could be related. Are your default gateway and DNS server properly configured if your set a static IP on the hub side? You could try a DHCP reservation on your router instead if you aren't sure. (Or you can temporarily revert to DHCP to see if the problem goes away, then you figured out the cause.)
Neither is strictly necessary, though either can make things easier. This is just my guess as to what may be wrong.
4 Likes
Probably a great question for @bobbyD from the Hubitat Support Team. Your hub definitely needs a reliable connection to the Hubitat Cloud server in order for the Amazon Alexa skill to work.
2 Likes
You know, when I setup the static IP, I left the DNS server at the default 8.8.8.8, basically because I didn't know any better. I guess I need to find out what that needs to be set to.
8.8.8.8 should still work if you don't have a preference.
2 Likes
Please reset the networking settings on your hub by holding the button on the hub for 10 seconds, then allow your DHCP server to assign a new IP address. If that doesn't resolve the cloud connectivity, you may want to "Update the Time from the Browser" as that is the only thing that might prevent the hub to connect to the cloud that is in our control. Other than that, the problem might be within your local network. You must be able to connect to the cloud in order to link devices to Alexa.
1 Like
Thanks much. I will give that a try this evening.
1 Like
Do this instead. Set hubitat to DHCP and do a reservation in your dhcp server on your router instead. See if that corrects your issue
2 Likes
I appreciate the suggestion, but I really don't know how to do that in my router. It is a Unifi Edgerouter X and I have 1 Unifi Access point. But when I set up the router original (4 years ago), I was able to use the Basic Setup wizard. I've poked around in the router setup, but I just don't really know what I'm doing there. Was really looking forward to using this Hub, but if I can't get this part to work, my wife is gonna nix the plan! :slight_smile
I tried this as well, but to no avail. What I don't understand is that I was able to register the hub, upgrade the firmware, and such, but I can't connect to the "cloud"? I have a Ring Base Station on the same router, which has always worked just fine. I swapped ports with it and the Hub. the Ring works fine on the new port, but the Hub still gives me this error. What else could I be doing wrong?
I highly recommend doing this and it will likely solve your issue.
and
Wow, doing the DHCP server Static Mapping change did the trick. In my Edgerouter, I already had a DHCP server of course. I went to the leases page on that DHCP server, and found my Hub in that list (based on IP and MAC address). I then selected "Map Static IP", and that was it. I left the HUB networks settings to continue using a static IP address. It works, so I assume I should leave it this way.
This is interesting but a but a bit frustrating. I am excited about the power of this HUB, but didn't expect network problems such as this. I am moving from a Wink v1, so obviously local control and rule set options are going to be fantastic. But I never had basic network and cloud issues with Wink. Maybe Hubitat is working toward to make it easier to deploy for a non-network savvy guy like me.
Thanks much for the help everyone!
3 Likes
Networking equipment can be different. Likely setting the hub for 100mb instead of auto would have solved this. It's not a hub issue it's a swtch issue (your edge router/switch in this case) and not something that Hubitat (or anyone else) can really account for. All they or anyone else can do is adhere to standards as closely as possible and hope everyone else does too.
1 Like
After a Hub software update, we wanted to reconfigure our network. This included changing our network address ranges, and on the router we assigned a new/different IP address for our Hub. We can log in to the Hub using the new IP, and see all the devices, but now we have "cloud connection unavailable".
The hub is wired to the Netgear router, with a static IP.
We have a 2.4 and 5g wifi, and I can login to the hub from my phone on 5G wifi. But I cannot "Find" my hub on the lan except through the advanced find by IP address. When I use the MAC address I see an unavailable hub with the old IP address. The old address is NOT an attached device in the router's list and is not in the range of addresses for DHCP, so is not in use by other devices...
Another twist; the Hub was originally registered with my husbands email account, and we can login to my.hubitat.com with this account, but the hubitat android app gives a message about "accessing user data" and never completes the login.
We have had the Hub for a few years, working fine, linked with Google. BUT every time we update the Hub, we have to relink with Google. Now we cannot do that with the "cloud unavailable". BTW when I login to the Hub, and use the network test, pings & traceroute all work just fine.
We are so stuck! Help appreciated!
Do the network reset procedure outlined here. This only resets the network settings, and is not a hub reset, so you shouldn't lose anything.
About 1/3 of the way down the page in the blue box. Network Setup | Hubitat Documentation
2 Likes
Did you configure the Hubitat hub’s Network Settings to use a static IP address? If so, please update the DNS a server settings as well on the same page. While it may have default addresses shown, they sometimes do not take effect until typed in again.
Using DHCP with a reserved IP address on your router for the Hubitat hub is really much more of an error-proof approach.
2 Likes
