Ditto @dknowles2, thank you! Quick and easy setup for my Schlage Encode Plus.
I (long ago) first set up the lock via Apple Home and the Schlage app, because Apple Home Key is very convenient. This new integration allows me to get the lock’s battery info into HA!
I wanted to share this in case there’s anyone else (who’s an idiot) like me and was having issues updating their changed_by attributes to match the access codes from the Schlage app.
I have an automation that triggers when the door is unlocked and a condition checks to see if it was unlocked by any of the mobile devices or keypad codes. The tricky part is that my keypad codes are constantly changing, and each change requires I update the automation, which can be difficult when I’m on the go.
I spent months trying to come up with a solution that would automatically include new codes. Unfortunately, wildcards (*) cannot be used to call out the state. I pondered if there was a way to set up a binary template sensor to evaluate if the changed_by attribute started with “keypad” or “mobile device”, but sadly my coding skills aren’t that far along yet. I thought to myself, why is this so hard? All I want to do is confirm it wasn’t unlocked by a thumbturn!
confirm it wasn’t unlocked by a thumbturn!
not unlocked by thumbturn
condition: not
conditions:
- condition: state
entity_id: lock.front_door_lock
attribute: changed_by
state: thumbturn
Hey folks! As a heads-up, support for Schlage locks has been merged into Home Assistant core and will be included with the 2023.9.0 release. Consider my custom integration deprecated, and be prepared to remove the custom integration when 2023.9.0 drops.
There are a few changes that had to happen between the custom integration and what’s been merged into core, as the core developers are much pickier about how things are implemented. There’s a chance this will cause issues if you’ve set up automations with your locks, so be prepared to spend a little time fixing that.
Also note that any custom integrations you have installed take precedence over the native version, so if you want to keep up-to-date you’ll need to remove the custom integration once you upgrade to 2023.9.0 and re-run the setup with the native integration, otherwise you’ll be perpetually stuck on the old custom integration.
When HA 2023.9.0 is released I’ll push one final release of the custom integration which will raise an issue in HA to give the same warning. After that, I plan to remove the code from Github in ~October 2023 to signal the final breaking change.
Post-2023.9.0, feel free to open bug reports directly in the Home Assistant core github. They should get routed to me and I’m happy to keep supporting this until I remove the locks from my own house. 
Also feel free to open issues in GitHub - dknowles2/pyschlage: Python 3 library for interacting with Schlage Encode WiFi locks. instead if there’s something that seems fundamentally broken about the interaction with the lock.
Cheers!
Amazing, thanks for your work David!
Congratulations and thanks for all of your hard work on this integration!
Thanks for all the work on this! Curious, is there a place we can find what changes you mention had to be made? I do have automations setup and am in the process of adding more automations based on the “changed_by” attributes
The major potential breaking change is adding compliance with Changes to entity naming | Home Assistant Developer Docs. But I’m also not sure if it affects existing entities you would have from the custom integration or if it only affects newly added entities.
Nice work! Thank you for all your effort on this!
Hey folks, I have been following this thread intently hoping that a solution would pop up for this model (Bluetooth / HomeKit)
I’m not sure how the Schlage Home app does it, but It seems to me that since I can control my lock away from home, that for some reason @dknowles2 excellent pyschlage python script would find it, but alas, when I log in (using pyschlage) it cannot find my lock.
Is this a WiFi locl only solution? Is there any way to have pyschlage ‘see’ my lock?
Thanks
I have the Schlage Sense as well, but I use it with the Schlage BR400 WiFi to Bluetooth adapter. I think adding it to Apple homekit allows outside connection for the Schlage app, but it doesn’t work for Home Assistant. I’m not sure how that works, my house is all Android phones.
Is it normal for the lock to sometimes take minutes to respond to a command?
For reference, I’m now on the new built in integration (deleted the custom component out of the folder and re-setup with the built in version).
Oh, that makes sense.
The integration is meant for Wi-Fi locks and has only been thoroughly tested on Encode locks. I think the v2 Encode locks work as well if you don’t add them to HomeKit.
The bluetooth protocol is very complicated and I haven’t had time to reverse it. There’s a FR tracking it here: FR: Bluetooth support · Issue #28 · dknowles2/pyschlage · GitHub. But it’s very low on my priority list and I probably won’t get it done any time soon.
I’ve heard multiple reports of the BR400 connected locks taking a long time to respond. I’m not sure what the cause is. From what I’ve been able to ascertain from the decompiled Android app, I’m calling the right endpoint. The code is mostly obfuscated though so it’s hard to follow in places. It’s possible there’s some switch to Bluetooth if it detects the lock is nearby. Bad Gateway when Locking/Unlocking with Schlage Integration · Issue #99777 · home-assistant/core · GitHub is tracking the problem with br400 if you want to follow along.
If by V2 you mean the Encode Plus, the one with Apple Home Key support, then yes it works with that.
You can add it to HomeKit as that appears to use the Bluetooth pairing, and then to Home Assistant (through the cloud), which appears to use WiFi. I think the delay is because the lock sleeps WiFi as much as possible. Interacting with the lock through the Apple Home app is significantly more reliable than the Schlage app.
It seems like HA can see the lock through Bluetooth, but the pairing process doesn’t work properly at the moment, potentially because of this:
I suspect even if it’s fixed, if you add the lock to HA, even if you export it back out to HomeKit, the Home Key functionality won’t work anymore.
At this point I’ve only installed one door lock (the Schlage Sense / Homekit) so I think it would be easier to just circle back and go with a different lock that would integrate well w/HA.
Not to derail this thread but are there thoughts about what that might be? I still like Schlage, are there any Schlage locks that integrate well w/HA and don’t rely on the cloud?
I don’t understand, what’s wrong with the Schlage Sense you have now? I’m confused.
It doesn’t integrate w/Home Assistant
If you have a bluetooth adapter, you can pair it via that however, after some quick googling, it looks like when you unpair it from your Schlage on your phone, so that you can pair it with HA, you lose the configured keypad codes, and there doesn’t currently seem to be a way to add them back via Home Assistant.
You might be able to pair the lock to HA via Bluetooth, then export it from HA to Homekit, then in the Apple Home app, add codes back to the lock.
would you all recommend this? I am looking to move to a wifi door lock and I can get the Schlage Ease White Abode WiFi Bridge here in Australia.
thank you
