Clear a Matter lock user

Use this action to delete a user and all their credentials from a Matter lock. A common use is to remove access for someone who no longer needs it, for example a former houseguest.

To remove every user at once, use index 65534. This is a special value defined by the Matter specification (hex 0xFFFE) that tells the lock to remove all users.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To clear a lock user from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create automation > Create new automation.
  3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
  4. In the Then do section, select Add action.
  5. Select what you want to control. Under By target (see Targets), select the lock you want to manage.
  6. From the actions shown for that target, select Clear a Matter lock user.
  7. Enter the User index to remove.
  8. Select Save.

Options in the UI

User index

The user slot index (1-based) to clear. Use 65534 to clear all users at once.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as matter.clear_lock_user. A basic example looks like this:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: matter.clear_lock_user
target:
  entity_id: lock.front_door
data:
  user_index: 3

To remove every user at once, use index 65534:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: matter.clear_lock_user
target:
  entity_id: lock.front_door
data:
  user_index: 65534

Options in YAML

user_index integer Required

The user slot index (1-based) to clear. Use 65534 to clear all users at once.

Targets of the action

This action requires a target. The target is the object of the action. You can point the action at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant will run the action on every matching matter entity behind that target.

  • Entity: one specific matter entity, such as matter.living_room.
  • Device: every matter entity that belongs to a device.
  • Area: every matter entity in a room or area.
  • Floor: every matter entity on a floor.
  • Label: every matter entity that shares a label.

You can also select different target types in one action. For example, you can add a specific entity and an area as targets in the same action to run the action on both of them at once.

Good to know

  • Clearing a user also removes all credentials linked to that user, such as their PIN codes and RFID tags.
  • Clearing all users with index 65534 cannot be undone. The lock keeps no record of the users it removed.

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Tip

AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.

Related actions

These actions work well alongside this one: