Does this integration work anymore? #2315
Replies: 18 comments 22 replies
-
|
Same on my site. I got this integration in trouble in late june 2024. Today I realized that most of my echo devices are there with double entries. So I removed the integration, restarted homeassistant and got the same as @mikemccomas. |
Beta Was this translation helpful? Give feedback.
-
|
maybe I fixed it now, but then the description is wrong? @mikemccomas This lead to the behaviour above! I rebooted my HASS, added the integration again and left the amazon.com as the default value, now it works! |
Beta Was this translation helpful? Give feedback.
-
|
I live in the US so I just left it as amazon.com. I tried completely uninstalling the integration (instead of just removing the devices), then rebooting HA but still no luck, |
Beta Was this translation helpful? Give feedback.
-
|
I do't think it's a chane in the Amazon API. I went back to HA 2024.7.4 and Alexa Media Player works again. At least after reconfiguring it. |
Beta Was this translation helpful? Give feedback.
-
|
same trying to set it up after upgrading my hardware to HA yellow. |
Beta Was this translation helpful? Give feedback.
-
|
It isn’t working for me either. When I try to enable it it gives me an ‘unknown error”. It was working a few weeks ago, but now I cannot enable it at all. |
Beta Was this translation helpful? Give feedback.
-
|
Me either. Thanks to everyone for taking the time to attempt to fix this. |
Beta Was this translation helpful? Give feedback.
-
|
Tried everything and all I get is “Unknown error”. Please fix!! |
Beta Was this translation helpful? Give feedback.
-
|
Started working after latest update! Did a full re-install and it connected. |
Beta Was this translation helpful? Give feedback.
-
|
It stopped working for me after the last update. I'm going to rollback when I get home to test. |
Beta Was this translation helpful? Give feedback.
-
|
Same issues as reported by others. Setup failed message when loading. Reloading it use to "fix" this issue but it simply does not work now. Try to delete and reinstall. Encountered the same issues other reported with the 500 error. I am not sure what changed other than the latest HA assistant update today. I had updated the Alexa Media Player to the latest version. Not sure how to get my 2FA key now as well, from Amazon right? Followed all the steps and I cannot find it but 2FA is in place. sigh... Appreciate any possible solutions. I liked this integration! |
Beta Was this translation helpful? Give feedback.
-
You can't get it after the fact from Amazon. If your authenticator app does not yet you see the TOTP secret and you failed to save it when the QR code was first presented, you are SOL with that one. However, you can just add another app to your Amazon account and capture the secret for its QR code when it comes up. |
Beta Was this translation helpful? Give feedback.
-
|
Mine is broken after todays HA update, however, my Alexa scripts still run even though Media Player is showing failed to set up |
Beta Was this translation helpful? Give feedback.
-
Mine did the same but a full reboot seemed to fix it. |
Beta Was this translation helpful? Give feedback.
-
|
Same error with 2024.8. I modified the file manifest .json --> "alexapy==1.28.2" + reboot, and it seems to work but it's not stable. |
Beta Was this translation helpful? Give feedback.
-
|
I have done a full reboot of my Pi but still getting the error but Alexa still seems to be working |
Beta Was this translation helpful? Give feedback.
-
|
Hello there, after running into the same issues like described in the posts before, i completely removed the integration from my HA instance and re-installed it. It wouldn't correctly install yesterday but today it seemed to work. At least i got no errors, the integration showed up correctly and all of my devices were added to my HA again. |
Beta Was this translation helpful? Give feedback.
-
|
So i found the solution myself, maybe it helps someone. I deactiveted the integration and activated it again with 'amazon.de' instead of 'amazon.com'. (i live in Germany, of course) |
Beta Was this translation helpful? Give feedback.
-
Try deleting the pickle file in .storage and restarting HA. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, but it after still not working after yesterday's update where "alexapy==1.28.2" was fixed. |
Beta Was this translation helpful? Give feedback.
-
|
I've uploaded 4.12.7 (it now works) and sat on 2024.7.4 (I haven't upgraded HAOS to the August release yet) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for fixing this. It was only a few days, not bad at all. Love this plugin. One request: On the HACS page for this addon, I do not see a link to buy you coffee. Please add this feature as it is lacking a way for any of us to donate towards this plugin. This is a lacking feature and I will only give you five stars. I would give you 10 stars but it is lacking the donation button. At least, let me buy you a cup of coffee, okay?!!! :) I was trying to be funny. If there is a link, I do not see it. lol |
Beta Was this translation helpful? Give feedback.
-
|
Yes thanks, latest update seems to have fixed it for me too, nice one |
Beta Was this translation helpful? Give feedback.
-
|
Is it safe to upgrade to 2024.8.x.yet? thanks |
Beta Was this translation helpful? Give feedback.
-
|
so I have 2024.8.1 running, latest OS Update that was released today (version 13 if I'm right). Always 403 forbidden |
Beta Was this translation helpful? Give feedback.
-
|
here we go :) I'm not entering the 2FA in the config during the integration installation, I do it (at that it what I would have done as many years before) in the upcoming browsertab where I have to enter everything. |
Beta Was this translation helpful? Give feedback.
-
AMP has no idea what you are doing in the separate browser tabs! Those are strictly between you (your browser) and Amazon. Your procedure will not work as AMP has no way to authenticate with Amazon EVER since Amazon does not permit legacy email/password only logins when Two Step Verification is enabled on the account. You must provide AMP with the OTP secret so that it can generate the OTP code on its own. That's the reason the AMP auth verification process requests confirmation that the OTP it's about to provide to Amazon is correct and that it can safely store the OTP secret and use it in future internal authentications with Amazon! |
Beta Was this translation helpful? Give feedback.
-
|
so you mean I have to enter the seed code that generates the 2FA 6 digit codes, OK I have done this, now I get this message I verify that the code is correct on my 2FA app and it is (and there are 15sec + left before it changes again). Still 403 :( Log looks like this: 2024-08-16 14:26:04.564 DEBUG (MainThread) [custom_components.alexa_media.config_flow] Creating new login
2024-08-16 14:26:04.564 DEBUG (MainThread) [custom_components.alexa_media.helpers] a****n@g***********e: Returning uuid {'uuid': 'f94f7e499ee4048c8ee30633983e8469', 'index': 0}
2024-08-16 14:26:04.570 DEBUG (MainThread) [alexapy.alexalogin] Creating TOTP for Z************************************************6OA
2024-08-16 14:26:04.571 DEBUG (MainThread) [alexapy.alexalogin] Generating OTP 811666
2024-08-16 14:26:04.571 DEBUG (MainThread) [alexapy.alexalogin] Login created for a*******@*******de - amazon.de
2024-08-16 14:26:04.584 DEBUG (MainThread) [alexapy.alexalogin] Generating OTP 811666
2024-08-16 14:26:04.584 DEBUG (MainThread) [custom_components.alexa_media.config_flow] Generating OTP from 811666
2024-08-16 14:26:12.766 DEBUG (MainThread) [custom_components.alexa_media.config_flow] Starting proxy for a****n@g***********e - amazon.de
2024-08-16 14:26:12.766 DEBUG (MainThread) [alexapy.alexalogin] Attempting oauth login to https://www.amazon.com/ap/signin?openid.return_to=https://www.amazon.com/ap/maplanding&openid.assoc_handle=amzn_dp_project_dee_ios&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&pageId=amzn_dp_project_dee_ios&accountStatusPolicy=P1&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns.oa2=http://www.amazon.com/ap/ext/oauth/2&openid.oa2.client_id=device:663934663765343939656534303438633865653330363333393833653834363932333431333234393536346335363335353634643332353733383331&openid.ns.pape=http://specs.openid.net/extensions/pape/1.0&openid.oa2.response_type=code&openid.ns=http://specs.openid.net/auth/2.0&openid.pape.max_auth_age=0&openid.oa2.scope=device_auth_access&openid.oa2.code_challenge_method=S256&openid.oa2.code_challenge=tiA867xJnaCpf70tNOU9iM_iGFsCxF9xK9EP6PDhecg&language=de_DE
2024-08-16 14:26:12.775 DEBUG (MainThread) [alexapy.alexalogin] Generating OTP 811666
2024-08-16 14:26:12.775 DEBUG (MainThread) [alexapy.alexalogin] Generating OTP 811666 |
Beta Was this translation helpful? Give feedback.
-
|
I tested it again with a complete removal of my 2FA stuff on amazon and recreating one new 2FA code. Still the same :( EDIT: For sience: I removed the 2FA completly and then tried again without providing anything besides username/password and right localtion URL. same! |
Beta Was this translation helpful? Give feedback.
-
|
ok I was just "stupid"... layer 8 problem ;) this is how the integration looks like on the setup page before I enter anything... you see my local and WAN DNS here. I always change the upper one to the WAN one and the lower one to the local one. BUT there is no https in the front of the URL. Long story short that was the issue for 403 :) |
Beta Was this translation helpful? Give feedback.
-
|
Broken again. It seems like it breaks every week. Unfortunately, it messes up my other automations. I get it, it's free and people are trying their best to maintain it in their spare time as a passion project and unless I'm willing to start committing some code, I have zero room to complain. I'm just wondering if it's something that Amazon is doing with their API to make it difficult to keep this thing going? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, any news? |
Beta Was this translation helpful? Give feedback.
-
|
Have exactly the same problem, my HDD on my HA failed, and had to start again, now i get the same issue over and over, stuck on Welcome, sign in Already a customer? loop. if i anyone has any ideas that would be great. |
Beta Was this translation helpful? Give feedback.
-
See issue #2514, specifically my workaround which is to select Create a new account which will fail, then reselect login to existing account which will then give you a window with both email & password on the same screen like it used to and then the OTP window will follow after that. Amazon has changed the login window structure and AMP is now befuddled with the email, then password, then OTP sequence as it expects email + password, then OTP, then return back to me. |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks, I will try the workaround as soon as possible. In the meantime, I downgraded HA to version 2024.7.4 and everything works again. Regards |
Beta Was this translation helpful? Give feedback.
-
|
thanks @danielbrunt57, it did the trick, i have added Alexia Media Player to HA with your work around. Thanks again for your help. |
Beta Was this translation helpful? Give feedback.
-
|
@danielbrunt57 Your workaround worked for me too after agonizing hours of trying. Many many thanks! |
Beta Was this translation helpful? Give feedback.
-
It worked for a few months but now, both of my Echo devices are no longer available. It says Failed to set up. Tried re-logging in to Amazon and it still said Failed to set up. Tried removing and re-installing. Now it just says 500 error, the server got into trouble whenever I try to log in and complete the re-captcha.
Beta Was this translation helpful? Give feedback.
All reactions