Schlage integration requiring reauth every few hours since 2023.12 upgrade

[elarsson1]

The problem

Since updating to HA Core 2023.12, entities exposed by the Schlage integration (two Encode locks) have gone Unavailable and notifications have prompted me to re-authenticate to Schalge (3 times in the past 24 hours since I've updated to 2023.12).

I suspect but cannot confirm that the reauth support added in #103351 is now triggering the reauth flow as a result of transient errors polling the API which were ignored before.

What version of Home Assistant Core has the issue?

core-2023.12.0

What was the last working version of Home Assistant Core?

core-2023.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Schlage

Link to integration documentation on our website

https://www.home-assistant.io/integrations/schlage

Diagnostics information

config_entry-schlage-2a78206c4fb8bf11f008c1bfe97eaf5d.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.schlage
Source: helpers/update_coordinator.py:353
Integration: Schlage (documentation, issues)
First occurred: December 6, 2023 at 8:00:09 PM (3 occurrences)
Last logged: 8:22:50 PM

Authentication failed while fetching schlage (REDACTED_EMAIL) data: Unauthorized

Additional information

No response

[home-assistant]

Hey there @dknowles2, mind taking a look at this issue as it has been labeled with an integration (schlage) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of schlage can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign schlage Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

schlage documentation
schlage source
_{^{(message by IssueLinks)}}

[elarsson1]

Supporting the theory that the re-auth flow is being triggered by some transient API error, reloading the integration without responding to the re-auth prompt also restores the entities.

I should be able to automate a workaround based upon entities going to Unavailable for a certain time period. Unfortunately reloading the integration does not clear the re-auth notification or remove the prompt to reconfigure the integration from Devices and services.

I suspect an HA restart also clears it, which i will try when I'm next prompted to re-auth.

[pm0u]

I am also experiencing this issue, and it does seem to line up with this update for me as well

[dknowles2]

I saw this appear on my instance as well, and I agree with the assessment here.

My guess is that the API is sometimes returning a 401, which we treat as an unauthorized error, per HTTP spec. (https://github.com/dknowles2/pyschlage/blob/main/pyschlage/auth.py#L68-L69) But there's a different class of unauthorized error from the API that is more application-specific (https://github.com/dknowles2/pyschlage/blob/main/pyschlage/auth.py#L42-L45), which makes me think that the 401 error is a transient error coming from a proxy or LB somewhere in the serving stack.

I'll cut a new pyschlage release later tonight to remove the NotAuthorizedError on 401 and have it instead just return the HTTPError from requests. Once that's cut I'll bump it in HA, which should hopefully fix the problem.

[myevit]

Same Issue.

[cnovicktx]

Unfortunate for me, the Schlage re-authentication issue is still occurring.

I have updated to the latest version as shown below:

Core
2023.12.1
Supervisor
2023.11.6
Operating System
11.2
Frontend
20231208.2

[pm0u]

@cnovicktx I don't believe this has been included in a released version yet, just merged into dev.

[dknowles2]

Correct. Also note that restarting HA will resolve the issue without needing to actually reauthenticate.