Schlage integration failing after 10.1 update

[thisiscam]

The problem

My schlage lock integration stopped working after upgrading version 2024.10.1 I can still lock/unlock it from the integration, but none of the lock status appears as available.

This causes some of my automation to fail --- this bug poses vulnerability issues if user depends on these features to lock the door automatically.

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

No response

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-01J278FJHGT08VSZKBTD061SGQ.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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)}}

[thisiscam]

Unclear if #127689 fixes this.

[mcanning]

Seeing this as well

[lopanwang]

Same here. Tried reloading it and deleting then re-logging back.

[dknowles2]

https://github.com/home-assistant/core/pull/127689 should fix this. It's included in the 2024.10.2 point release that's currently being pushed: https://github.com/home-assistant/core/releases/tag/2024.10.2

[dknowles2]

@home-assistant close