Something seems to have changed on Amazon side of things. I now also see this in my app and logs. Never had an issue before and Echo Speaks is working properly.
It seems that per the error, and looking at the corresponding lines in the app code, the app no longer seems to like the response returned for the cookie auth status.
@tonesto7 perhaps you can take a look at things when you have a moment?
Hubitat Elevation voices in Setting > Hub Details.
@jtp10181 ... I've restarted the container, and at the end of the text run of the container it states the cookie was sent successfully. However, the red X on the Auth Status does not go away. It looks like @jkudave is having the same problem.
I think there may be something going on with the Amazon side that is not allowing the app to work nicely with Amazon.
Below is a screenshot of the Amazon Page. Should I try to clear login status and try again?
Everything on the page of the app looks good
But still the red X on this page of the app
Seeing same thing on mine.
You aren’t doing anything wrong. This appears to be something new on Amazon’s side of things. If things are working, leave them be. Either it will get sorted on its own, or @tonesto7 will need to take a look when time permits.
Thanks you..... Leave it alone is great advice I need to hear often.
Same. Curious if they went to a similar change as Blink using OAuth2 authorization. Might take some time to resolve.
weird it stays in the server logs it got the cookie but cannot validate it.. 404 error .. not sure what it does to validate but it seems the url has changed.. wonder if it is the alexa plus crap?
how long can this go on before stuff stops working.. its been 3 days now..
Not sure if it is Alexa +, but it definitely appears to be something on the Amazon side of things.
Only @tonesto7 can answer that. However, it seems that cookie refreshes are successful despite this error/warning.
You are correct. My last cookie update does show 1 day 1 hour and I have been getting the error since 11/6.
I have not done anything with Alexa+. Been getting emails and seeing stuff on my Alexa Show about getting early access to Alexa+. Has anyone done the "upgrade" and if so has it had any effect on Echo speaks or Hubitat Alexa integration in general.
I did the upgrade and had nothing but problems with the integration. So I removed it. This was back when they first released, so maybe it is better but I am not taking the chance for a while. It is a bit odd now that when it speaks I get 2 different voices. Old voice says 1 new message, new voice says what the message is. Almost like what happens in my own head 
I am curious if anyone else is using + successfully now.
My Echo Show proudly announced that Alexa+ was currently available at no charge after I asked it to do something else. I declined the upgrade.
any update on getting this fixed?
Same for me too
I wouldn't worry too much about this. Cookies are being refreshed and the app continues to work. It's just a matter of the authorization health status in the app not working. It's more of a cosmetic check than anything else, as far as I can tell. I don't know if anyone other than @tonesto7 can fix this, and it's essentially up to him to be able to find the time to address the issue. My take is that at some point, sooner than later, the ES app will need a bit of a re-write.
This is stopping me from getting the first Cookie at all and so is not ever working on my side
You seem to have something else going on. I don’t know why your setup is trying to get to https://registry.npmjs.org/echo-speaks-server. I’ve never seen that URL before. I suggest rebuilding your ES server instance.
Amid the recent flurry of activity on this thread, is there something I can do to help ES recognize my new Amazon Echo Dot Max (released first week of Nov '25) as a device? ES lists it but shows as "Offline", as if it doesn't yet know what do with that model.
Download the Hubitat app
