Today i realized my Alex Media Player Integration was not working. I check my home assistant dashboard and there were updates for both core and AMP. I’m currently running:
Check which version of alexapy you have. To check:
open /custom_components/alexa_media_player/manifest.json
make sure the version for alexapy is 1.28.2. If not, change it to this
If that failed, try this workaround someone posted on Github:
Through trial and error trying to figure out the flow sequence, I was able to trick it and get to the OTP window.
After you’ve cycled through name, password and back to name, select the option Create Account New to Amazon? Fill in a first & last name (anything at all as not going to matter so “Q W” is quick and easy to type!)
Amazon will then inform you that an account with your email already exists.
At that point re-select “Sign in Already a customer?” and proceed with the email and password windows and then the OTP window should appear.
By that point though, the integration generated OTP has likely expired but you can just enter your current app generated OTP code and it should work.
If it returns to the integration add window and it just sits and spins and never progresses, that likely means the proxy listening session has expired and you’ll have to repeat the process.
I had to sign in first which brought me back to the login page and then clicked on create new account. Kept the email in there and tried to create the account it said it already exist. Clicked back on sign in to existing account. When I clicked on it this this the username and password fields both were visible usually you have to enter one at a time. Entered my creds and it worked!
Hi, I am struggling with this so any help appreciated. When I try and add the integration its all good, asks to open the page, I enter my Amazon login info (with amazon.co.uk) selected at top as UK. It then goes to the page to enter the text code to stop bots but every time it then just says server error 500. Any ideas please anyone as really want to integrate my Amazon AQM. Thanks
I checked twice the idea of changing the ap version to 1.28.2 like above but then it doesnt even send me to the opening a new page to login, it just fails with same error in a window straight away:
Error
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble
Ok, having read more I see the issue and I don’t have 2 factor on my Amazon account and see it also has to be via a self provided authentication app so I think I am put off now as several family members use Amazon.
This is driving me crazy! I’m stuck in a loop. If I don’t get the 500 error, i get this: Alexa Media Player - Unable to Connect to HA URL
My URL is correct and verified. Why does this have to be so complicated? Can someone please fix this so idiots like me can connect to my Alexas? I’m not an expert, but I’m not a newbie either… Why is it so complicated to make it work properly? Was working fine for a long time…
I have the same. I expect it’s a problem with HA25.11 compatibility and there will be a fix soon. However it’s really annoying as all my automations that have a TTS response ( e.g. “dishwasher delay set” ) have stopped working.
Same - tried all methods and failing to login even after OTP stage reached and correct code entered. Assume it’s an issue with latest HA update to 25.11
The Alexa login issue was present before 2025.11 and AMP 5.7.10. It appears as if this is an Amazon issue and nothing to do with Home Assistant. Something has changed or stopped working on their authentication servers - so we might just have to wait until they fix whatever is broken - or get an update to AMP which reflects a different login/authentication method.
Just for clarification, does this same Login problem happen with the NEW Alexa Devices integration? If not, this may be my signal to start changing over.
In my case this issue appeared this morning before updating HA to 2025.11.
In particular I updated some docker stuff in my debian environvent first; this leaded to a HA restart (was 2025.10.x) and the AMP logout appeared.
