Device: C-5
Platform: 2.4.3.158
I recently redid some internet settings in my house, so I disabled my Alexa skill in Hubitat (which was working perfectly). When I went to Enable it through the Alexa app, it took me to a place to log in to my account, which I did, but before it got anywhere, it said "Unable to connect the skill at this time." I could really use some help to get this back to being connected!
Thanks
Jon
Can you check if your hub is connected to Hubitat's cloud? And if it has access to a DNS?
It that the paid cloud service? If so, I haven't ever been signed up for that and the Alexa skill has been working for a couple of years no problem. If it is something else, I'm happy to check, but I'm not sure how. As far as the DNS, how can I check? I'm hardwired in, and run all the network tests on both 1.1.1.1 and 8.8.8.8 and they're good.
I'm still having issues with this. Can anyone help? I'm not sure if it is related, but when I go to my Registered Hubs, it's saying "Guest account detected" even though it is my main admin account.
I think what aaiyar meant was to go to the Settings page, and then Network Setup option. In the upper right corner of that page, there is a Network Test button. See if you can Ping Hubitat.com and Amazon.com ,
You also should check My Hubitat and see if the hub appears to be offline or online. You can click on the Hub Details button to see when the last time the hub checked in.
Is there some possibility that your network router has updated recently, or some "network security protection" or "network virus protection" has become enabled in your router?
Did you ever find a solution for this?
Not yet, unfortunately. And I haven’t been able to get a direct contact with anyone at Hubitat for tech support.
It would help us to help you if you could answer some of the previously posted questions.
The Hubitat Alexa Skill requires the Hubitat Elevation hub to be properly registered with the Hubitat Cloud Server (no subscription required). It also requires that the HE hub have unfettered access to the Hubitat Cloud Server. Often complex home network configurations with VLANS, Firewall Rules, and/or double NAT can cause connectivity issues.
I have been using Hubitat since early 2018 and have never experienced persistent issues with the Alexa Skill. Every once in a while, there will be cloud outages (mostly on the Amazon side of things) that cause widespread Alexa outages for Hubitat and other home automation platforms.
I’m guessing this opening line in the first post played a role.
OP, specific details about the changes you made would be helpful in diagnosing the path forward.
Originally I had just a standard 192.168.1.XXX setup. I have (had) the Netgear Orbi, so I decided to utilize the 4 IP’s and create a IoT one, which I put the Hubitat on (192.168.30.XXX). At that point, I can’t remember why, as it’s been a while, I removed the Alexa Integration from Hubitat and reinstalled it. That’s when everything broke. Now, I’m back to the single 192.168.1.XXX setup, but it’s still not working.
I just checked a ping to both hubitat.com and amazon.com and they’re both coming back “ping failed.” I checked on cmd and it was the same. 8.8.8.8 and 1.1.1.1 are fine
New router is an Eero Max7.
Apologies, neonturbo, as I didn’t see your reply from the other day until now.
A little more: the findmyhub.hubitat.com finds my hub right away.
Thanks for the reply. I’ve been with hubitat since 2019 and, honestly, have loved everything about it. This is the first major hiccup I’ve had with it. Hopefully I can get it resolved as my family has gotten so used to the “Alexa turn off the lights” and now they have to hit a physical button instead. 
This means your hub does not have access to a DNS (which I pointed out in my first response to your post).
Without access to a DNS, Hubitat will be unable to connect to the Hubitat Cloud, which is necessary for the Alexa integration to work.
In your hub’s network settings, make sure that the switch that permits use of well-known DNS providers as a backup is selected.
I checked on the hub, and that toggle was already enabled. I also checked with cloud.hubitat.com on the Network test, and that was successful. Not sure if that is different than the regular hubitat.com.
I’m not sure if it is related, but I’ve also been trying to reach out to Hubitat about the user name issue I’ve been having for a very long time. I started with relatively early, and there was a point when the “mixed case” emails were resolved. I’ve messaged the forum about that, contacted the support email, but I’ve only ever gotten one response, which didn’t fix anything. I won’t get into it, if that wouldn’t be an issue here. Like I said in the beginning, the skill had been working for years up until January.
