What Home Assistant can actually do
Checked against Home Assistant 2026.10 documentation and current manufacturer material. Research only: no hardware was commissioned or tested. Features refer to the named connection path, not everything the vendor app can do.
Choice: Freestyle ET-WIFI is the first design-preserving candidate for a Trilock-style entrance. Yale Assure with an ANZ Z-Wave module is the first local-control architecture to investigate if a separate deadbolt is acceptable. Neither recommendation establishes retrofit fit.
C-HA = confirmed in official HA documentation or implementation. C-V = confirmed vendor feature, not automatically exposed to HA. Conditional = exact SKU, firmware, advertised capabilities or commissioning must establish support. Unsupported = explicitly excluded or absent from the stated standard integration path. Unknown = evidence does not establish it. An HA platform capability alone is not exact-lock certification.
Commands, sensing, credentials and outages
Each card keeps the same feature order for comparison. A reported locked state does not prove that the physical door is closed.
Freestyle ET-WIFI
GFSW8951AURBSC / GFSW8951AURMB · Matter
- HA lock / unlock
- Conditional HA; C-V Matter control.
- Reported lock state
- Conditional HA.
- Separate secure / deadlock mode
- Unsupported over Matter.
- Physical door state in HA
- Unsupported vendor Door Sensor Kit over Matter; use a separate sensor.
- Battery alerts in HA
- C-V Matter battery; Conditional HA entity, then alerts possible.
- HA add / remove PIN
- Conditional Matter credential support; untested HA.
- Scheduled guest access
- C-V scheduled access in selected ecosystems; HA Conditional, not inherited from Apple / Google.
- Events and user identity
- Conditional operation source; named user Unsupported in standard Matter lock attribution.
- Auto-lock / timer
- C-V in selected ecosystems; HA timer-setting Unknown.
- Outages and setup
- C-V local Matter after app / firmware setup; Thread border router required. App and Matter modes are separate.
Evidence: Gainsborough ecosystem comparison · HA Matter actions · HA 2026.10.1 Matter lock implementation
Yale Assure ANZ
YRD226HK / YRD256HK + YRD-ZWM-1 ANZ · Z-Wave JS
- HA lock / unlock
- C-HA integration; Conditional secure inclusion and interview.
- Reported lock state
- Conditional device reports, including manual operation.
- Separate secure / deadlock mode
- Unsupported as a separate inside-handle deadlock; ordinary deadbolt locking is different.
- Physical door state in HA
- Unknown on this module. Do not transfer Yale Home DoorSense claims; use a separate sensor.
- Battery alerts in HA
- Conditional battery reports; alerts possible once exposed.
- HA add / remove PIN
- C-HA set / clear code actions; Conditional device slots.
- Scheduled guest access
- HA timed add / remove Conditional; native schedule storage Unknown for the delivered module.
- Events and user identity
- C-HA notification framework; Conditional model emits userId / slot. A slot is not proof of who entered.
- Auto-lock / timer
- Conditional exact model settings; HA timed locking possible with reliable door sensing.
- Outages and setup
- Local HA radio path; no Yale cloud needed for Z-Wave setup / control. Keypad / manual use is separate from HA.
Evidence: HA Z-Wave JS actions and events · Yale Assure AU
Yale Unity
YUR/DEL/1/SIL or MBK · Yale Access BLE
- HA lock / unlock
- C-HA named models.
- Reported lock state
- C-HA, subject to update / latency caveats.
- Separate secure / deadlock mode
- C-HA secure-mode entity and C-V Unity deadlocking; Conditional verified operation.
- Physical door state in HA
- C-HA after DoorSense calibration.
- Battery alerts in HA
- Unknown on BLE path; do not promise a battery entity.
- HA add / remove PIN
- Unsupported in documented BLE integration; optional keypad uses vendor administration.
- Scheduled guest access
- C-V Yale app time-limited access; HA BLE credential scheduling Unsupported.
- Events and user identity
- State changes available; event user identity Unknown. Vendor activity history is separate.
- Auto-lock / timer
- Vendor / app timer details Unknown here; HA timed locking possible.
- Outages and setup
- Local commands with offline key / slot; app / account may provision or refresh keys. Key rotation can require reauthentication.
Evidence: HA Yale Access BLE · Yale Unity AU
Aqara U400 AU
Matter
- HA lock / unlock
- C-V HA compatibility; C-HA generic Matter control.
- Reported lock state
- Conditional delivered firmware.
- Separate secure / deadlock mode
- Unsupported as an inside-handle deadlock; vendor night-latch is a different function.
- Physical door state in HA
- C-V gyro sensing; HA exposure Unknown.
- Battery alerts in HA
- C-V low-battery warning; HA entity Conditional.
- HA add / remove PIN
- Conditional Matter credentials on exact firmware.
- Scheduled guest access
- C-V scheduled passwords; HA timed add / remove Conditional.
- Events and user identity
- Conditional source; named user Unsupported in standard Matter attribution.
- Auto-lock / timer
- C-V gyro auto-lock on close; HA timer-setting Unknown.
- Outages and setup
- Local Matter with Thread border router; vendor settings / firmware and digital keys have separate setup dependencies.
Evidence: Aqara U400 manufacturer · HA Matter actions · HA 2026.10.1 Matter lock implementation
Aqara U200
EL-D02D · Matter
- HA lock / unlock
- C-V third-party Matter control; C-HA generic path.
- Reported lock state
- Conditional delivered firmware.
- Separate secure / deadlock mode
- Unknown separate remote deadlock; depends on underlying mechanics.
- Physical door state in HA
- C-V gyro closure detection; HA exposure Unknown.
- Battery alerts in HA
- Conditional reported Matter battery; keypad battery separately unverified.
- HA add / remove PIN
- Conditional Matter credentials.
- Scheduled guest access
- C-V periodic / one-time codes via Aqara Bluetooth; HA timed add / remove Conditional.
- Events and user identity
- Conditional source; named user Unsupported in standard Matter attribution.
- Auto-lock / timer
- C-V calibrated closure auto-lock; HA timer-setting Unknown.
- Outages and setup
- Local Matter; smartphone setup / calibration. Advanced Aqara settings use app / Bluetooth; remote vendor features may need an Aqara hub.
Evidence: Aqara U200 manufacturer FAQ · HA Matter actions · HA 2026.10.1 Matter lock implementation
Aqara U300
DL-D02D · Matter
- HA lock / unlock
- C-V Matter support; C-HA generic path.
- Reported lock state
- Conditional delivered firmware.
- Separate secure / deadlock mode
- Unknown separate remote deadlock; latch locking is different.
- Physical door state in HA
- Unknown; assume a separate contact sensor is required.
- Battery alerts in HA
- Conditional reported Matter battery.
- HA add / remove PIN
- Conditional Matter credentials.
- Scheduled guest access
- C-V periodic passwords in manufacturer material; exact AU firmware Conditional; HA timed add / remove Conditional.
- Events and user identity
- Conditional source; named user Unsupported in standard Matter attribution.
- Auto-lock / timer
- C-V native auto-lock / passage mode; exact timer / HA setting Unknown.
- Outages and setup
- Local Matter / Thread; vendor advanced-feature setup dependencies must be checked on the AU package.
Evidence: Aqara U300 AU listing · Aqara U300 manufacturer listing · HA Matter actions · HA 2026.10.1 Matter lock implementation
Schlage Encode AU
SRE60121 / SRE60120 · Schlage cloud
- HA lock / unlock
- C-HA; cloud required.
- Reported lock state
- C-HA; approximately 30-second polling.
- Separate secure / deadlock mode
- Unsupported separate inside-handle deadlock; ordinary deadbolt only.
- Physical door state in HA
- Unsupported in documented HA integration; separate sensor required.
- Battery alerts in HA
- C-HA lock-battery sensor; alerts possible.
- HA add / remove PIN
- C-HA add / delete / get codes.
- Scheduled guest access
- HA timed add / delete possible while cloud is reachable; native schedule configuration Unknown in HA.
- Events and user identity
- Full event / user-ID stream Unknown; native PIN-use notifications do not prove HA event support.
- Auto-lock / timer
- C-HA auto-lock-time select.
- Outages and setup
- HA fails without internet / Schlage service. Stored keypad codes and mechanical key are separate local access methods.
Evidence: HA Schlage · HA Schlage add-code action
Important distinctions
- Locked is not closed. Bolt or handle state does not establish that the door leaf is seated. An HA “open” lock action can mean unlatching, not detecting or physically swinging the door open. HA 2026.10.1 Matter lock implementation
- Matter credential support is no longer universally absent in HA. Current HA provides user and credential actions; the selected lock must advertise the capabilities. Native time schedules are not established by those actions. An HA automation that adds or removes a code at a given time depends on HA and communication working then. It is not equivalent to expiry stored and enforced inside the lock. HA Matter actions
- Source is not identity. Current Matter lock attribution maps operationSource into changed_by, such as keypad, manual or remote. It does not map userIndex to a named occupant. A vendor history screen is not evidence of an HA event feed. HA 2026.10.1 Matter lock implementation
- Internet-independent is not power-independent. HA, radios, LAN and Thread border routers still need power. A stored keypad code can work when HA is down; an HA-timed revocation may not happen. Remote phone notifications may require internet.
Practical automation ideas
These are design examples, not instructions to enable or change security settings.
- Notify when an independent door sensor reports that the door has remained open. Separately notify when the door is confirmed closed but the lock remains unlocked.
- Where authorised and commissioned, ordinary locking after a delay can depend on a fresh, reliable closed-door reading. Verify the resulting lock state and alert on failure, a jam or unavailable data instead of repeatedly cycling the motor.
- Notify on an exposed low-battery level and on sensor or lock unavailability. Treat stale readings as unknown, never as evidence that the entrance is secure.
- Keep free interior exit. Do not automate secure or deadlock modes that can trap occupants. Do not auto-unlock on a doorbell, motion, voice recognition or geofence alone.
Before purchase, verify the exact SKU and region, firmware, HA feature list, physical fit and outage behaviour. Keep access codes, key material, credentials, activity histories and house-specific preparation drawings private.