Problems during first login

Versions

• ha-google-home: Error occur with v1.0.0 and latest commit on master
• homeassistant/core: 2021.3.3

Configuration

Google Account

Since I have 2FA enabled, I have created an application password.

Home Assistant

This component does not need configuration in yaml format but you can check how to install it or the complete configuration in my repository:

• Dockerfile (installation of component): https://github.com/ManuelLR/MomaHome/blob/e289ff9aa27c3b775fa0353f694de69f1d13403d/home_automation/home_assistant/Dockerfile#L22-L25

• Link to custom_components custom path: https://github.com/ManuelLR/MomaHome/blob/next/home_automation/home_assistant/config/custom_components

All the configuration and plugins work perfectly, only this one fails.

Describe the bug

After installing the plugin, I tried to configure it but, after entering my login details, it fails with the following error:

 Username/Password is incorrect. If your google account has 2FA enabled please generate app password (https://myaccount.google.com/apppasswords) 

and in the home-assistant logs I can see the following:

Logger: glocaltokens.client
Source: /usr/local/lib/python3.8/site-packages/glocaltokens/client.py:169
First occurred: 8:42:50 PM (1 occurrences)
Last logged: 8:42:50 PM

[!] Could not get master token.

Debug log

I tried to debug a bit more and discovered that here the variable res contain the value Error=BadAuthentication.

I can probe further but first I wanted to know if this is a known bug since it seems to be related to https://github.com/simon-weber/gpsoauth/issues/24.

[ManuelLR]

Just for your information, today I updated HA and the ingration to the latest releases (2021.4 and v1.3.0) and magically all works perfectly. I can configure the integration without problems, retrieve data and also delete timers.

Really thanks for your help here!

[ManuelLR]

No, I am having a lot of work and have not been able to dedicate much time to it. Just yesterday I did another test but nothing remarkable, I repeat my last test in the server and works so it seems that it is not a Debian or similar problem. When I have some time I will test with all the active integrations to see if it is something strange with some integration.