Issue with initial setup of new Schlage integration when friendlyName isn't set

[jacobshepherd]

The problem

I have a Schlage Encode Wifi lock that I was setting up to use the new Home Assistant integration. My Schlage profile didn't have a name set, which results in the integration throwing an unhandled exception when trying to parse friendlyName field.

All other integrations and the Schlage app seemed to work without having the profile name set, so it seems this may need to be set as an optional field? After setting the name, the integration finished setting up.

What version of Home Assistant Core has the issue?

core-2023.9.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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

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.

_{^{(message by CodeOwnersMention)}}

---

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