alexa_media_player: Experiencing endless Amazon-Captchas while trying to install integration

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I’m not not going to look at this thread anymore.

can anyone say whether the developers are working on it? it would be very nice if at least one developer could give a short feedback that they are working on it, or let it be and we have to look for other possibilities, that much should be allowed by decency, right?

Given this attitude, I’m not not going to look at this thread anymore.

please don’t listen to this comment 😃 you are doing a great job 😃 I would love to try this integration, but i also know that this integration is not your “reason to live” and I’am sure you have so much more to do in your free time than read comments like the one above and feel forced to find a fix for something, but please don’t let one “lost soul” be the reason to be mad a some users 😃

@sixdas: seems not to work for Germany (amazon.de)

Please confirm you have 2FA enabled. That is required.

Is there a solution ?

Same problem with amazon.it

I confirm the issue using the last release 4.7.9: no way to get it working.

luckily we didn’t need the arrogant developer and amazon fixed it themselves, great!

1. Me too posts are not helpful. Use +1 on the relevant post instead. I will accept new domain reports since that adds info.
2. Changing the domain may or may not avoid the Captcha request Amazon is generating. You can try it, but it’ll work until Amazon decides to give you a captcha.
3. Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.
4. Logs showing the urls being generated help the most because we can see if Amazon is taking you to a new set of pages. The auth capture proxy has a test to detect when you’ve successfully logged in. If Amazon takes you to a new set of pages, we can’t detect it.

When I look at the log, only a connection to amazon.com is established, but not to amazon.de. Does this play a role at this point or is it intended that way?

This is intended. Amazon’s apps used to always login via amazon.com before swapping to local domains. While it may change, that’s not what’s going on here. What is happening is Amazon is giving you a captcha that does not appear to properly redirect to a success page. Hence it’s endless. We solved it once before by detecting this state and automatically restarting the login procedures, but I’m not seeing any log info right now that can be used to solve it here.

Obviously, Amazon did fix something in the login procedure. I did try just the same as before, using Edge on Win11, and now it immediately worked with .de (Germany) domain just out-of-the-box without any hassles and no captchas at all anymore.

Great to see it working now!

Given this attitude, I’m not not going to look at this thread anymore.

This is an immature and irresponsible response, it’s clear you cannot work with a community.

Have the same Problem at amazon.de All mentioned Workarrounds did not work.

1. Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

When I click the submit butten (of Alexa Media Player), then a new webpage as y new tab opens up. Nothing to go back in browser history. Can you tell me exactly how to manage this?

When you submit it should get you to the alexa login site. and after you log in is when the captcha comes up. submit once. if it gives you an extra captcha, go back to the login screen. and then you start logging in and going back until no captcha is requested.

Unfortunately, this approach doesn’t work for me either. However, after submitting I go straight to the CAPTCHA. Frustrating

1. Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

When I click the submit butten (of Alexa Media Player), then a new webpage as y new tab opens up. Nothing to go back in browser history. Can you tell me exactly how to manage this?

3. Another workaround may be to enter the Captcha, and then hit back in your browser or refresh the initial Amazon login page we sent you to. Amazon may not display the captcha page again and it should work like normal.

After much frustrations, this is what finally worked for me. Thanks! Went back about 6 or 7 times (less than 10 seconds) until in one it just clicked and let me through.

Problem with Captcha always here also with 4.7.9 (amazon.de)

Same here. Endless captcha requests. Core 2023.11.0, all updates installed. AlexaMediaPlayerLog.txt

Log file is attached.

It’s working for me. After 3 weeks of testing, today Amazon changed something and now it’s working for amazon.de

Okay, it worked for me too. iPhone 12 with Standard Safari Browser and Amazon App. It worked immediately. What a lucky day! But I am sorry, that “Alan Tse” doesn’t look at this thread anymore. So he is not able to share the joy with us! And even if he reads all this silently, I guess he will not tell us?! Don’t waste your time with anger everybody out there! Peace!

Yes, with Smartphone App works! Here Apple iOS!

Great!

Same problem here 😕 Using working 2FA-Code & my nabu casa url

** EDIT ** It did work when i tried to do it in another browser! i got it to work in Microsoft EDGE.

I does it with my Handy and the HA-App. All worked fine and i am logged in 😃 And thank you for your work and time on this great integration.

Given this attitude, I’m not not going to look at this thread anymore.

This is an immature and irresponsible response, it’s clear you cannot work with a community.

he’s probably just using it as an excuse because he’s not able to fix the bug or just doesn’t feel like it anymore, then it should be maintained by other developers as well

Hello sir,

You clearly needed attention and you have many things to say. Unfortunately, in my honest opinion, your ‘many things to say’ are rude, off putting, and impolite, to say the least. I hope you get the attention that you need to choose better words to become a helpful member of the society. Cheers.

he’s probably just using it as an excuse because he’s not able to fix the bug or just doesn’t feel like it anymore, then it should be maintained by other developers as well

@Doldak Feel free to fix the issue and to send à pull Request, if you can do it better.

Try to add the “Alexa Media Player” Integration in the HA App on your Smartphone, not in the Browser. Thats the way it worked in my case. Maybe its a workaround.

Same here with amazon.de (Germany): No matter which variant I choose, I cannot bring it up to be working… NOT for the amazon.de NOT for the amazon.com NOT with clicking-“back”-approach (neither .de nor .com) Also deactivating AdGuardHome didn’t have any impact - thought maybe some DNS calls are considered being ads/spam. 😣

2FA is enabled. I’ve download againg Alexa Media Player 4.7.9 Deleted the two .pikle files Reboot HA At the end of the setup, the process stops at the screen “Caricamento del passaggio successivo per Alexa Media Player” After about 5 minutes I get a “Error” message

2FA ist enabled and OTP is confirmed after opening the Popup there is coming the never ending Captcha journey I have Duckdns running. Also tried lokal IP after I disabled Duckdns

Disabled IPv6 does Not make a change

I can agree with that. It doesn’t seem to help in Germany. I have tried both variant. (.de and .it). If i use the URL (the original one, without the proxy, it redirects my browser to a 404 Page.

I’m experiencing exactly the same, also with amazon.de; using nabu casa to access homeassistant from “outside”. I always end up on this screen, in an endless loop of recaptcha.

I read somewhere that amazon did shut down alexa for web recently, maybe that is related?