# AL54 End-to-End Setup Guide

This guide walks you through the complete setup process for Verkada’s AL54 wireless lock system, from pre-installation testing and site planning to hardware installation and Command configuration. Follow these steps to ensure reliable communication between your AC12 access controllers, WH32 wireless hubs, and AL54 locks.

***

## System architecture <a href="#h_f7d55836c3" id="h_f7d55836c3"></a>

To bring an AL54 online in Verkada Command, three Verkada hardware components are required:

* [AC12 Access Controller](https://www.verkada.com/access-control/ac12/): Connects to the WH32 via RS-485 cable.
* [WH32 Wireless Hub](https://www.verkada.com/alarms/wireless-hubs/): Communicates wirelessly with the AL54 using the vLink protocol (915 MHz).
* [AL54 Wireless Lock:](https://www.verkada.com/access-control/locks/#overview) Installed on compatible doors and paired with a WH32.

Each AC12 supports up to 4 WH32 hubs (two per reader port, daisy-chained if needed) and can manage up to 16 AL54 locks. Each WH32 can connect with up to 16 AL54s.

<div align="left" data-with-frame="true"><figure><img src="/files/k1mdc0hsxST7fJt1STW6" alt="" width="563"><figcaption><p>Figure 1: AL54 communication architecture</p></figcaption></figure></div>

***

## Build your own test setup <a href="#h_8ac818b84f" id="h_8ac818b84f"></a>

Before your site visit, create a test setup to confirm connectivity and validate hub and lock placement.

### You will need <a href="#h_7a81f416d1" id="h_7a81f416d1"></a>

1. AC12
2. WH32
3. AL54 (interior and exterior modules)
4. 8 AA batteries
5. GC31
6. Verkada Command organization for testing

### Steps <a href="#h_183b7fbe06" id="h_183b7fbe06"></a>

1. Set up the AC12 and WH32 following the [installation steps](#h_9a69943e54) in this guide.
2. Connect the AC12 to the GC31 using an Ethernet cable for stable internet connectivity.
3. Connect the reader cable from the exterior AL54 module to the interior AL54 module.
4. Insert the eight AA batteries into the interior module to power the lock.
5. Add all devices to your Command organization.
   * For GC31 setup, see [Add Cellular Gateway to Command](https://app.gitbook.com/s/iAGnzScvko5PkG7YBy3i/configuration/add-cellular-gateway-to-command/README).
   * For AL54 details, see the AL54 Install Guide.
   * [Add a Device to Your Command Organization](/command/organization-settings/add-a-device-to-your-command-organization.md)

***

## Pre-site walk planning <a href="#h_2102cf350b" id="h_2102cf350b"></a>

Before beginning your site walk, review the floor plan and mark all doors where you plan to install an AL54. Based on these planned lock locations, determine optimal placement for the WH32 hubs.

Each WH32 has a wireless range of up to 150 feet in a typical building environment. However, this range can vary depending on several factors, including:

* The number and material of walls between the hub and the lock
* The angles of those walls
* The presence of radio interference
* Whether the lock is installed indoors or outdoors

Because of these variables, it’s important to perform testing as outlined in the [Site walk](#h_29d4777d8e) section.

WH32 broadcasts its strongest signal directly in front of the device, while the sides and rear have significantly weaker coverage. For best results, mount the WH32 on a wall facing the wireless locks, and position it so that the exterior side of each AL54 faces the hub to maximize signal strength.

![](https://downloads.intercomcdn.com/i/o/q5re5q6g/1817626500/ace7cfcfd0d615a118b672193a8c/3b7ec320-62d8-47d8-a1c1-90b1a0a62f3c?expires=1765605600\&signature=3105299eeb7ec4260edc0b72574d9a49c920f4fd08f9315a187217adac38b981\&req=dSgmEc98m4RfWfMW3nq%2BgZLWQDS7aA3KDqDIA99HZ8G3jVw5yjxNWI%2FoEaU9%0AopKENp0yEKWGGj2I5qTL0usYdfE%3D%0A)

***

## Site walk <a href="#h_29d4777d8e" id="h_29d4777d8e"></a>

Before starting your site walk, make sure you have:

* The test setup you built earlier (GC31, AC12, WH32, and AL54)
* The floor plan with all device locations marked

### Procedure <a href="#h_e364d4769e" id="h_e364d4769e"></a>

#### Position the first hub <a href="#h_5e5dc95969" id="h_5e5dc95969"></a>

1. Go to the first planned hub location on your floor plan.
2. Place the WH32 from your test setup at that location.
3. Ensure the GC31 is powered on to maintain connectivity while testing.

#### Check the first door location <a href="#h_9af6729c59" id="h_9af6729c59"></a>

1. Proceed to the first door that will connect to the hub.
2. Verify that the door is compatible with the AL54 and confirm the correct SKU.

Refer to the [AL54 SKU Selection & Door Compatibility](https://www.youtube.com/watch?v=I4SitQXmz10) training center video or review the Mechanical Compatibility sections of the [AL54-CY](https://docs.verkada.com/docs/al54-cy-datasheet.pdf) and [AL54-MS](https://docs.verkada.com/docs/al54-ms-datasheet.pdf) datasheets for additional information.

#### Place and test the AL54 <a href="#h_199955fa3e" id="h_199955fa3e"></a>

1. Place the powered AL54 at the door location.
2. In Command, remove and re-add the lock to the WH32 to reset its connectivity status.
3. Wait six minutes for the system to gather enough data and update the connectivity status.

#### Evaluate connectivity <a href="#h_7e287c7c0b" id="h_7e287c7c0b"></a>

1. If the status is Connected or Good, the door placement is acceptable.
2. If the status is Poor or Disconnected, take one of the following actions:
   * Move the WH32 closer to the door
   * Connect the AL54 to a different nearby hub
   * Add another hub to improve signal coverage

#### Retest as needed <a href="#h_5352d5472e" id="h_5352d5472e"></a>

1. After making any changes, retest the door’s connectivity.
2. If you repositioned a hub, retest all other doors previously connected to it to ensure they still show acceptable connectivity.

#### Repeat for all locations <a href="#h_3aa5e67bff" id="h_3aa5e67bff"></a>

Continue this process for all hub and door locations on your floor plan until each door’s SKU has been confirmed and connectivity has been verified for every door location.

***

## Post Site Walk Planning <a href="#h_165494519c" id="h_165494519c"></a>

After finalizing hub locations, plan AC12 placement.

* Each AC12 supports up to 4 WH32s (2 per reader port, daisy-chained if needed).
* RS-485 cabling limits:
  * One WH32 per port: up to 1,500 ft
  * Two WH32s daisy-chained: up to 300 ft between devices
* Use shielded RS-485 compliant cable (18–22 AWG).

***

## Purchase Equipment <a href="#h_e871c30fa2" id="h_e871c30fa2"></a>

1. After confirming device quantities from your site plan, order all required AL54 locks, WH32 hubs, and AC12 access controllers.
2. To ensure flexibility during installation and account for range or signal limitations discovered during testing, we recommend purchasing approximately 1.5 times the planned number of WH32s.
3. Keep any additional WH32s on hand during deployment to adjust hub placement for optimal coverage and signal strength.
4. Once installation is complete and all final hub placements are confirmed, return any unused WH32 units to Verkada for a full refund. Verkada provides an extended return period for the WH32 to accommodate this flexibility.

***

## Installation <a href="#h_0e829410a5" id="h_0e829410a5"></a>

### Command Setup <a href="#h_3b3342d588" id="h_3b3342d588"></a>

To streamline installation, set up all devices in Command ahead of time without physically building or wiring them.

1. Determine the exact AC12, WH32, and AL54 devices to place at each location on the floor plan and label them accordingly.
2. [Commission each device](/command/organization-settings/add-a-device-to-your-command-organization.md) into Command.
3. Complete the software portion of the device setup in Command using the AL54 Command Setup Guide.

### Physical Installation <a href="#h_9a69943e54" id="h_9a69943e54"></a>

1. Mount the AC12 and WH32 units in the locations specified on your floor plan. Note: See the [AC12 Setup Guide](https://docs.verkada.com/docs/access-control-ac12-quick-start-guide.pdf) and [WH32 Setup Guide](https://docs.verkada.com/docs/WH32-wireless-repeater-install-guide.pdf) for more information.
2. Wire the AC12 and WH32s together:
   1. Connect one WH32 per reader port, or daisy-chain two WH32s as needed.
   2. Connect the RS-485 OUT terminal of the first WH32 to the RS-485 IN terminal of the second WH32.
   3. Refer to the[ wiring diagrams](#h_dfff8a14fe) below for wiring configurations.
3. Once the AC12 and WH32s are wired and powered, [install each AL54](https://docs.verkada.com/docs/AL54-CY-Cylindrical-Lock-Install-Guide.pdf) on its designated door.
   1. Verify that each AL54 connects to its assigned WH32 and confirm its connectivity status in Command.
   2. If the connection shows as Poor or Disconnected, adjust the hub or lock placement to improve signal strength, or add an additional WH32 as needed.
   3. Repeat this process for all AC12, WH32, and AL54 devices until every lock shows stable connectivity and functions as expected.

#### Wiring diagrams <a href="#h_dfff8a14fe" id="h_dfff8a14fe"></a>

<div align="left" data-with-frame="true"><figure><img src="/files/6Ro1vY4M7KZ2aII5f48N" alt="" width="563"><figcaption><p>Figure 2: Wire an AC12 to a single WH32</p></figcaption></figure></div>

<div align="left" data-with-frame="true"><figure><img src="/files/py0bAiRXwJZ03LlEbSRU" alt="" width="563"><figcaption><p>Figure 3: Wire an AC12 to four WH32s (two daisy-chained to each AC12 reader port)</p></figcaption></figure></div>


---

# 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/al54-end-to-end-setup-guide.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.