Get lock user code

Use this action to read the user codes from a Z-Wave lock. You can query a single code slot or retrieve all code slots at once, for example to check which slots are in use before assigning a new code.

This action returns its result in a response variable, which you can use in later steps of the same automation or script.

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 get lock user codes 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 locks to read.
6. From the actions shown for that target, select Get lock user code.
7. Optionally set a Code slot to read a single slot.
8. In the Response variable field, enter a name to store the result, for example, codes.
9. Select Save.

Options in the UI

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 zwave_js.get_lock_usercode. Store the result in a response variable so you can use it in later steps:

action: zwave_js.get_lock_usercode
target:
  entity_id: lock.front_door
response_variable: codes

Options in YAML

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 lock entity behind that target.

• Entity: one specific lock entity, such as lock.living_room.
• Device: every lock entity that belongs to a device.
• Area: every lock entity in a room or area.
• Floor: every lock entity on a floor.
• Label: every lock 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.

Response data

The response is keyed by code slot. Each slot includes the following fields:

• usercode: The user code stored in the slot. Empty when the slot is not in use.
• in_use: Whether the slot currently holds a code.

A shortened example of the response looks like this:

"1":
  usercode: "1234"
  in_use: true
"2":
  usercode: ""
  in_use: false

Good to know

• Query a single slot with a code slot, or leave it out to read every slot at once.

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn 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] without writing a line of YAML.

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.

Related actions

These actions work well alongside this one:

• Set lock user code: Sets a user code in a code slot on a Z-Wave lock.

• Clear lock user code: Clears the user code from a code slot on a Z-Wave lock.