alexa_media_player: Captcha showing up repeatedly after repeated failure and triggering forgot password
Describe the bug The captcha challenges just keep showing up, asking for email, password, answering captcha and eventually just saying to press the button to attempt login, but they never stop coming however many times I jump through the hoop.
To Reproduce
- Restart hass
- Open the notification
- Do the thing it asks
- GOTO 2
Expected behavior
Working after entering the captcha
Screenshots Log is probably more useful. PMing you this
System details
- Home-assistant (version): .113.3
- Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug). Yes (I haven’t updated in a while)
- alexa_media (version from
const.py
or HA startup):2.10.1 - alexapy (version from
pip show alexapy
or HA startup):1.12.1
Logs I am PMing @alandtse a link with a log on the homeassistant community since I’m not sure how much sensitive info is in there (alexa media player doesn’t look like it does a great job of sanitizing it’s logs).
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 21 (10 by maintainers)
Commits related to this issue
- Merge pull request #875 from alandtse/#870 fix: handle forgot password page — committed to alandtse/alexa_media_player by alandtse 4 years ago
Same thing is happening for me now. Constant capcha notification pops up. I type in the capcha, and it pops right back up. I never even get to the text message portion.
edit. I can log into alexa.amazon.com just fine. I’ve tried restarting HA, did not help.
I’ve also had this happen before and it was maddening… What I found has worked (mostly) for me to enter the captcha is to 1) turn off my PiHole AdBlocker and 2) Use Chrome in an incognito window [on macOS Catalina for me] and not Safari. After the captcha succeeds, I can re-enable my ad blocker and go back to using Safari as I do normally.
Suggestion: It could be helpful to have the integration send a TTS “success” message to all defined Echo’s to confirm that the integration is correctly configured and everything is working end-to-end.