Home Assistant Matter lock sensor: the technical guide

Home Assistant users tend to fall into two camps on the lock question. One camp wants full smart-lock actuation — motors, remote unlock, temporary PIN codes for cleaners, all of it — and HA integrations for Yale, Nuki, August, and Schlage cover that well. The other camp wants the monitoring half without the motor: does the door exist in a secure state, yes or no, and notify me if not. This camp has been badly served by the smart-lock market, because every hardware maker is selling the motor.

Matter changed the protocol picture — any Matter lock device now works in HA without a vendor-specific integration — but it didn't change the product picture. Until recently, there were no monitoring-only retrofit Matter devices. The Locksure Matter Lock Sensor launches in May 2026 as the first of that category; this post explains how to integrate it into a Home Assistant setup, with the YAML for the automations HA users typically want.

YAML examples for common automations

Here are four automations that Home Assistant users running our beta sensor have built, shown as YAML you can drop straight into your automations.yaml file or create through the UI. All of these assume the entity names from the commissioning above.

1. Alert if door closed but not locked within 5 minutes

The single most-requested automation from beta users. Catches the “shut the door on the way out but forgot the key” mistake. Uses a delay to avoid firing during the normal “close the door, turn around, lock it” sequence.

- alias: Front door closed but not locked
  trigger:
    - platform: state
      entity_id: binary_sensor.front_door_contact
      to: "off"  # door closed
      for:
        minutes: 5
  condition:
    - condition: state
      entity_id: lock.front_door
      state: unlocked
  action:
    - service: notify.pushover_primary
      data:
        title: "Front door unlocked"
        message: "Closed 5 min ago, still unlocked."

2. Log every lock event to InfluxDB

HA users running InfluxDB for long-term sensor history can pipe lock-state changes straight into their time-series database. Useful for audit trails, noticing patterns (“the house was unlocked for 3 hours yesterday afternoon, why?”), or building Grafana dashboards.

influxdb:
  host: 192.168.1.50
  port: 8086
  database: home_assistant
  include:
    entities:
      - lock.front_door
      - binary_sensor.front_door_contact

3. Bedtime reminder if lock not engaged

Time-triggered check at 11pm. If the lock isn't engaged, send a one-tap notification that links to the HA dashboard so you can check the camera or the room before going to bed. Uses HA's actionable notifications — press “Ignore” to dismiss, press the notification body to open the HA app on the relevant view.

- alias: Bedtime lock check
  trigger:
    - platform: time
      at: "23:00:00"
  condition:
    - condition: state
      entity_id: lock.front_door
      state: unlocked
  action:
    - service: notify.mobile_app_pixel
      data:
        title: "Bedtime check"
        message: "Front door is still unlocked."
        data:
          actions:
            - action: dismiss
              title: "Ignore"

4. Slam detection (noise-complaint alert for teenagers)

Fires when the door state changes more than 4 times within 60 seconds. Useful if you want to know about repeated slamming without actually listening for it. Uses a counter entity to track the event rate.

- alias: Door slam detection
  trigger:
    - platform: state
      entity_id: binary_sensor.front_door_contact
  action:
    - service: counter.increment
      target:
        entity_id: counter.door_events_1min
    - service: counter.reset
      target:
        entity_id: counter.door_events_1min
      delay:
        seconds: 60
    - condition: numeric_state
      entity_id: counter.door_events_1min
      above: 4
    - service: notify.family
      data:
        message: "Door slammed 4+ times in 60s."

All four of these rely specifically on having both the lock. and binary_sensor. entities available from a single device. A contact sensor on its own gives you door events; a smart lock gives you lock events; only a device that exposes both can cleanly express “door closed but still unlocked” or “doors opening late at night while lock was untouched.”

Common questions

Does Home Assistant need to be on the same network as the Thread border router?

Yes, the Thread border router needs to be reachable from your HA host over the local network, because HA's Matter Server communicates with the Matter device through the border router's mesh. In practice this means your HA host and your border router should be on the same VLAN/subnet. If you're segmenting smart-home devices onto their own VLAN (sensible for security), make sure the HA host is able to reach that VLAN for Matter discovery traffic.

Can HA share the lock sensor with Apple Home and Google Home at the same time?

Yes. Matter's multi-admin feature allows a single device to be commissioned to multiple controllers simultaneously. Once commissioned into HA, you can generate a pairing code from the HA Matter integration and use that to also add the device to Apple Home and Google Home. All three platforms then see the device independently. This is useful if you want your HA automations to be authoritative while still having a consumer-app fallback.

Do Matter devices work offline?

Mostly yes. Matter over Thread is fully local — the sensor talks to the Thread border router, which talks to the Matter Server on HA, all over your LAN with no internet involvement. State changes, automations, and local notifications (like HA push notifications to HA mobile apps) continue to work during an internet outage. Only services that require internet — Pushover, SMS via Twilio, remote access via Nabu Casa — break.

What HA version is required for the Matter integration?

Home Assistant 2023.12 or later. Matter support is still being actively developed in HA — newer releases add more device types, improve commissioning reliability, and fix edge cases. We recommend running a reasonably current HA version (2025.x or later) for the best Matter experience. The Matter Server add-on is updated independently of core HA and is on a faster release cadence.