Set credential

Use this action to add or update a credential, such as a PIN code or password, for an existing user on a Z-Wave lock. The user must already exist, so call the Set user action first if you need to create one.

If you omit the credential slot, the integration assigns the first available slot for the credential type. The action returns the assigned credential slot and user index in a response variable.

Note

Only pin_code and password credentials can be added or modified through this action. Other credential types, such as RFID, NFC, or biometric, may appear in the response of the Get users and Get credential capabilities actions, but must be enrolled directly on the device.

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 set a credential 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 set the credential on.
  6. From the actions shown for that target, select Set credential.
  7. Set the User index, Credential type, and Credential data.
  8. In the Response variable field, enter a name to store the result, for example, result.
  9. Select Save.

Options in the UI

User index (Required)

The user slot index that owns the credential. Must refer to an existing user.

Credential type (Required)

The type of credential, either pin_code or password.

Credential data (Required)

The credential data, such as the PIN digits or password string.

Credential slot (Optional)

The credential slot index. When not set, the first available slot for the credential type is used.

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.set_credential. Store the result in a response variable so you can use the assigned slot in later steps:

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: zwave_js.set_credential
target:
  entity_id: lock.front_door
data:
  user_id: 1
  credential_type: pin_code
  credential_data: "1234"
response_variable: result

Options in YAML

user_id integer Required

The user slot index that owns the credential. Must refer to an existing user.

credential_type string Required

The type of credential, either pin_code or password.

credential_data string Required

The credential data, such as the PIN digits or password string. Always quote the value in YAML, for example “0123”, to preserve leading zeros and prevent it from being read as a number. For a PIN code, use digits only.

credential_slot integer

The credential slot index. When not set, the first available slot for the credential type is used.

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 lock entity. Each entry includes the assigned credential slot and user index:

lock.front_door:
  credential_slot: 1
  user_id: 1

Good to know

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.

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:

  • Set user: Creates or updates an access-control user on a Z-Wave lock.

  • Delete credential: Removes a single credential from a user on a Z-Wave lock.