# Verkada Wireless Lock Command Setup

### Before you begin

Make sure the following devices are installed and powered before starting your Command configuration:

* AL54 installed on a door powered with 8 AA batteries

{% hint style="info" %}
Refer to the [AL54 Installation Guide](https://docs.verkada.com/docs/AL54-CY-Cylindrical-Lock-Install-Guide.pdf) for setup instructions.
{% endhint %}

* AC12 powered through PoE
* WH32 connected to an AC12 via RS485

***

## Configuration

{% stepper %}
{% step %}
[**Add the AC12 to your Command organization and complete the setup.**](/command/organization-settings/add-a-device-to-your-command-organization.md)
{% endstep %}

{% step %}
**Under Device Mode, select Verkada Wireless Lock.**
{% endstep %}

{% step %}
**After setup, click View Device.**

{% hint style="info" %}
If the setup was completed previously, go to the **Devices** page, select the **AC12**, and click the arrow on the right panel to open its configuration page.
{% endhint %}
{% endstep %}
{% endstepper %}

### Connect a hub

{% stepper %}
{% step %}
**From the Wireless lock configuration page, click + Add Hub.**
{% endstep %}

{% step %}
**Select + New Hub.**
{% endstep %}

{% step %}
**Enter the Hub Serial Number and Hub Name, then click Add.**
{% endstep %}
{% endstepper %}

### Connect a lock

{% stepper %}
{% step %}
**From the Wireless lock configuration page, click + Add Lock.**
{% endstep %}

{% step %}
**Select + New Lock.**
{% endstep %}

{% step %}
**Enter the Lock Serial Number and Lock Name, then click Add.**

**Note:** The serial number is located under the lock’s battery cover.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The AL54 should connect to the WH32 within a few seconds.
{% endhint %}

***

## View and modify AL54 settings

{% stepper %}
{% step %}
**In Command, go to All Products > Access.**
{% endstep %}

{% step %}
**Select the door controlled by the AL54.**
{% endstep %}

{% step %}
**At the top right, click Settings.**
{% endstep %}
{% endstepper %}

Doors managed by an AL54 share most [settings](/access-control/configuration/configure-a-door-in-command.md) with other Verkada doors, but there are a few key differences:

* Battery performance depends on configuration and usage. Enabling extra antennas under **Antenna Configuration** increases power consumption and may shorten battery life. For best results, enable only the antennas needed for your setup.
* Battery performance also depends on the polling period between the lock and controller. There is a tradeoff between latency for remote unlocks and lockdowns and battery life.
* The internal button on the AL54’s interior module can be configured under **Internal Button Function**:
  * **No Action** – The button has no effect.
  * **Unlock Mode** – Pressing the button toggles the door between its current schedule and unlocked. Press again to return to the schedule.
  * **Privacy Mode** – Functions as described in [Use the Wireless Lock Internal Push Button](/access-control/installation/wiring-best-practices-for-third-party-wireless-locks/use-the-wireless-lock-internal-push-button.md).

***

## Configure local cache of credentials

The local cache is a backup list of credentials stored locally on the Verkada Wireless Lock. When the lock loses its connection to the vLink Hub, it falls back to this local cache to grant access, so authorized users can still get through critical doors during a network or hardware failure.

Unlike systems that automatically cache recently used credentials, the local cache requires administrators to explicitly select which Access Groups retain offline access. This prevents recently deactivated credentials, such as those belonging to terminated employees, from continuing to work while the lock is disconnected.

{% hint style="info" %}
 Enable Static Cache on critical doors where uninterrupted access is essential.
{% endhint %}

### Individual door

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access > Doors.**
{% endstep %}

{% step %}
**Select the door associated with your Verkada Wireless Lock.**
{% endstep %}

{% step %}
**In the top right, click Settings.**
{% endstep %}

{% step %}
**Under Installer Settings, toggle on Cache.**
{% endstep %}

{% step %}
**Under Cached Groups, select one or more Access Groups whose users should retain access while the lock is offline.**
{% endstep %}

{% step %}
**Click Save.**
{% endstep %}
{% endstepper %}

### In bulk

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access > Doors.**
{% endstep %}

{% step %}
**Select the door associated with your Verkada Wireless Lock.**
{% endstep %}

{% step %}
**In the top right, click Edit Settings.**
{% endstep %}

{% step %}
**Under Installer Settings, toggle on Cache.**
{% endstep %}

{% step %}
**Under Cached Groups, select one or more Access Groups whose users should retain access while the lock is offline.**
{% endstep %}

{% step %}
**Click Submit.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The local cache supports up to 100 credentials. If the total number of credentials across the selected Access Groups exceeds 100, only the first 100 credentials sync to the lock. Verkada Command displays a persistent warning on the door settings page when this limit is reached.
{% endhint %}

{% hint style="danger" %}
While the local cache supports most card formats, it does not support all of them. Please test your specific format to ensure compatibility.
{% endhint %}

***

## Connect Multiple Devices

### WH32

You can connect up to four WH32s to a single AC12.

{% hint style="warning" %}
See Verkada Wireless Lock End-to-End Setup Guide for wiring details.
{% endhint %}

{% stepper %}
{% step %}
**Go to All Products > Access > Devices.**
{% endstep %}

{% step %}
**Double-click on an AC12 or WH32 that is already connected.**
{% endstep %}

{% step %}
**Next to Hubs, click +.**
{% endstep %}

{% step %}
**Under Unassigned Devices, select the WH32 you want to connect.**
{% endstep %}
{% endstepper %}

### AL54

You can connect up to 16 AL54s to a single WH32 or AC12.

{% stepper %}
{% step %}
**Go to All Products > Access > Devices.**
{% endstep %}

{% step %}
**Double-click on an AC12, WH32, or AL54 that is already connected.**
{% endstep %}

{% step %}
**Next to Locks, click +.**

a. Select the hub you want to connect the lock(s) to and click **Next.**\
b. Choose the lock(s) to connect to the selected hub and click **Confirm.**
{% endstep %}
{% endstepper %}

***

## Move devices

AL54s can be moved between WH32s, and WH32s can be moved between AC12s.

{% stepper %}
{% step %}
**Navigate to All Products > Access > Devices.**
{% endstep %}

{% step %}
**Double-click on the device you want to move.**
{% endstep %}

{% step %}
**On the Wireless Lock Configuration page, select the device again.**

a. In the top right click .\
b. Choose **Move Lock** or **Move Hub**.\
c. Select the device you want the WH32 or AL54 to connect to.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/access-control/installation/verkada-wireless-lock-command-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.