Schlage
Schlage lock with Apple Home resident PIN
Locks · Security
Partly worksApple Home issues
1 report: 1 says it partly works.
Reported with 1 integration: keymaster.
What people report
| Integration | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| keymaster | Partly works | Partly in Home Home Key resident PIN appears as HomeKit-xxxx code, managed only from Apple Home | HomeKit-created PINs cannot be tagged; keymaster now skips themSaved copySummary Fixes Schlage refresh spam for HomeKit-created resident PINs by treating untagged `HomeKit-*` code names as unmanageable before keymaster assigns virtual slots or attempts add-then-delete tagging. Schlage exposes only code names and PINs, with no provenance metadata, so name matching is the only available mechanism for this provider. ## Proposed change The Schlage provider now keeps a module-level tuple of compiled unmanageable name patterns, starting with a case-insensitive `HomeKit-*` prefix match. Tagged `[KM: ]` codes always remain keymaster-managed, even if their friendly name … Excerpt saved from GitHub on 2026-10-23. | PR #819 · 2026-10 |
Each row is one report from a GitHub thread, an integration’s docs, or r/homeassistant. Check the date and the linked source before you buy.
In ReReHome
Once Home Assistant’s HomeKit Bridge shares it, this device reaches Apple Home as a HomeKit accessory behind your Home Assistant bridge, so ReReHome shows and controls it like any other.
Identifiers
| Brand | Schlage |
|---|---|
| Category | Locks |