Unknown Error Occurred

[ethanblom]

I’ve installed the integration, but when I go to submit the configuration info, I get a “Unknown Error Occurred” message.

[fcastilloec]

Hi there, I wasn't expecting anybody to use this integration besides myself. I'm a noob when writing Home Assistant integrations, I know some basic Python but usually for scripting, so this whole repository is probably not top-notch.
I can help figure out what's happening, but not sure how much help I can be.

When do you see that error? Have you been able to go throw the config flow? Please enable logging, I did add some error messages to the code, so logging is the best way to go.

[ethanblom]

Hello! I was very excited to stumble across this integration - the only others I could find have been archived and I couldn't seem to make them work. I use Google Keep quite a bit, and this would be a great addition to my Home Assistant. Here's what I'm running into: I enter my info into the configuration wizard screen, hit Submit, and that's where the error shows (see picture below).  I checked the logs, and here is what I found: 2023-09-24 13:29:53.050 ERROR (MainThread) [custom_components._gkeep_list_sync.config_flow] Login error: ('BadAuthentication', None) I'm a noob when it comes to Home Assistant, so you'll have to excuse my inexperience. Let me know if you need more info from me or what I can do to help. I really appreciate your assistance on this! Thanks, Ethan

…

________________________________ From: Felipe Castillo ***@***.***> Sent: Sunday, September 24, 2023 12:33 PM To: fcastilloec/gkeep-list-sync ***@***.***> Cc: ethanblom ***@***.***>; Author ***@***.***> Subject: Re: [fcastilloec/gkeep-list-sync] Unknown Error Occurred (Issue #2) Hi there, I wasn't expecting anybody to use this integration besides myself. I'm a noob when writing Home Assistant integrations, I know some basic Python but usually for scripting, so this whole repository is probably not top-notch. I can help figure out what's happening, but not sure how much help I can be. When do you see that error? Have you been able to go throw the config flow? Please enable logging, I did add some error messages to the code, so logging is the best way to go. — Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATH3N2XWOUQKIT3VHYODTV3X4BVIJANCNFSM6AAAAAA5ESWAVE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[fcastilloec]

The error "BadAuthentication" happens because your username or password is wrong. It can also happen because you're using two-factor authentication and this integration doesn't support it.
I suggest you create an app password for this integration and try again. It might fix your issue.
Here's a guide on how to create an app password if you're not familiar with it: Sign in with app passwords

FYI, I think you removed the link to the image you uploaded, so it can't be seen. Try editing your message and re-adding it, and keep the link that GitHub generates when you add the image.

[ethanblom]

I tried signing in with the app password prior to this as well, but I tried it again to be sure, and I'm still getting the same "unknown error" message and same log error.

[fcastilloec]

I really don't know what's going on. From the error message, I think this is coming from the gkeepapi module that we use to contact Google Keep.
Maybe it has something to do with kiwiz/gkeepapi#144
If the problem is with app passwords, if you want to test, you can disable two-factor authentication temporarily and sign in using your actual password. This integration doesn't store your password in any way, once you're logged in, we retrieve a token and use that to login in future attempts. Of course, remember to re-enable two-factor afterward.
I'm going to start the developing environment again and see what's happening, it'll take some time. I haven't done the configuration flow in a really long time, because once you have that token, everything works seamlessly.

I could also create a small Python script that uses gkeepapi and will ask for your username and password and check if everything is working correctly. That way, you don't have to temporarily disable two-factor authentication. I'm a little busy at the moment, so it'll take a while before I get back to you.

[fcastilloec]

I also found this issue kiwiz/gkeepapi#81 that looks similar to what you're seeing. I know Home Assistant recently upgraded their Python version and it might be the reason why this is not working. Maybe, I could modify the code to accept a token instead of a password, and the problem should be fixed. This will make it so that you will have to run a separate script to generate this token, which requires the user to have Python installed. I also see that a Docker container can be used, which is probably the best way to make sure dependencies are met and nothing weird happens, and of course means that the user has to have Docker installed.
I can also look into Docker and the script (probably a script that uses Docker is the best way), but it'll take a long time before something functionally gets into this repo.

You could install an old version of Home Assistant, probably 2022.09 or maximum 2022.11, run the config (which should work), and then update Home Assistant.

[ethanblom]

Thank you for the suggestions. I tried disabling two-factor authentication as well as installing a few different old versions of Home Assistant and I'm still getting the same error message.

[mistikdonbass]

I also get an authorization error.

fcastilloec , your integration will be very useful!!!

[fcastilloec]

Because this issue depends on the kiwiz/gkeepapi#144 to be fixed, I can only do a partial workaround.
My thoughts right now are to change the login process to accept an access token in addition to a password (either of them, not both). That way we bypass the login error. Each user will have to find a way to get their access token. I'll probably provide instructions on how to do it, using https://github.com/rcdeoliveira/gkeepapi-docker seems to work according to people on the original gkeepapi issue. Nonetheless, retrieving the access token will be outside of the scope of this integration because of the gkeepapi issue.

[fcastilloec]

@mistikdonbass @ethanblom can you guys test the new commits?
After some searching, I've found other projects affected by the same bug and they've solved it by pinning old versions of some dependencies. I tested the new dependencies on the dev branch of Home Assistant core and it's working without an issue and there's no need to retrieve a master token by users.

[mistikdonbass]

Does gkeepapi have to be installed? Now I don’t have it installed, there is an authorization error.

[fcastilloec]

@mistikdonbass gkeepapi is installed automatically under Home Assistant, it's a dependency of this integration and you don't have to worry about it.
You don't have to do anything different, just follow the instructions on how to install this integration (see README.md).
If you already had it installed, you should eventually get the update automatically, or you can force an update (check documentation on how to do that online).

[ethanblom]

I've updated the integration and tried using an app password, as well as turning off 2-step verification, but with both ways I continue to get a Bad Authentication error.

[fcastilloec]

I'm sorry but I can't replicate this anymore. Having a fresh installation of Home Assistant, with only this integration enabled, and everything works as it should. Here's a video of the integration running on said fresh installation of Home Assistant.

Segmented_video.mp4