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