I’m facing problems, in the last months, while I try to connect Alexa Media Player in my amazon account… in the beggining it just losted connection, and I could easily reconnect it, but now nothing I did make it worked.
Considering the orientation I got in the integration page, I already tried to uninstall the integration, reinstall it from HACS and after manually… I also tried to make a connection using 2FA and without use it. In amazon account, I also tried to change my password, to clean and remake my 2FA key… in the last I tried change the Regional Domain of amazon, considering my country… absolutely nothing works…
Try this workaround from Github (posted in the forum by ColtonYYZ), it worked for me.
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 also found this post and I must say that it worked for a couple of hours… then it stopped… I then reconfigured and reloaded the integration, for now it works but I don’t know for how long.
Update, after a while restarting the configuration it works again so for now I have done an automation that reloads the configuration
Alexa media player every 30 minutes… it’s working for now, we’ll see if we need to reload it sooner or later…
@carlosead
The problem is the new three page login sequence with email, then password, then 2SV
AMP was programmed to do the callback after two pages (the way the Amazon login used to be) but gets an “unsuccessful” response after only two pages since the login sequence did not finish all three pages and AMP returns you to the previous (first) page to try again. So…
At this screen, select the first option
Enter “x x” for First and last name and click CREATE YOUR AMAZON ACCOUNT
Now you can select SIGN IN which then proceeds to the 2nd page which is Two-Step Verification
and the callback to HA will then occur where it will test if your email, password & OTP login was successful or not. If not, it sends you back to the first page in Amazon’s new 3 page sequence…
Still not working for me. I’m going to give up on this integration, I’m spending way too much time trying to troubleshoot it and research for solutions. After I was able to get past the username and password request page, I was prompted for the OTP and it seemed to work fine. I went back to HA and the integration cannot be found. Rebooted HA, tried again, still the same… any other who had the same experience?
I’m confused by your sequence of events. When you were prompted for the OTP, it should have been prefilled and you just click SIGN IN at which point that tab closes and the Home Assistant tab then reappears. You do not have to manually go back to HA.
Hey, thanks for replying me. This is the exact sequence of events:
Installed latest version of AMP from HACS after uninstalling it and making sure the folder was not existing anymore in the custom_components folder
I added the integration in the integration page and entered all the required info: domain, email, password (left the rest as default)
It then opened the sign-in page and I was able to get past it with the workaround of the fake name, otherwise it was stuck in a loop
I was prompted for the OTP and entered it
I got the successful page and it went back to HA but the integration was not installed and I was not prompted to select the entities as usual
I’m not getting this screen like you though
Perhaps it depends on the domain? Not sure. Anyway the process I described above is the usual one which always worked fine, I have no idea what’s wrong this time…
This is your problem: (left the rest as default). You need to enter the app secret so that AMP can self-generate an OTP code. The OTP code is not just required during onboarding but is necessary for AMP to be able to re-login to Amazon when it needs to reauthenticate.
It might be, but I never had to do this and I was always able to configure it successfully. Anyway, I ran out of options, so I’ll give this one a try. Thanks!
Click on Can’t scan the barcode? and the 52 character app secret is displayed.
You then have to enter the generated 6-digit OTP code from the authenticator app (alexa media integration) to successfully Verify OTP and continue adding the additional app to your Amazon account.
There’s absolutely no way I can get this integration to work. Tried with OTP, without OTP, tried the account creation workaround, uninstalled numerous times… Definitively wasted too much time that I don’t have on this. I just gave up and removed the related actions from all automations and scripts. I’ll get back to it the day all these issues will be definitively fixed.
I was in the same situation as you, stuck because Amazon kept saying that the OTP code generated by Home Assistant was always incorrect. I tried restarting all OTP apps, reactivating two-factor authentication, and even changing my email, but the problem persisted. Finally, I decided to remove the integration from HACS, restarted HA, reinstalled it, and this time, everything worked by following the steps mentioned above to try adding your existing account.
trust me I did everything I could try. I’m not really a “newbie” (not a developer, but a sysadmin since 12 years, so not really new to the field), so I literally tried everything.
I was able to get it configured and it looked like it was working, but after a few days it began to give again the login issue with the API and multiple warnings appeared in the integration section of HA, so I finally gave up. It’s too bad I was using it quite often and quite happily, but cannot spend time on staying behind updates, workarounds and so on anymore, so I just removed it for the last time and using HA without it since a few days.
