Just checked my logs and not seeing that error - odd!
Just checked my logs (using Alexa skill and Echo Speaks).
I do have a new error in my logs:
However, I was just able to add a new Alexa Dot (What I was just doing, coincidentally)
Yes! I had a light go on twice late last night, but there's no telling where it came from anymore.
Are your events still listed on the device page?
There is no way that the 2 circled ones actually were triggered by a concurrent command given to an Alexa (I say concurrent due to my "cached command" theory above), and the only Alexa Routine I have related to this switch is a power cycle (i.e. if the routine had been somehow triggered, it should have turned the switch back on too, but it didn't. Really odd.
Yes. My dimmer got two commands to set level from an App that is unknown, so I'm going with Alexa.
Edit: I forgot, that I did an update yesterday...
update Updated with build: 2.3.5.117 2.3.5.117 2023-03-25 01:19:12.135 PM EDT
Someone fixed it. I tried a few more times yesterday, and this morning. Just now it worked.
It should be posted in this thread;
And there is an interim solution has been posted here:
Thank you. I will move it.
And thanks for the interim solution.
1 Like
Almost a year to the day, Alexa didn't work for me again today, and of course I disabled the skill and tried re-enabling, but got the exact same error messages 
.
Question: Do you have some certificate that expired that's used to validate account linking?
Edit 1: I guess this is where it started being an issue. "Show more" yields no more results.
Alexa skill is working fine for me.
Same thing last time. A few days later it worked.
Glad to hear the Alexa Skill is working again for you.
I really don't believe anyone fixed anything on the Hubitat side of things. The most common cause for an issue like "Amazon Echo is not working" (i.e. a cloud-based integration) is that your Hubitat Hub is having an issue staying connected to the Hubitat cloud server. Often, this is quickly remedied by rebooting either the Hubitat Hub, the Network Router, or the ISP Modem (or some combination of these.)
The issue might be brought on by an automatic firmware upgrade of the router, or the ISP changing something, or the end-user upgrading their home network equipment, etc...
It is usually easy to see if the Hubitat hub is having a cloud connectivity issue by the tell-tale red alarm icon in the upper right hand corner of the Hub's web interface. If the HE hub cannot connect to the Hubitat Cloud, that issue must be resolved first, before any additional troubleshooting is initiated. Hope this helps in the future should the issue rear its ugly head again. 
1 Like
The coincidence of it being almost exactly a year later, raises some suspicion about it being a certificate or some other schedule issue. (I guess we'll see next year )
Edit 1: I should mention that while trying to link the account, I was shown my hub, but then it failed. When it did work, after the hub, it showed me the devices, that I'd checked off in HE.
There has been no interruption in Alexa service for the vast majority of us. The issue that typically causes a lack of connectivity with the Hubitat cloud is when the hub doesn’t have access to functioning name servers.
1 Like
I work from home and would have instantly noticed if DNS wasn't working. I actually have had redundant providers for the last few months, but the router on my side of the two modems is the DNS proxy server for my network.
I never said that your computers didn't have DNS access.
To reiterate what I said - "The issue that typically causes a lack of connectivity with the Hubitat cloud is when the hub doesn’t have access to functioning name servers."
One common method to prevent this from occurring (or reoccurring) is to configure the hub to use the DNS servers indicated in the Network Setup portion of Hubitat Documentation.
1 Like
I don't really want to get into a big discussion, but if the network is online and the C8 has an IP, it should be honorig the DNS server option, and that DNS server was available and functioning as expected. Further it was enabling the Alexa skill that wasn't completing, and this has happend to me now exactly twice at almost a year to the day...
This typically happens only when the hub doesn't have access to the Hubitat cloud. In 5+ years, I haven't seen other situations causing this. And lack of cloud access typically happens when there are issues, temporary or permanent, with the hub accessing a functional DNS. A search of this community would provide an indication of how frequently the latter happens.
This can be revisited if/when your hub indicates a lack of cloud connectivity.
1 Like
