Schlage Integration returns invalid unique_id error in HA v2024.2.1 on startup

[StephenShamakian]

The problem

HA v2024.2.0 changed something and caused the Schlage integration to stop HA from starting. This fix (#109966) was put in and released for HA v2024.2.1. HA now starts but with this startup error:

2024-02-09 09:38:04.093 ERROR (MainThread) [homeassistant.config_entries] Config entry 'Schlage Locks' from integration schlage has an invalid unique_id '['s****@s******t.com']', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+schlage%22

What version of Home Assistant Core has the issue?

2024.2.1

What was the last working version of Home Assistant Core?

2024.1.6

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Schlage

Link to integration documentation on our website

https://github.com/mcnutter1/homeasssitant-schlage

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-02-09 09:38:04.093 ERROR (MainThread) [homeassistant.config_entries] Config entry 'Schlage Locks' from integration schlage has an invalid unique_id '['s****@s******t.com']', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+schlage%22

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

[StephenShamakian]

More info also reported in this Issue as well: mcnutter1/homeasssitant-schlage#23

[dknowles2]

This is not the official Schlage integration, but an old custom integration. Please remove it from custom_components and use the official integration instead.

[dknowles2]

@home-assistant close

[StephenShamakian]

@dknowles2 I believe there was a reason the custom one was required...

Does the official Integration support the new Encode Plus locks (the ones with homekey)?

[dknowles2]

AFAIK yes. If you find that's not the case, feel free to open an issue in https://github.com/dknowles2/pyschlage and I'll investigate why it's not working.

[StephenShamakian]

I can confirm the Schlage Encode Plus locks work with the official integration! Thank you!