-
Notifications
You must be signed in to change notification settings - Fork 79
v0.8.1.15 and above - Error: login failed: 2fa: startup failed #1060
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
Comments
Did google block your app password? You can also check in |
I dont see any indications of a blocked app password in the Google acoount, tfa_password looks ok. |
If that doesn't work can you attach some logs. |
Sure thing thanks... These were after the restart when I updated, do you need any other specific logs? Error: login failed: 2fa: startup failed 2025-02-17 08:21:48.878 ERROR (SyncWorker_3) [pyaarlo] imap connection failedb'[ALERT] Application-specific password required: https://support.google.com/accounts/answer/185833 (Failure)' |
Just the same logs but with |
Same Problem .... Logger: custom_components.aarlo unable to connect to Arlo: stopping retries, too may failures |
@Zingaro1 the same Google password message? |
twrecked what do you mean ? |
You said it was the same error but I couldn't tell from your log so I was just verifying it. The first message has a link to Google i was checking you saw the same thing. Did you try any of the solutions mentioned in the other messages? |
@twrecked I'll try again later to create a new google App Password and check if works . |
@twrecked Solved : by create new App Password . |
I enabled debug logging and saw it was complaining about not being able to login but also saw that all my passwords were in plain text in the log, I know I could have removed them before uploading but I decided to try completely remove the integration and install from fresh with the latest version and it now works ok. Didnt have to create a new app password so something must have got corrupt on the upgrade fro 0.8.1.14.1 to 0.8.1.15. |
And nothing between those versions alters the code to do with the password.
Glad it's working now
…On Tue, Feb 18, 2025, 04:13 symonchester ***@***.***> wrote:
I enabled debug logging and saw it was complaining about not being able to
login but also saw that all my passwords were in plain text in the log, I
know I could have removed them before uploading but I decided to try
completely remove the integration and install from fresh with the latest
version and it now works ok. Didnt have to create a new app password so
something must have got corrupt on the upgrade fro 0.8.1.14.1 to 0.8.1.15.
—
Reply to this email directly, view it on GitHub
<#1060 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJU6QYAVGRNH7O3IL4N3T2QL2TTAVCNFSM6AAAAABXIXRBQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRVGAZDKNBSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: symonchester]*symonchester* left a comment
(twrecked/hass-aarlo#1060)
<#1060 (comment)>
I enabled debug logging and saw it was complaining about not being able to
login but also saw that all my passwords were in plain text in the log, I
know I could have removed them before uploading but I decided to try
completely remove the integration and install from fresh with the latest
version and it now works ok. Didnt have to create a new app password so
something must have got corrupt on the upgrade fro 0.8.1.14.1 to 0.8.1.15.
—
Reply to this email directly, view it on GitHub
<#1060 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJU6QYAVGRNH7O3IL4N3T2QL2TTAVCNFSM6AAAAABXIXRBQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRVGAZDKNBSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yeah was a strange one for sure... really appreciate the replies though. |
I'm not sure but some of the home assistant storage files look different to
me but I could be wrong about that.
But that is probably just me misremembering.
…On Tue, Feb 18, 2025, 06:02 symonchester ***@***.***> wrote:
Yeah was a strange one for sure... really appreciate the replies though.
—
Reply to this email directly, view it on GitHub
<#1060 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJU6SKLFXP2KJJEJ5SIND2QMHMDAVCNFSM6AAAAABXIXRBQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRVGMYDGOJUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: symonchester]*symonchester* left a comment
(twrecked/hass-aarlo#1060)
<#1060 (comment)>
Yeah was a strange one for sure... really appreciate the replies though.
—
Reply to this email directly, view it on GitHub
<#1060 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJU6SKLFXP2KJJEJ5SIND2QMHMDAVCNFSM6AAAAABXIXRBQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRVGMYDGOJUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Upgrading to 1.15 or newer I get login failures.
2025-02-17 08:21:48.878 ERROR (SyncWorker_3) [pyaarlo] imap connection failedb'[ALERT] Application-specific password required: https://support.google.com/accounts/answer/185833 (Failure)'
2025-02-17 08:21:48.878 ERROR (SyncWorker_3) [pyaarlo] login failed: 2fa: startup failed
The text was updated successfully, but these errors were encountered: