Skip to content
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

Closed
collateral87 opened this issue Jun 7, 2024 · 40 comments
Closed

GoogleHome cannot load/SSL error #876

collateral87 opened this issue Jun 7, 2024 · 40 comments

Comments

@collateral87
Copy link

I use version v1.11.0 in homeassistant 2024.6.1.

Yesterday the integration worked like expected, today i get this strange error:
Screenshot_20240607_235713_Home Assistant.jpg

I deleted the integration and tried to setup again (with app password), then i get "password or username incorrect".

@corgana
Copy link

corgana commented Jun 7, 2024

Same issue. Tried deleting/re-adding too and got the same error.

@cdn4lf
Copy link

cdn4lf commented Jun 7, 2024

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.

@robertoleonardo
Copy link

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.

@cdn4lf
Copy link

cdn4lf commented Jun 7, 2024

@robertoleonardo, Docker container returned a token without any issues

@pqpxo
Copy link

pqpxo commented Jun 7, 2024

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:
requests.exceptions.SSLError: HTTPSConnectionPool(host='android.clients.google.com', port=443): Max retries exceeded with url: /auth (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')))

@cameronjust
Copy link

cameronjust commented Jun 8, 2024

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.

@sp3cialck
Copy link

Same here, and when i tried to login again after removing the integration, it says, invalid master token!

@Gtwizzy
Copy link

Gtwizzy commented Jun 8, 2024

Same Issue here unfortunately

@Jantjuhhh
Copy link

Same issue here.

@BenAChilds
Copy link

+1 for me

@tvvalbonne
Copy link

+1

2 similar comments
@lobolobo
Copy link

lobolobo commented Jun 8, 2024

+1

@xs2erwin
Copy link

xs2erwin commented Jun 8, 2024

+1

@KapJI
Copy link
Collaborator

KapJI commented Jun 8, 2024

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 context.load_default_certs() (simon-weber/gpsoauth#57).

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.

@kwkid
Copy link

kwkid commented Jun 8, 2024

My issue started after installing 2024.6.1…perhaps just a coincidence

@MalteMatthey
Copy link

Yes, the issue appears to be with version 2024.6.1. After downgrading to version 2024.6.0, the problem no longer persists.

@xs2erwin
Copy link

xs2erwin commented Jun 8, 2024

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.

@psleutel
Copy link

psleutel commented Jun 8, 2024

Yes, the issue appears to be with version 2024.6.1. After downgrading to version 2024.6.0, the problem no longer persists.

@ctsdad
Copy link

ctsdad commented Jun 8, 2024

Hey I am having the same issue . Can anyone advise on how to roll back to the old version?
What are the chances this will be fixed through an update soon?

Thanks in advance for any help given

Sorry I just realized that we are talking about rolling back Home Assistant not the Integration
Also just saw your response. I did it through a backup I'm hoping that worked.

@m3tc0n
Copy link

m3tc0n commented Jun 8, 2024

Hey I am having the same issue . Can anyone advise on how to roll back to the old version?
What are the chances this will be fixed through an update soon?

Thanks in advance for any help given

Ssh into HA and use the following command: ha core update --version 2024.6.0

@ejpenney
Copy link

ejpenney commented Jun 8, 2024

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 context.load_default_certs() (simon-weber/gpsoauth#57).

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.

I added that line to gpsoauth as recommended and it works, issue went away. PR created here

@ctsdad
Copy link

ctsdad commented Jun 8, 2024

Hey I am having the same issue . Can anyone advise on how to roll back to the old version?
What are the chances this will be fixed through an update soon?
Thanks in advance for any help given

Ssh into HA and use the following command: ha core update --version 2024.6.0

Thanks!

@Jantjuhhh
Copy link

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 context.load_default_certs() (simon-weber/gpsoauth#57).
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.

I added that line to gpsoauth as recommended and it works, issue went away. PR created here

in what file do you put this ?

@ejpenney
Copy link

ejpenney commented Jun 8, 2024

It's in the PR I linked. site-packages/gpsoauth/__init__.py

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.

@michaeldjjohnson
Copy link

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

@viertel97
Copy link

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
With this you can get the master token

@ejpenney
Copy link

Gpsoauth 1.1.1 was released, not sure what needs to happen here, will the new release get picked up without changes?

@Omnipius
Copy link

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.

@KapJI
Copy link
Collaborator

KapJI commented Jun 10, 2024

Version 1.11.1 was released. It should include the fix for SSL verification.

@tsew2674
Copy link

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!

@cimco1990
Copy link

Is there a way to update manualy? HA is not offering an update to 1.11.1.

@tsew2674
Copy link

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

@KapJI KapJI closed this as completed Jun 10, 2024
@pista73
Copy link

pista73 commented Jun 10, 2024

C'è un modo per aggiornare manualmente? HA non offre un aggiornamento alla versione 1.11.1.

In HACS, seleziona riscarica e dovresti vedere 1.11.1 come opzione

solved...thanks a lot

@collateral87
Copy link
Author

I installed version 1.11.1 and running HA version 2024.6.1 and still cannot setup the integration. Have i miss something?

@corgana
Copy link

corgana commented Jun 10, 2024

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.

@collateral87
Copy link
Author

That means reauthentication doesnt work at the moment?
What must happen, that i will work again?

@robertoleonardo
Copy link

robertoleonardo commented Jun 10, 2024 via email

@collateral87
Copy link
Author

collateral87 commented Jun 11, 2024

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:
I went into the backup directory --> homeassistant --> data --> .storage --> config_entries. In this file i searched for google_home and then copied out the master token here. With these, I was able to restore the integration in version 2024.6.1 as well.

@michaeldjjohnson
Copy link

I now have this issue. I think I need to delete all elements and start again. Could someone guide me here please.
Error

Thank you

@michaeldjjohnson
Copy link

How do I delete my setup and start all over again please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests