-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration no longer working #2592
Comments
i have the same issue HA 2024.10.1 container. |
Same issue HA 2024.10.1 docker |
I've had the same problem, and resolve in this way:
|
Not working. It still goes to the login page |
this worked for me but goes to an error 500 screen after the captcha |
for me it goes to the username login page |
Same problem for me. @alandtse is it possible to fix this? |
for amazon.de server the same problem , endless login loop , very frustrating addition , i tried the method with creating new amazon account and after receiving the message that the account already exists i switched back to already have an account and it worked, at least for me on the german Amazon servers |
As 4.13.3 put HA into an infinite loop, it was pulled, but not before HA 2024 10.1 was updated to NOT accept any version at or before 4.13.3. If you're on HA 2024 10.1 it wont like AMP until it receives a correction release |
This was driving me crazy.. I disabled the integration for now. Just to make sure there isn’t any other option currently right? |
The only solution I'm aware of is stay on 4.13.2 / HA 2021.10.0 - I restored a backup |
I restored a backup, then upgraded core to 2024.10.1. It's been working for me. |
I restored backup as well, but integration shows initializing. |
Worked. Thank you !!!! |
Worked for me too, thanks a lot! |
For me i just Missed to Update hacs. After removing everything related to
the old Alexa Media Player, i installed the newest hacs Version and then i
used the workaround aaklan mentioned. Thx
aaklan ***@***.***> schrieb am So. 6. Okt. 2024 um 09:48:
… I've had the same problem, and resolve in this way:
- From the Amazon login page (where you will be asked for username
only and not for the password) check "Create new account"
- Put XX in the first field and compile the module with your Amazon
Account (if not already compiled), don't create a new one
- At this point a page with the message that username already exist
will appear.
- Now check the box "Already have account" and it will show a page
with Username and Password (and not only username as the first time),
- go on and everything will work (it will ask for an OTP)
Worked for me too, thanks a lot!
(For the later readers, I had difficulties to understand "compile the
module with your Amazon Account " but it meant just to press the big blue
button on the form for me :) )
—
Reply to this email directly, view it on GitHub
<#2592 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFTZGSCOLVGUKJJVMOYXXLZ2DTMHAVCNFSM6AAAAABPNLPFAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGMZTKMZVGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I dont know how u guys get the work around to work. May be I think its issue with amazon India |
I have the same issue. When trying the workaround I must enter a captcha wich turns into a 500 server error when submitted. EDIT: After a few tries it didn't required a captcha and directly prompted the 2FA |
I have the same problem. Also try to several times, but didnt get worked ps: Domain is Amazon.de |
Yesterday I installed my first Home Assistant (2024.10.1 with Docker on Raspberry Pi OS). Thanks to @LG69Domo, today I got it configured with the "create new account" workaround (on amazon.it). This time the configuration form required the 2FA code too, and I wrote one generated with my authenticator app. I also updated to the just released v4.13.4, but my device still doesn't connect... I attach a log that I tried to create: Thanks! |
4.13.4 still doesn't fix the loop to login page problem. @alandtse please look into this |
It does not work with amazon.de - Same problem as described by other users - endless loop wile logging in - Error 500:
|
The ‘create new account’ workaround as mentioned above by @LG69Domo works for me and attached devices appears to be working fine; for ‘compile’ -> ‘submit’. |
It is worked for me. Two more info: I did the setup many times and later realized that I disabled the integration some days ago and after update and authenticate, it was still disabled. |
this workaround doesnt work for me, once its back in HA it says failed |
I just tested it now and successfully added integration to my backup system. I got the same login screen after entering password again and again. Then Noticed, that URL is pointing to my local IP. So I decided to add integration from my phone and from outside network, as I have cloudflared integration. So filled all fields - in both HA access URL and public URL I added my external domain, confirmed 2FA and got all my speakers in HA. And I did not use NabuCasa subscription. |
I got this too. Make sure you’re entering the right details |
Amazon has changed the login windows for the Alexa app and the original code in alexapy/AMP no longer works correctly.
I've found that after clearing your browser's cookies, you need to log into amazon once to fulfill the captcha and re-establish initial cookies. It was only after doing that that I could then successfully complete the AMP proxy authentication otherwise I got the infamous "500 error".
This is kind of resolved with the latest alexapy/AMP version. The initial screen should now be the new customer screen with option to log into existing at which point after selecting you get the email & password prefilled on 1st window followed by the OTP prefilled window. AMP proxy auth callback only works with two screens - email & password, then OTP. Anything else will fail & return you to the first window to try again. Also, the URL being your local IP is correct as that is how auth proxy callback works. |
I think I have tried all the tricks above and some combinations of them but nothing works. I am always given a spinner that spins for a minute or two and then an error pop-up with no concrete logs. Furthermore, I checked docker's log and nothing useful too. Any idea? |
Alan no longer maintains this code and only merges PR requests from contributors... |
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
All my Alexa devices got disabled. So I deleted the integration and tried adding it again. THen it asks to login to alexaa using my amazon id But even after giving correct username and password it keeps on coming back to to the login screen
To Reproduce
Expected behavior
Screenshots
System details
const.py
or HA startup log): 4.13.2pip show alexapy
in homeasssistant container or HA startup log):Debug Logs (alexa_media & alexapy)
Please provide logs.
Additional context
The text was updated successfully, but these errors were encountered: