Verkada supports an intergration with Assa Abloy IN120 & IN220 locks. The following guide will show you how to add these locks in Command.

What you need

Assa Abloy IN120 or IN220 Lock.
Windows Machine (server) running Windows 7 and above with administrative permissions.
Assa Abloy DSR (Door Service Router) software installed on a Windows machine.
Assa Abloy LCT (Lock Configuration Tool) software installed on a portable machine Windows machine, as the locks need to be connected via a cable.

Required. You have to download the LCT & DSR from Assa Abloy's partner portal.

Note: The LCT does not need to run on the same Windows machine as the DSR.

Get started

Install the Lock Configuration Tool (LCT) and the Door Service Router (DSR) according to Assa Abloy's documentation.

Note: If you encounter issues during the installation of these tools, please contact Assa Abloy Support.

Differences between IN120 & IN220

IN120: Is an offline lock powered via Alkaline batteries that communicate with the DSR over WiFi. With the IN120:

Events will sync once a day automatically
Events can be synced manually by pressing the Comm button on the lock.

IN220: Is an online lock powered via PoE (802.3af) that communicates with the DSR over Ethernet. The IN220 supports the following features:

Live events
Remote unlock
Schedule override

Configure the IN120 & IN220 with the LCT

When configuring the IN120 or IN220, the lock must be configured in Persona Mode for full functionality. If it is not configured in Persona Mode, features such as double badging may not behave as intended.

After the profile has been configured on the lock, it should reach out and connect to the DSR. If you are pairing an IN120 and it does not automatically connect, try pressing the Comm button on the lock.

Note: If you are having trouble getting the lock to communicate with the DSR, you may need to create a firewall rule to allow it to do so.

The default port used by the DSR is 2571.

Add a DSR in Command

Note: The DSR Connector must be installed on the same system that the DSR is installed on.

In Verkada Command, go to All Products > Access.
On the left navigation, click Access Settings .
Select a site from the dropdown menu.
Select Door Service Routers.
In the top right, click Add Door Service Router.
1. Give the DSR a unique name.
2. Click Create.
Click Next to continue the configuration.
Download the DSR Connector that matches your environment.
```
The default DSR Connector's file name is 'daemon.exe'.
```
Copy or download the 'config.yaml' file and add it to the same directory as the connector.
Using a PowerShell admin account, run the following commands in the same directory as the DSR Connector:
```
chdir <path to DSR Connector directory> 
.\daemon.exe -s install
.\daemon.exe -s start 
```
Click Done when finished.

If everything has been done correctly, we should see a green checkmark to the right of the newly configured DSR's name that indicates that it has synced with Command. You can check to ensure the Verkada Connector service runs by going to Services on the Windows machine.

Recommended. Verify recovery is enabled on the Verkada Connector service.

Redownload DSR Connector

If you need to re-download the DSR Connector, click ? next to Door Service Routers at the top of the page.

Door management

Claim doors

Any locks added to the DSR but not claimed in Command will show as Unclaimed Doors under the paired DSR.

In Verkada Command, go to All Products > Access.
On the left navigation, click Access Settings .
Select Door Service Routers.
Select a door.
1. Click Claim to add the door.
2. Follow the prompts to complete the door setup.
Click Done to save.

Remove doors

Note: To remove the door, the reader needs to be disconnected from the DSR. Power off the lock or load a profile that prevents communication with the DSR.

In Verkada Command, go to All Products > Access.
On the left navigation, click Access Settings .
Select Door Service Routers.
Select the door you would like to remove from Command.
In the top right, click Unclaim.

Move Sites

Before a door can be added to a new site, it must be removed from its current site.

Required. Ensure the IN120/IN220 can still communicate with the DSR.

Remove the door from its current site.
The door will appear in the Unclaimed Doors section of the DSR.
Follow the steps under Claim doors to move the door.

Door configurations

First Person In (FPI) can only be enabled on an Unlocked schedule. The door will remain locked until a member of the assigned FPI group unlocks it, at which point it will maintain an unlocked schedule.
Double Badge can only be enabled on an Access Controlled schedule.
Exceptions are currently not supported on the IN120 & IN220.
Privacy Mode allows an occupant of a room to lock the door and restrict access to other users except for users in the assigned ac Industrial more questions the default DSR file is named this access group.

Enable Privacy Mode

The IN120 & IN220 lockset is normally secure. The inside lever always allows free egress. To enable privacy mode, engage the deadbolt.

In Verkada Command, go to All Products > Access.
On the left navigation, click Access Settings .
Select a site from the dropdown menu.
Select a door and click Settings > Installer Settings.
Under Privacy Mode, select the access group that will have permission to unlock the door on the Access Group dropdown.

Note: Only one access group can be assigned to the Privacy Mode per door. Straight

Example use case

A user badges into a room and engages the deadbolt. The door is no longer accessible to regular access users, but users in the Privacy Mode access group assigned to this door will still be able to badge into it.

Need more help? Contact Verkada Support.