alexa_media_player: 500 Internal Server Error - when adding Alexa integration without 2FA
Describe the bug
Alexa media player stopped working for a few days.
Adding Alexa integration from scratch throws a server error after the code challenge from the amazon autthorization proxy page.
To Reproduce
- Start a new installation of the Alexa integration
- Follow the HA Alexa login form (skip the optional 2FA built in codes) and open the proxy
- Sign up with the Amazon credentials and complete the code challenges
- See error on: https://the.ha.domain:8123/auth/alexamedia/proxy/verify
Expected behavior
If this always throws a 500 Internal Server error, it would be ideal to make the Built-in 2FA codes field to be mandatory.
Screenshots
System details
- Home-assistant (version): all versions since 2024.2 up to 2024.3.4
- alexa_media (version from
const.pyor HA startup): [4.9.2] - alexapy (version from
pip show alexapyor HA startup): - Amazon 2FA is enabled (y/n). <!—We will not debug login issues if unanswered—>: N
Logs Please provide logs.
Additional context
Versions of HA back from 2024.2 still have the same issue.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (1 by maintainers)
Yep, same here, turns out this is the error you get when the wrong password is used and Amazon doesn’t tell you you’ve got the wrong password, just shows the captcha screen then you get redirected back to HA to find the 500 error.
I got this working! Turns out I was using the wrong Amazon password to login (oops!). With the correct password supplied I get the authenticator code screen presented rather than the captcha. Enter the code from the authenticator app and the add-in was installed successfully.