-
Notifications
You must be signed in to change notification settings - Fork 289
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
aiohttp.client_exceptions.InvalidUrlClientError: /errors/validateCaptcha - solved by alexapy v1.28.2 but needs manual manifest.json edit #2418
Comments
Even if you uninstall the Integration you can't install it. |
Same problem here... I tried uninstalling and reinstalling, and I got this:
|
this isnt to do with the fact the Alexa web page we used to be able to access has gone and it points you to an app install? I have been unable to use the integration for a few updates now. |
and, if you click "install the app" it loads up an Amazon app store which tells you it is no longer supported on Windows 11 and all the apps will no longer be supported, and you dont seem to be able to install anything from it. Sorry if tis isn't relevant. |
same problem here, tried 2 time to remove and reinstall integration but can't install it |
Same issue here on upgrade to 2024.8 |
Same issue. |
Downgraded back to 2024.7.4 and it's working again, so something definitely broke this in 2024.8 |
For anyone having this same issue, you can rollback your HA version by using Advanced SSH Terminal and inputting
Error log on 2024.8.1:
|
I have the same. I set debug on. Was working fine prior to 2024.8. Note that I have cleaned my PIA data from this debug log, username is replaced with <<>> |
Thanks for this. I rolled mine back and can confirm its now working! Definitely keeping this version until I see a fix. |
Same here... |
same here, unfortunately |
same here, 2024.08.0 |
It seems to me, that it may have to do with the unification of Services into Actions that something broke. 2024.7.4 put Services back. |
Thanks man, I downgraded and it worked again as you mentioned |
This comment was marked as outdated.
This comment was marked as outdated.
It looks like this PR added the exception where its raising but the comment in that PR implies it would fail anyways later |
No it looks like it's an alexapy issue as mentioned in other threads see: |
Somehow alexapy is attempting to send a post request to the url "/error/validateCaptcha", clearly a malformed url, which is why the exception is being raised by aiohttp. Could be an uncaught issue on how alexapy finds that URL, could be that amazon updated some page, a combination of these, etc. |
@alandtse I believe everyone who has upgraded to 2024.8 is having this issue. |
Same issue here. Fixed by rolling back to 2024.7.4 |
having the same issue. rolled back but now i can't re-add the integration. 2FA stuff not working... |
Don't install previous version of this integration. Use the newest release. The previous one was giving me that unknown error business too. |
That was the ticket, thanks! |
also having issue with 2024.8 - Following for updates |
Nope, nothing to do with
In all likelihood, it comes down to I will continue investigating but I make no promises of it working again... |
What if you aren't using Docker? I search for Manifest.JSON in StudioCode and find no file with that name. |
Describe your installation. |
Its probably easier to install the File Editor add on: https://github.com/home-assistant/addons/blob/master/configurator/README.md Then open File Editor, and go to /homeassistant/custom_components/alexa_media/manifest.json |
@expozeur Its all lower case - eg manifest.json |
The is the one that did it for me. I'm running HAOS and thought I could just run the patch in the terminal. Turns out that I HAD to run the patch in the homeassistant docker container. Once I ran the patch in the right place and restarted HA, all my Echos showed up again. Thanks community! |
I believe this patch is only needed if your domain is NOT amazon.com |
THANK YOU, THANK YOU, THANK YOU! Fixed for me as well! |
This looks fixed in the newly released 4.12.7 |
Confirming fixed as well |
I got the Integration working. Byt no message to Echos. |
Infact, no integration problem but notify to echo not working
Il Ven 9 Ago 2024, 10:50 Nico Emanuelsson ***@***.***> ha
scritto:
… I got the Integration working. Byt no message to Echos.
—
Reply to this email directly, view it on GitHub
<#2418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5RUO4RY3RJW7ZIP4C6H7DZQR7F7AVCNFSM6AAAAABMFDXK46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGQ3TAMBSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@micium as this seems to impact only some people I wonder if it's related to the service you call I am using notify.alex_media and it works OK.. are you using the old media_player.alexa_tts method? |
My echo's also stopped notifying, but I re-authenticated to Amazon and all is well again. |
I'm using notify.alexa_media, also in the developer tool i got the same problem/msg |
The update worked for me. I completely removed it from HACS, added the latest version, then completed the authorisation setup again, and it all works perfectly now. Thank you for the update! |
This ticket seems to be similar #2053 - an issue with the tokens that needs to be refreshed. |
Refresh token mean remove and re-add the integration? |
I think others have reported success doing that |
I confirm that after new authentication the problem is resolved. Many thanks |
Thank you everyone! |
After a restart Echos work and notify for a couple of hours then it stops working and requires a restart to work again. No error messages or reauthentication requests from the integration. Already tried reauthenticating a cuple times. No changes in behaviour |
Same problem 😞
Il Ven 9 Ago 2024, 22:32 ob1w4nken0b1 ***@***.***> ha scritto:
… After a restart Echos work and notify for a couple of hours then it stops
working and requires a restart to work again. No error messages or
reauthentication requests from the integration
—
Reply to this email directly, view it on GitHub
<#2418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5RUO5AB5SAOMJCYZUAH3LZQURO7AVCNFSM6AAAAABMFDXK46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYG4YTCNRQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Same here. 2024.8.1 not working |
So: What is recommended to do for now? I'm having the same issue and deleting and adding the integration to reconfigure it doesn't work. Also refreshing it doesn't. Only that worked for me was to roll back to last July HA update. Should we stick on this update for now? |
|
And add to this a password reset. |
Seems that it also didn't work:
|
I think I've tried everything... As soon as I restart Home Assistant it seems to work (with some warnings), then after a few minutes everything freezes. Any hope of seeing this integration work? |
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
When updating to HA 2024.8.0 the alexa_media_player integration unfortunately broke for me.
Was working fine on HA 2024.7.x.
I think this has to do with a version bump of aiohttp.
seems to me like the InvalidUrlClientError needs to be catched and a re-auth flow needs to be initialized.
To Reproduce
Expected behavior
Initialize a re-auth flow if needed.
Screenshots
System details
const.py
or HA startup): v4.12.5pip show alexapy
or HA startup):YES 2FA enabled
Logs
Please provide logs.
Additional context
The text was updated successfully, but these errors were encountered: