Open nathang21 opened 1 year ago
Hey there @shred86, mind taking a look at this issue as it has been labeled with an integration (abode
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
abode documentation abode source (message by IssueLinks)
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1452670701, 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 Invalid credentials: Multifactor authentication code required for login
error message. I have also had 2FA enabled on the abode account for well over a year, but have only noticed the integration failing to authenticate on full restart over the last couple of months. I'm almost certain the authenticated session used to survive across home-assistant container restarts previously.
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. 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.
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1665973477, 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 : /root/.local/share/Abode/cookies.json
in my HassOS setup. In addition it looks like this location isn't grabbed as part of the built-in back up system, so restoring from backup probably causes this bug as well.
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1666585070, 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.
docker run ... --volume /path/to/hass/root-share:/root/.local/share ...
Is there any update on this? I'm having the issue on every restart too. Also, congrats!
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.
Hmm. I can go to Settings, where I then see "Devices & Services" and a subheading under that says "Integrations, devices, entities and helpers". When I drill into that I see the list of Integrations (the default tab) and Abode is my first one in the list. But neither at that level, nor once I drill into Abode, do I see a Reconfigure button. I see only this: (and "Reload" does nothing of note)
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?
Credentials did not survive 2023.8.3 update
Same here.
I don’t know why, but this is not happening to me on either upgrades or restarts.
On Sun, Aug 20, 2023 at 3:40 PM guitarflipper @.***> wrote:
Same here.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/88334#issuecomment-1685374513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANRHP5X4LB2D53H3A7MP2DXWJR3RANCNFSM6AAAAAAU7RS43A . You are receiving this because you were mentioned.Message ID: @.***>
@guitarflipper @tradel do either of you have two factor authentication turned on for abode
No, I do not have 2FA turned on.
On Sun, Aug 20, 2023 at 4:53 PM grainsoflight @.***> wrote:
@guitarflipper https://github.com/guitarflipper @tradel https://github.com/tradel do either of you have two factor authentication turned on for abode
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/88334#issuecomment-1685394987, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANRHP5OJI2AFWJW4MT7IWTXWJ2LBANCNFSM6AAAAAAU7RS43A . You are receiving this because you were mentioned.Message ID: @.***>
I do, I'm wondering if this only affects users with 2FA or if any non 2FA users experience
It affects me and I use 2FA. Thanks for looking into it.
On Aug 20, 2023 18:25, grainsoflight @.***> wrote:
I do, I'm wondering if this only affects users with 2FA or if any non 2FA users experience
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/88334#issuecomment-1685411869, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB3UDFIC3IZWTGYVOIMCD2LXWKFDTANCNFSM6AAAAAAU7RS43A. You are receiving this because you are subscribed to this thread.Message ID: @.***>
This is happening with me as well. It's not just limited to restarts, which I do rarely. I'm not sure if it's due to updates - but I find I have to login back in every few days. (Actually I just did a HA OS udpate and Abode is still logged in). I use 2FA. This happens to me with Hubitat's Abode integration as well - but much less frequently and not with every update or restart. Perhaps once every few months with hubitat vs every few days with HA.
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 ShelvedCookieJar
(from a lib also developed by the author). I don't actually know anything about the abode api so I'm not sure whether the cookies are necessary in each request, or whether just returning with the _token
and _oauth_token
to the Hass integration and letting it set them at startup (instead of just setting username and password from config like it does now) would work, I'll have to experiement when I have some time.
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 Client
constructor, leaving all the old behavior in place if you don't pass in the tokens.
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701, 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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701, 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 GitHubhttps://github.com/home-assistant/core/issues/88334#issuecomment-1857167222, or unsubscribehttps://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 < https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701>,
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857167222, 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 <
https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701>,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/home-assistant/core/issues/88334#issuecomment-1857167222>,
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857171866, 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 <
https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701>,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/home-assistant/core/issues/88334#issuecomment-1857167222>,
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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857171866, 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 GitHubhttps://github.com/home-assistant/core/issues/88334#issuecomment-1857223809, or unsubscribehttps://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 <
https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701>,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/home-assistant/core/issues/88334#issuecomment-1857167222>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/home-assistant/core/issues/88334#issuecomment-1857171866>,
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< https://github.com/home-assistant/core/issues/88334#issuecomment-1857223809>, 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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857230751, 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 <
https://github.com/home-assistant/core/issues/88334#issuecomment-1857152701>,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/home-assistant/core/issues/88334#issuecomment-1857167222>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/home-assistant/core/issues/88334#issuecomment-1857171866>,
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< https://github.com/home-assistant/core/issues/88334#issuecomment-1857223809>, 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 https://github.com/home-assistant/core/issues/88334#issuecomment-1857230751, 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 GitHubhttps://github.com/home-assistant/core/issues/88334#issuecomment-1857231638, or unsubscribehttps://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 GitHubhttps://github.com/home-assistant/core/issues/88334#issuecomment-1857249778, or unsubscribehttps://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
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