-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Abode integration needs to re-auth after every HA restart #88334
Comments
Hey there @shred86, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) abode documentation |
This only occurs for me when a new version of Abode is installed, but the log entry is the same. The python lib that's used creates a file called abodepy_cache.pickle that contains the credentials and it continues to exist. cc: @tradel Who I think discussed this issue in another ticket I can't find. |
By chance are you talking about #86765, I originally thought that was my issue, but then opened this? Edit: Also I just restarted, and didn't need to re-auth this time, so perhaps it's not every time, but still more frequently than expected. I will update here if I can find any sort of pattern worth mentioning. |
I've noticed it is every time I Home Assistant updates, not every reboot. |
I am also seeing it with every Home Assistant update. |
My apologies for not contributing to the thread earlier. I’m getting
married this weekend so I’ve been a little busy. :)
I will take a look at this next week. I thought the jaraco library didn’t
need the pickle file anymore.
…On Thu, Mar 2, 2023 at 5:49 PM fwedler ***@***.***> wrote:
I am also seeing it with every Home Assistant update.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP4CMTXS5AV5A4CMJHTW2EPWBANCNFSM6AAAAAAU7RS43A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Adding me to the list of those affected. For clarification, in my case, I use 2FA on my goabode account and I use the Yubico Authenticator which requires using a Yubico hardware key. The HA log entry states: "Config entry 'Abode' for abode integration could not authenticate: Invalid credentials: Multifactor authentication code required for login." - It makes sense. Abode does not supply an API key for integration so the HA integration is completely dependent upon your username/password and in my case a 2FA six digit PIN. I'm guessing that if I turned off 2FA (which is a really bad idea) I wouldn't experience this problem. What puzzles me is that I've had 2FA turned on for a long time but, it wasn't until just that last few months that this problem reared it's ugly head. |
@tradel Congrats on the nuptials! If we can drag drag you away from the marital bliss for a few minutes, any chance you have an update on this one? Most appreciated! |
As an additional datapoint, I find I don't need to reauthenticate if I restart home-assistant using the restart button in developer tools, but I do if the home-assistant docker container itself is restarted. The pickle file exists in the configuration directory which is bind-mounted into the container. I see the same |
Is there any update on this? I'm having the issue on every restart too. Also, congrats! |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
This issue has occurred after every update to Home Assitant and still appears after installing the latest update (2023.7.3) but did not occur after a subsequent restart. |
I had to re-auth after the 2023.7.3 update. I rebooted HA and did not have an issue (2023.7.3) |
Contributing my experience, never noticed it on reboot, but needs reauthentication on every update. Minor inconvenience, but would prefer to not have to reauthenticate so often. |
I too have to reauthenticate after each update, but not after reboots. |
Maybe the cookie jar is being stored in a directory that gets wiped out on
each update. I’ll take a look.
…On Fri, Aug 4, 2023 at 1:46 PM Will Adler ***@***.***> wrote:
I too have to reauthenticate after each update, but not after reboots.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP5X75EH6E5Y473OMM3XTUYPNANCNFSM6AAAAAAU7RS43A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@tradel Pretty sure that's what it is. It's being stored in : I had to use the information here to find it, and this addon made it easier. jaraco.abode uses the python lib platformdirs to decide on this location, so I suspect it may store it in different places based on OS / installation method. It probably needs to be stored in a HA configentry instead to make sure it's saved reliably. I haven't been able to figure out how to do this. The jaraco.abode lib changed quite a bit and all the constants the integration relies on were moved, but it was more complex than I could figure out. |
Yes, the author made a ton of changes to the library. Most of my PR against
Hass was just fixing imports.
Thanks for tracking this down and confirming. I’m not sure the config entry
will work because the jaraco library is also designed to be used
standalone. I have to dig into it further. Maybe I can pass configuration
through or add some kind of hook to pull config in.
…On Sat, Aug 5, 2023 at 3:19 PM snapcase ***@***.***> wrote:
@tradel <https://github.com/tradel> Pretty sure that's what it is. It's
being stored in : /root/.local/share/Abode/cookies.json in my HassOS
setup.
I had to use the information here
<https://developers.home-assistant.io/docs/operating-system/debugging/>
to find it, and this addon
<https://community.home-assistant.io/t/add-on-hassos-ssh-port-22222-configurator/264109/272>
made it easier.
jaraco.abode uses the python lib platformdirs to decide on this location,
so I suspect it may store it in different places based on OS / installation
method.
It probably needs to be stored in a HA configentry instead to make sure
it's saved reliably. I haven't been able to figure out how to do this. The
jaraco.abode lib changed quite a bit and all the constants the integration
relies on were moved, but it was more complex than I could figure out
beyond this info.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHPZAF2J5X3FTYK4A2ZLXT2MCLANCNFSM6AAAAAAU7RS43A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for investigating this, I've had the same issue every time my docker container restarts (but not when home-assistant is restarted using the developer tools, where the container itself is not restarted). If anyone else using containers has the same issue, adding a host volume mount to /root/.local/share to persist the token across restarts will workaround it in the interim.
|
Excuse my noobie-ness but how does one go about reauthenticating after a restart? There is no explicit command for that. I've tried to Reload the integration, and tried to Reinstall it. The latter didn't work because I'm allowed only one instance of the integration at a time. |
@danielbcook, If you go to Settings>Integrations, the Abode integration should have a big "reconfigure" button. Click that, and re-enter your username and password. |
Hm, are you actually having the same problem that others are? Are all of your Abode devices and entities available or unavailable? |
They're all unavailable, which just started in the past few days. When I look at the list of entities each of them says "This entity is no longer being provided by the abode integration. If the entity is no longer in use, delete it in settings." My assumption was that a recent restart caused the integration to de-authenticate and made the entities unavailable. But it's certainly possible I have another issue. The last known event from the integration was about 20 hours ago when the alarm was set to Standby. |
I don't know why it's not prompting you to reconfigure! You may indeed have a different issue. |
I installed all the latest updates and then restarted HA. My entities are now re-enabled, but I still don't have an option to configure the integration as I do with many others. So that part remains a mystery but thanks for the support anyhow! |
I just updated to Home Assistant 2023.8.2 and had to reauthenticate the Abode integration. Is anything being done about this? |
I just took a look at the jaraco.abode source. I think it'll need to be refactored to make this work properly. It manages its state in two parts: a _token and _oauth_token that it keeps in memory, and cookies that it persists to disk using a If that would work, it would probably be pretty straightforward to ignore all the cookie stuff and be able to pass in the tokens as part of the |
This is still an issue. Any progress on a fix yet? |
Happening for me as well. Every update. At least now I know why. 👍 |
I have not been able to reproduce this. For those of you replying, can you
please describe how you’re running HA? Is it in Docker, HAOS, etc. Thank
you.
…On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
Happening for me as well. Every update.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
On HA Green device. It also happens to me every restart, every reboot.
________________________________
From: Todd Radel ***@***.***>
Sent: Thursday, December 14, 2023 8:20:01 PM
To: home-assistant/core ***@***.***>
Cc: Mike Nelson ***@***.***>; Comment ***@***.***>
Subject: Re: [home-assistant/core] Abode integration needs to re-auth after every HA restart (Issue #88334)
I have not been able to reproduce this. For those of you replying, can you
please describe how you’re running HA? Is it in Docker, HAOS, etc. Thank
you.
On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
Happening for me as well. Every update.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#88334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABPW7UCTQGDQZSGDZC7QDR3YJOXVDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3DOMRSGI>.
You are receiving this because you commented.Message ID: ***@***.***>
|
The title of this issue is slightly off, it's not on every restart, it's
only when HA Core updates and the auth session expires upon reboot after
the update complete, and I need to reauthenticate. Supervisor updates do
not trigger this, I can't remember about OS updates, I will keep an eye on
the next one.
…On Thu, Dec 14, 2023 at 9:20 PM Todd Radel ***@***.***> wrote:
I have not been able to reproduce this. For those of you replying, can you
please describe how you’re running HA? Is it in Docker, HAOS, etc. Thank
you.
On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
> Happening for me as well. Every update.
>
> —
> Reply to this email directly, view it on GitHub
> <
#88334 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CUJQXQP5RHXEXVGXZIOLYJOXVFAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3DOMRSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
HASS OS in a VM, 2FA turned on in abode
On Thu, Dec 14, 2023, 8:27 PM Nathan Guenther ***@***.***>
wrote:
… The title of this issue is slightly off, it's not on every restart, it's
only when HA Core updates and the auth session expires upon reboot after
the update complete, and I need to reauthenticate. Supervisor updates do
not trigger this, I can't remember about OS updates, I will keep an eye on
the next one.
On Thu, Dec 14, 2023 at 9:20 PM Todd Radel ***@***.***> wrote:
> I have not been able to reproduce this. For those of you replying, can
you
> please describe how you’re running HA? Is it in Docker, HAOS, etc. Thank
> you.
>
> On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
>
> > Happening for me as well. Every update.
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#88334 (comment)>,
>
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
>
> > .
> > You are receiving this because you were mentioned.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#88334 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AB4CUJQXQP5RHXEXVGXZIOLYJOXVFAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3DOMRSGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHANMY6YLILAUDUYYSRG53TYJOYQLAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3TCOBWGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
HA yellow. Standard config. Also on core update. Thanks!
On Dec 14, 2023 22:42, grainsoflight ***@***.***> wrote:
HASS OS in a VM, 2FA turned on in abode
On Thu, Dec 14, 2023, 8:27 PM Nathan Guenther ***@***.***>
wrote:
The title of this issue is slightly off, it's not on every restart, it's
only when HA Core updates and the auth session expires upon reboot after
the update complete, and I need to reauthenticate. Supervisor updates do
not trigger this, I can't remember about OS updates, I will keep an eye on
the next one.
On Thu, Dec 14, 2023 at 9:20 PM Todd Radel ***@***.***> wrote:
> I have not been able to reproduce this. For those of you replying, can
you
> please describe how you’re running HA? Is it in Docker, HAOS, etc. Thank
> you.
>
> On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
>
> > Happening for me as well. Every update.
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#88334 (comment)>,
>
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
>
> > .
> > You are receiving this because you were mentioned.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#88334 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AB4CUJQXQP5RHXEXVGXZIOLYJOXVFAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3DOMRSGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHANMY6YLILAUDUYYSRG53TYJOYQLAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3TCOBWGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#88334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB3UDFNIH36SE673ZEINE7DYJPBJVAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGIZDGOBQHE>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
[image: __tpx__]
Also, can you please indicate if you have turned on 2FA in your Abode
account?
…On Thu, Dec 14, 2023 at 10:52 PM jsmarion ***@***.***> wrote:
HA yellow. Standard config. Also on core update. Thanks!
On Dec 14, 2023 22:42, grainsoflight ***@***.***> wrote:
HASS OS in a VM, 2FA turned on in abode
On Thu, Dec 14, 2023, 8:27 PM Nathan Guenther ***@***.***>
wrote:
> The title of this issue is slightly off, it's not on every restart, it's
> only when HA Core updates and the auth session expires upon reboot after
> the update complete, and I need to reauthenticate. Supervisor updates do
> not trigger this, I can't remember about OS updates, I will keep an eye
on
> the next one.
>
> On Thu, Dec 14, 2023 at 9:20 PM Todd Radel ***@***.***> wrote:
>
> > I have not been able to reproduce this. For those of you replying, can
> you
> > please describe how you’re running HA? Is it in Docker, HAOS, etc.
Thank
> > you.
> >
> > On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
> >
> > > Happening for me as well. Every update.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#88334 (comment)>,
>
> >
> > > or unsubscribe
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
>
> >
> > > .
> > > You are receiving this because you were mentioned.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#88334 (comment)>,
>
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AB4CUJQXQP5RHXEXVGXZIOLYJOXVFAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3DOMRSGI>
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#88334 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AHANMY6YLILAUDUYYSRG53TYJOYQLAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3TCOBWGY>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub<
#88334 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AB3UDFNIH36SE673ZEINE7DYJPBJVAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGIZDGOBQHE>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP6CNBFPWFCUEHT2G5DYJPCPRAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGIZTANZVGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes. I did.
On Dec 14, 2023 22:53, Todd Radel ***@***.***> wrote:
[image: __tpx__]
Also, can you please indicate if you have turned on 2FA in your Abode
account?
On Thu, Dec 14, 2023 at 10:52 PM jsmarion ***@***.***> wrote:
HA yellow. Standard config. Also on core update. Thanks!
On Dec 14, 2023 22:42, grainsoflight ***@***.***> wrote:
HASS OS in a VM, 2FA turned on in abode
On Thu, Dec 14, 2023, 8:27 PM Nathan Guenther ***@***.***>
wrote:
> The title of this issue is slightly off, it's not on every restart, it's
> only when HA Core updates and the auth session expires upon reboot after
> the update complete, and I need to reauthenticate. Supervisor updates do
> not trigger this, I can't remember about OS updates, I will keep an eye
on
> the next one.
>
> On Thu, Dec 14, 2023 at 9:20 PM Todd Radel ***@***.***> wrote:
>
> > I have not been able to reproduce this. For those of you replying, can
> you
> > please describe how you’re running HA? Is it in Docker, HAOS, etc.
Thank
> > you.
> >
> > On Thu, Dec 14, 2023 at 9:00 PM inDgenious ***@***.***> wrote:
> >
> > > Happening for me as well. Every update.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#88334 (comment)>,
>
> >
> > > or unsubscribe
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/AANRHP3FJZUTLHVRET2GTNTYJOVMDAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE2TENZQGE>
>
> >
> > > .
> > > You are receiving this because you were mentioned.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#88334 (comment)>,
>
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AB4CUJQXQP5RHXEXVGXZIOLYJOXVFAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3DOMRSGI>
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#88334 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AHANMY6YLILAUDUYYSRG53TYJOYQLAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGE3TCOBWGY>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub<
#88334 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AB3UDFNIH36SE673ZEINE7DYJPBJVAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGIZDGOBQHE>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP6CNBFPWFCUEHT2G5DYJPCPRAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGIZTANZVGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#88334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB3UDFNFDX33MUJNOJNX6XDYJPCUFAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGIZTCNRTHA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
HAOS on rPi, 2FA on. |
Yes, 2FA enabled with Green.
…________________________________
From: inDgenious ***@***.***>
Sent: Thursday, December 14, 2023 10:16:29 PM
To: home-assistant/core ***@***.***>
Cc: Mike Nelson ***@***.***>; Comment ***@***.***>
Subject: Re: [home-assistant/core] Abode integration needs to re-auth after every HA restart (Issue #88334)
HAOS on rPi, 2FA on.
—
Reply to this email directly, view it on GitHub<#88334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABPW7UCRQDFUXDHTDEIX3STYJPFJ3AVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGI2DSNZXHA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
A year later now, still needs reauth on each update |
Have we kinda decided that the only resolution to this is to turn off 2FA for the home security system? |
Ultimately ended up removing 2FA. Probably an awful idea for a home security system, but having to reauthorize multiple times a month is very annoying |
+1 on this issue - just saw it again after updating HA core to 2024.6.1. 2FA is enabled on my Abode account. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Anti stale
…On Thu, Sep 5, 2024, 9:24 PM issue-triage-workflows[bot] < ***@***.***> wrote:
There hasn't been any activity on this issue recently. Due to the high
number of incoming GitHub notifications, we have to clean some of the old
issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check
if that solves the issue. Let us know if that works for you by adding a
comment 👍
This issue has now been marked as stale and will be closed if no further
activity occurs. Thank you for your contributions.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHANMY6YJ5HWHNRVUVAGSETZVEG6DAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGA3DGNBSGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Please keep it alive. The issue persists. Thanks!
On Sep 5, 2024 22:28, grainsoflight ***@***.***> wrote:
Anti stale
On Thu, Sep 5, 2024, 9:24 PM issue-triage-workflows[bot] < ***@***.***> wrote:
There hasn't been any activity on this issue recently. Due to the high
number of incoming GitHub notifications, we have to clean some of the old
issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check
if that solves the issue. Let us know if that works for you by adding a
comment 👍
This issue has now been marked as stale and will be closed if no further
activity occurs. Thank you for your contributions.
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHANMY6YJ5HWHNRVUVAGSETZVEG6DAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGA3DGNBSGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#88334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB3UDFKKCJXXMONN5KKC7LLZVEHL7AVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGA3DMNJVGY>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Still Broke on 2024.9.0 |
Symptom is still reproducible on 2024.9.1 |
I don’t have time to devote to implementing 2FA right now. If anyone wants
to give it a try and submit a PR, I’d be happy to review it.
…On Sat, Sep 7, 2024 at 6:08 PM Jon Eklund ***@***.***> wrote:
Symptom is still reproducible on 2024.9.1
—
Reply to this email directly, view it on GitHub
<#88334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP3JWQHDHOEIV7F4XRTZVN2OXAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWGQ3DKMRWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I took a shot at fixing this a month or so ago in #123035, and there was some discussion there on how to more cleanly implement what's in that pr (without a symlink) What's in the pr does work for HA being run as a container, and persists through recreating it. I'm not sure if that can be put in |
It works—I just did my first core update without having to re-auth Abode. Been waiting for this one! Big thanks to all the devs here. |
Same here. Thanks everyone!
On Oct 5, 2024 10:31, Will Adler ***@***.***> wrote:
It works—I just did my first core update without having to re-auth Abode. Been waiting for this one! Big thanks to all the devs here.
—
Reply to this email directly, view it on GitHub<#88334 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB3UDFPQLCXY7LU7BLF4UDLZZ7Z5BAVCNFSM6AAAAAAU7RS43CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGA3TOMZYGA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Did not work for me. I'm using a Yubico Key with Yubico Manager. |
The problem
Every time I restart HA for any reason, the Abode integration fails to start up, and shows that it needs to be re-authenticated on the Integration page.
Upon logging in, and entered my 2FA code, everything starts working again, and remains stable (until the next restart).
What version of Home Assistant Core has the issue?
2023.2.5
What was the last working version of Home Assistant Core?
2023.1.7
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Abode
Link to integration documentation on our website
https://www.home-assistant.io/integrations/abode/
Diagnostics information
home-assistant_abode_2023-02-17T14-42-12.427Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: