Schlage Encode Smart WiFi Deadbolt via HomeKit Bridge

Hardware
,
1

My Setup

I have a Schlage Encode Smart Wifi Deadbolt (not an Encode Plus), model be489wb2, configured using wifi with Schlage’s app. It is currently working correctly though the app.

I have a locally hosted Home Assistant instance, which currently isn’t aware of the lock.

I have a number of Apple devices (an AppleTV and several HomePods) acting as HomeKit hubs, and a HomeKit Bridge setup in Home Assistant to expose HA entities to HomeKit

My Goal

I’d like to be able to query the status of the lock, and lock/unlock the door, though Home Assistant, locally without using Schlage’s cloud API.

My Plan

Since the device natively supports HomeKit, my thinking had been that I could simply onboard the lock to HomeKit, and then use the HomeAssistant HomeKit Device integration to bring it into HA.

My Problem

None of the guides I’ve found either from Schlage’s FAQ’s or the HA community seem to work. At the step where I’m supposed to go to the “Works With” section of the Schlage app and select HomeKit, the HomeKit option is missing. Instead, I see a “Manage Apple Homes” option in my main menu, indicating that HomeKit has already been set up. Tapping this just lets me see an incomplete and non-interactive list of exposed entities, but the lock itself isn’t included.

This remains the case after factory resetting the lock and re-installing the app.

How do I get the lock into a state where I can attempt to add it as a HomeKit accessory? Alternatively, how else might I go about locally exposing this lock to HA?

2

Are you sure about this? I know the “Encode Plus” and the “Sense” both support HomeKit, but I don’t think the Encode does. To my knowledge the only way to use the WiFi Encode is to use the Schlage integration, which unfortunately relies on the cloud.

See ongoing thread: Schlage Encode Wifi

3

Hmm, that might explain it! The FTUE and docs talk a lot about using HomeKit for Siri integration, but I don’t actually see any explicit evidence that it’s native, vs just piggybacking off of the fact that the app is running on iOS.