-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Can no longer authenticate in 2024.10.1 #148
Comments
What version of home assistant core are you running? It looks like it maybe didn't download the latest vivintpy library appropriately based on the error and I'm wondering if there might be a conflict. And can you try again, restart home assistant and upload the logs to see if there are any issues prior to that? |
home-assistant_2024-10-11T01-00-51.886Z.log |
This still occurs in HA core-2024.10.2. I found the vivintpy folder where init.py listed version 2024.1.1. I renamed the vivintpy and vivintpy-2024.1.1.dist-info directories, re-updated through HACS, and restarted HA which re-created the vivintpy and dist-info folders, still referencing 2024.1.1 and I still receive I removed the vivintpy folder and downgraded this integration to 2024.10.1b0 and restarted, and saw it create download vivintpy 2024.1.0 and then updated to b1 which downloaded vivintpy 2024.1.1. The issue still continues. |
I've been unable to reproduce this unfortunately. The error seems to indicate that refresh token is being passed in but not expected, so it seems like the custom component code is correct (trying to use a refresh token), but the vivintpy account seems to not be expecting it, which makes me think it's still somehow conflicting with something else. |
Is there anything I can do on my end to help narrow it down further?
…On Mon, Oct 14, 2024, 10:37 PM Nathan Spencer ***@***.***> wrote:
I've been unable to reproduce this unfortunately. The error seems to
indicate that refresh token is being passed in but not expected, so it
seems like the custom component code is correct (trying to use a refresh
token), but the vivintpy account seems to not be expecting it, which makes
me think it's still somehow conflicting with something else.
—
Reply to this email directly, view it on GitHub
<#148 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATWLGUHSK7E2476YO35K7K3Z3SLZLAVCNFSM6AAAAABPX3LZLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJSHA4DAMJQGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Are you able to bash into your docker container and run |
That command returns nothing, which surprises me because I'm currently running 2024.7.0 without any issues. It also returns nothing after redownloading 2024.10.1. I tried
I'm running HA as privileged in podman and mapping the entire /config directory to my local filesystem ( |
I am also getting this after the last update. i have version 2024.10.1 running on a pi 2024-10-16 18:36:36.293 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('vivint', '6b2bf93645ebc1ec51a44dc2daad94ea'): 90605.152042556} EDIT: |
Yours was related to Vivint service interruptions I've been seeing today. |
The problem
After updating from 2024.7.0 to 2024.10.1, I get an error when starting the integration.
I tried removing the integration and re-adding it but still got
TypeError: Account.__init__() got an unexpected keyword argument 'refresh_token'
when trying to log in at the username/password stage. This occurred both with and without MFA enabled for the account it is using. Reverting to 2024.7.0 allows it to log in again with a new emailed verification code.What version of Home Assistant Core are you running?
core-2024.10.1
What was the last working version of Home Assistant Core?
No response
Anything in the logs that might be useful?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: