-
Notifications
You must be signed in to change notification settings - Fork 74
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
GoogleHome cannot load/SSL error #876
Comments
Same issue. Tried deleting/re-adding too and got the same error. |
I thought I was going crazy. Same issue here. Enabled debugging, but I still only get the error above. Tried rolling my password and token, no change. |
same issue - and i thought maybe i needed a new master token and tried to run that python script to get one, and it seems to be giving the same issue. so i think it's probably google server side. |
@robertoleonardo, Docker container returned a token without any issues |
Same issue. I'm getting SSL errors for what looks like the domain 'android.clients.google.com' I've spent a few hours trying work arounds and different methods with no luck. Error in logs: |
Seeing the same error here. SSL certificate should be valid as I'm using NginxProxyManager for exposing Home Assistant to the internet. Home Assistant can still trigger Google Home devices to play sounds/voice prompts when automations trigger though. |
Same here, and when i tried to login again after removing the integration, it says, invalid master token! |
Same Issue here unfortunately |
Same issue here. |
+1 for me |
+1 |
2 similar comments
+1 |
+1 |
I'm unable to repro this issue on any of my setups (local macos, linux debian, haos on x86 or arm64). But it's likely this can be fixed by adding If you can repro this issue, please submit a PR to gpsoauth. And stop posting "+1" if you can't to provide any useful context. You can hit "subscribe" button to get the updates about this issue. |
My issue started after installing 2024.6.1…perhaps just a coincidence |
Yes, the issue appears to be with version 2024.6.1. After downgrading to version 2024.6.0, the problem no longer persists. |
Same here. Got back to 2024.6.0 and lost the problem. |
Yes, the issue appears to be with version 2024.6.1. After downgrading to version 2024.6.0, the problem no longer persists. |
Hey I am having the same issue . Can anyone advise on how to roll back to the old version? Thanks in advance for any help given Sorry I just realized that we are talking about rolling back Home Assistant not the Integration |
Ssh into HA and use the following command: ha core update --version 2024.6.0 |
I added that line to gpsoauth as recommended and it works, issue went away. PR created here |
Thanks! |
in what file do you put this ? |
It's in the PR I linked. I'm being intentionally vague, because if that doesn't make sense to you I would recommend you revert and wait for the updates. Modifying Python libs in site-packages requires a small amount of expertise, and the method will vary a lot depending on your setup. |
I would be grateful to hear of how this can be resolved. I am also unable to obtain a master token. How did everyone here get theirs? Thank you kindly |
https://github.com/simon-weber/gpsoauth#alternative-flow |
Gpsoauth 1.1.1 was released, not sure what needs to happen here, will the new release get picked up without changes? |
Hard to say. Even with forcing gpsoauth==1.1.1 to be installed on integration setup, I had to use the alternate flow above to get a viable master token. No other approach was effective. |
Version 1.11.1 was released. It should include the fix for SSL verification. |
For what it's worth, everything started working for me again after installing 1.11.1. I didn't have to mess with my master token at all, however, I never tried to re-authenticate when the SSL error was present, so that that may be part of it. Thanks all for such a quick resolution! |
Is there a way to update manualy? HA is not offering an update to 1.11.1. |
In HACS, select redownload and you should see 1.11.1 as an option |
solved...thanks a lot |
I installed version 1.11.1 and running HA version 2024.6.1 and still cannot setup the integration. Have i miss something? |
I was still unable to log in (generic invalid username/password error) but restored a backup where I was logged in, updated the integration, then updated HA and it appears to be working. |
That means reauthentication doesnt work at the moment? |
i think it might help if you update the integration before upgrading to ha os 2024.6.1 -- i had downgrowneded to 2024.6 when the issue started a few days ago, and only updated to .1 after i saw the google home update in hacs and it seems to be working fine.
…--
rob lee
m: 310.431.1619
________________________________
From: collateral87 ***@***.***>
Sent: Monday, June 10, 2024 6:22:10 AM
To: leikoilja/ha-google-home ***@***.***>
Cc: robertoleonardo ***@***.***>; Mention ***@***.***>
Subject: Re: [leikoilja/ha-google-home] GoogleHome cannot load/SSL error (Issue #876)
That means reauthentication doesnt work at the moment?
What must happen, that i will work again?
—
Reply to this email directly, view it on GitHub<#876 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADELGEYQES6UC3ON552JRLDZGWSAFAVCNFSM6AAAAABI7NGBX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJYGM3DSNBRGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I didn't want to restore a backup that was so long ago. I have found another way, which I would like to show here for other people who also don't want to restore a backup but have one: |
How do I delete my setup and start all over again please? |
I use version v1.11.0 in homeassistant 2024.6.1.
Yesterday the integration worked like expected, today i get this strange error:
I deleted the integration and tried to setup again (with app password), then i get "password or username incorrect".
The text was updated successfully, but these errors were encountered: