-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Google Keep sensor not working since 0.118.x #15
Comments
Have it worked before? |
Have it worked before? - yes |
|
You can check out this thread, maybe some solution will work for you (I would start with captcha) |
There is no solution. Disable 2FA verification did not help either. |
This integration uses unofficial API, so maybe Google somehow blocks it in some conditions... It's really hard to say |
A few days ago it worked for me ... |
Has anything in your HA changed in a meantime? |
Update Version 0.118.2 |
How is your HA installed? |
Docker |
Same problem here, working nicely until update HA to 0.118. Since then the sensor keeps saying 'BadAuthentication' when system starts. |
Can you manually change
then restart HA and check if sensor is working? |
Does not work |
Same here, updated gkeepapi to 0.13.1 via manifest and same exception. I will try again the captcha thing and see if it helps. edit: Nah, same exception. |
I'm afraid I can't do anything more for now |
The same for me! No fix yet? Home Assistant 0.118.2 |
Same problem. Home Assistant 0.118.2 |
Same in 0.118.3 |
Same problem |
Same in 0.118.4 |
same in 0.118.5 |
it works, |
Installed the 3 python modules mentioned above in the homeassistant venv, still getting the error: gkeepapi.exception.LoginException: ('BadAuthentication', None) HA 0.118.4 |
Same for me |
Same ;/ 2020.12.0 |
same in 2020.12.1 but i fix it with pyatmo one more time pip install -U --force-reinstall pyatmo |
how do you run the pip command on an rpi4 running HA? i have the terminal open but wont let me.... update: figured out i was using the wrong terminal. ran the command, reboot and..... still an error |
anyone found a solution for this ? I can't get it working |
I just installed the add-on via HACS. I entered the info in my config.yaml file, and I'm getting the exact same error as the first post. I'm on Home Assistant 2021.1.0 (on a Raspberry Pi). I have NO IDEA how to even run the pip commands on the Raspberry Pi; based on some research I understand it is not possible.
@Scags104 what do you mean "the wrong terminal?" How did you run the command? Thanks all. |
There is another add-on with a similar name that allows it
…On Fri, Jan 8, 2021, 7:26 PM krelltunez ***@***.***> wrote:
I just installed the add-on via HACS. I entered the info in my config.yaml
file, and I'm getting the exact same error as the first post. I'm on Home
Assistant 2021.1.0 (on a Raspberry Pi).
I have NO IDEA how to even run the pip commands on the Raspberry Pi; based
on some research I understand it is not possible.
update: figured out i was using the wrong terminal. ran the command,
reboot and..... still an error
@Scags104 <https://github.com/Scags104> what do you mean "the wrong
terminal?" How did you run the command?
Thanks all.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJCYYDQO7M5GX3LP22LCC3SY6PD7ANCNFSM4T4VYILQ>
.
|
I have tried all the steps above and still have this problem, please update us when the API is working |
2021.2.2 - working again! But I changed the password on my google account |
I just installed this integration and front end card via HACS in HA 2022.3.6. Initially I used the same app pw I had created for HA to send email notifications via my GMail account. I wasn't seeing any errors, but the state of the sensor entity was 0 and it didn't show any of my Keep Notes. I created a new Google app password and set the sensor to use it. It now shows all of my notes under the sensor attributes and the state is > 0. |
Google Keep sensor not working
The text was updated successfully, but these errors were encountered: