# Assa Abloy IN120/IN220 Setup

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

### Differences between IN120 & IN220

**IN120:** The IN120 lock is a daily polling lock that updates its configuration once a day. The lock is powered via Alkaline AA batteries. The lock communicates 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 (with the battery cover off).

**IN220:** The IN220 is a real-time online lock powered via PoE (802.3af) that communicates with the DSR over Ethernet. The IN220 supports the following features:

* Live events
* Remote unlock
* Scheduled override

### 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)](https://go.intelligentopenings.com/dsr8) software installed on a Windows machine.
* Assa Abloy [LCT (Lock Configuration Tool)](https://go.intelligentopenings.com/lct) software installed on a portable machine Windows machine, as the locks need to be connected via a Mini USB to USB-C cable.

{% hint style="warning" %}
The LCT does not need to run on the same Windows machine as the DSR.
{% endhint %}

## Setup

Configure the IN120/IN220 with the LCT and setup the DSR according to the [**Assa Abloy IN120/220 Install Guide**](https://docs.verkada.com/docs/assa-abloy-in120-in220-install-guide.pdf) and other applicable Assa Abloy’s documentation.

{% hint style="warning" %}
Contact Assa Abloy Support if you encounter issues during the installation of these tools.
{% endhint %}

### LCT

Ensure the lock is 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.

### DSR

In the WS Security & Port Configuration section of the DSR Support Tool, **turn off WS Encryption** so that the daemon and DSR can connect.

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 (with the battery cover off).

{% hint style="warning" %}
Prior to claiming the doors, as described later under **Door Management**, the locks will show up on the DSR Support Tool as unconfirmed.
{% endhint %}

***

## Add a DSR in Command

{% hint style="danger" %}
The DSR Connector must be installed on the same system that the DSR is installed on.
{% endhint %}

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Access**.

{% endstep %}

{% step %}

#### On the left navigation, click **Access Settings** .

{% endstep %}

{% step %}

#### Select a site from the dropdown menu.

{% endstep %}

{% step %}

#### Select **Door Service Routers.**

{% endstep %}

{% step %}

#### In the top right, click **Add Door Service Router.**

a. Give the DSR a unique name.\
b. Click **Create.**

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-302ae9d1a7c2e7566d959a718722cb9e792f1af8%2F6591533126189fd2743bde4ef83bfeff31efb842.png?alt=media" alt="" width="300"></div>

​
{% endstep %}

{% step %}

#### Click **Next** to continue the configuration.

{% endstep %}

{% step %}

#### Download the DSR Connector that matches your environment.

```
The default DSR Connector's file name is 'daemon.exe'.
```

{% endstep %}

{% step %}

#### Copy or download the ‘config.yaml’ file and add it to the same directory as the connector.

{% endstep %}

{% step %}

#### 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 
```

{% endstep %}

{% step %}

#### Click **Done** when finished.

{% endstep %}
{% endstepper %}

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.

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-c94462455df78317ecb9b6b193ffcb656e693d49%2F8d966cb393e95d9012e1686e7701b1afaaa19b6c.png?alt=media)

{% hint style="info" %}
Verify recovery is enabled on the Verkada Connector service.
{% endhint %}

### Redownload DSR Connector

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

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-d3922f127a65b2e676ec330fa003fc16fb846bab%2F5aeb47f918b0802c2d3bc76833b799e8dca94c80.png?alt=media)

***

## Door management

### Claim doors

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

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Access**.

{% endstep %}

{% step %}

#### On the left navigation, click **Access Settings** .

{% endstep %}

{% step %}

#### Select **Door Service Routers.**

{% endstep %}

{% step %}

#### Select a door.

a. Click **Claim** to add the door.\
b. Follow the prompts to complete the door setup.
{% endstep %}

{% step %}

#### Click **Done** to save.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-7e9a79c05afcae5224a8fdd19092ab366e4f5b28%2Fea32c2cd04909561f1973285672e05103b96a889.png?alt=media" alt="" width="742"></div>
{% endstep %}
{% endstepper %}

### Remove doors

{% hint style="warning" %}
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.
{% endhint %}

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Access**.

{% endstep %}

{% step %}

#### On the left navigation, click **Access Settings** .

{% endstep %}

{% step %}

#### Select **Door Service Routers.**

{% endstep %}

{% step %}

#### Select the door you would like to remove from Command.

{% endstep %}

{% step %}

#### In the top right, click **Unclaim**.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-d8cc2643f959c95c6e31b35fc2c9a73d0f2edb45%2Fb41dea6db77519efad2c2e56c11c6ac6e80f09e3.png?alt=media" alt="" width="1365"></div>
{% endstep %}
{% endstepper %}

### Move Sites

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

{% hint style="danger" %}
Ensure the IN120/IN220 can still communicate with the DSR.
{% endhint %}

{% stepper %}
{% step %}

#### [Remove the door](#h_fc78762e88) from its current site.

{% endstep %}

{% step %}

#### The door will appear in the **Unclaimed Doors** section of the DSR.

{% endstep %}

{% step %}

#### Follow the steps under [Claim doors](#h_445f62ee01) to move the door.

{% endstep %}
{% endstepper %}

***

## Door configurations

* [**First Person In (FPI)**](https://help.verkada.com/access-control/configuration-and-setup/first-person-in-feature) 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**](https://help.verkada.com/access-control/configuration-and-setup/scheduling/double-badge-to-override-a-doors-schedule) **c**an only be enabled on an **Access Controlled** schedule.
* [**Exceptions**](https://help.verkada.com/access-control/configuration-and-setup/scheduling/door-schedules-and-exceptions) are currently not supported on the IN120 & IN220.
* [**Privacy Mode**](#h_5168cb4a09) allows an occupant of a room to lock the door and restrict access to other users except for users in the assigned 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.

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Access**.

{% endstep %}

{% step %}

#### On the left navigation, click **Access Settings** .

{% endstep %}

{% step %}

#### Select a site from the dropdown menu.

{% endstep %}

{% step %}

#### Select a door and click **Settings** **> Installer Settings**.

{% endstep %}

{% step %}

#### Under **Privacy Mode,** select the access group that will have permission to unlock the door on the **Access Group** dropdown.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-20aa725b4d6e6c7dd311f1a2762a58eab1fef276%2F272a4e42b8165cbf8ec77acf3b03279fcfbb3454.png?alt=media" alt="" width="509"></div>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Only one access group can be assigned to the Privacy Mode per door.
{% endhint %}

**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](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/need-help/contact-verkada-support).
