I don’t think that maintenance message they have on the API has any relation to what’s not working at the moment. That message has been there for years and confirmed this with the Wayback Machine earlier.
Perhaps but it’s certain from Amazon end, as AMP and AD stop working at the same time
as chemelli say
Alexa devices doesn’t need cookies or keys to logon once the integration is configured successfully the first time
But endpoint error may prevent it to load.
Investigating on a possible workaround for such situations
It was our mistake for being so desperate to update our system right away we see 2025.7.1, now we are going to have to put up with it
and the sad part is this update was not big a deal lol
I think all users have a broken Alexa integration. Has nothing to do with 2025.7.x
i know but we upgrade and that cause a reboot, the reboot cause the integration to ask for a token again, and thats why we dont have alexa right now
1 Like
Issue is closed because it’s solved. New version 5.7.3.
Some people have some little issues or missing entities. But here everything is working again.
3 Likes
On 2025.6.x as well. After restart evetythings back again.Thanks a lot for that quick reaction. Great work.
1 Like
AMP works again with v5.7.3 
I think Alexa Devices is being fixed
Don’t want to rain on any parades here…
But my Amazon Air Quality detector disappeared on 5/6, I was running Alexa Media Player 5.7.1… I upgraded to v5.7.3 and it has not repopulated?
Any suggestions on how to resolve this?
log a issue on GitHub
thats actually not a fix, this changes makes the error handling much clearer and user-friendly, especially for debugging or logging
for error 199 and 299
2 Likes
its finally fix the 299 error , on the 3.2.8 , just test it and it work like a few weeks ago without sensors , but speak and announce works
Is this thread still active for AMP issues or is there somewhere better now?
Assuming here is best I’ve been having strange authentication issues in the last few days.
I haven’t had to re-authenticate my AMP integration for many months but in the last few days I’ve needed to basically re-auth on every HA restart.
It asaks me to open a web page that I don’t remember ever needing to go to before (sorry I forgot to fully look at the URL but it had some about alexadevices or some such) and it asks me to again enter my OTP and password. This last time I had to do the same thing three times in a row and it finally took.
Is anyone else seeing this and/or is there something I’m needing to do differently?
Hi, there are issues discussed on GitHub. I for myself rolled back to x.7.3 and its stable
1 Like
Thank you for the tip. I found commands for my fan (activated via the media_content command) stopped working with the most current version and did not return after reverting to 1 version earlier. 5.7.3 does work.
Yes finding the same thing after updating AMP.
Will try to re-install previous version as @Pirol62 suggests.
However I have the latest version on my production instance which is working ok. The only difference is that i haven’t updated the HAOS on this yet.
So is it HAOS issue? I doubt it but …
I don’t run HAOS. I run HA Container. But also I hadn’t updated to the latest version (2025.10.4) until yesterday.
I think I remember updating AMP just recently so everything is pointing to it being the AMP update that caused it.
I’ll try rolling back and see how it goes.
Thanks for the tips.
I can confirm its nothing to do with HAOS.
I reverted back to a previous version of HAOS and still have the issue.
I also rolled back AMP to 5.7.3 but that didn’t work either.
so to me this is pointing to something at Amazon that has changed.
I also note that Blink cameras were having an authentication issue which is now solved with 2025.11.0 but on the GitHub issue someone is saying that they also have issues with not only AMP but the official Alexa Devices integration
Yes, there are serious issues in Alexa Devices as well as AMP. But the issues have to be separated as fa as I see it. Some issues resulting obviously out of a too high polling frequency, especially when having both solutions active. This authentication issue must result out of other circumstances. All I can say ist, having updated to latest AMP did not work. x.7.3 works. A HA update to 2025.11 will take plaxe when at least 2025.11.3 is out
This was posted on Discord for the Alexa Devices integration and I believe the same issue affects AMP:
I tried rolling back to 5.7.3 and I cant get it to work at all now. I’ve tried logging in at least 5 times and restarting twice.
I guess it’s finally time to give up on this. unfortunately.