Set up your door in Command
Before you begin, ensure that you’ve followed all the requirements in Get Started with Verkada Intercom.
Add a door to the TD52
Unlock settings
Setting | Description |
Unlock time | Determines how long the door remains unlocked before re-locking. The default is 10 seconds (configurable 1 to 60 seconds). This duration affects both card scan unlocks and keypad pin unlocks. |
NFC Card Unlock | Toggle on if NFC Card Unlock is needed. |
Remote Unlock | Toggle on to allow eligible Verkada Pass app users to unlock this door via the Pass app. |
Daha fazla göster
Bluetooth settings
Setting | Description |
Bluetooth Unlock | Toggle on to allow eligible Verkada Pass app users to unlock this door via Bluetooth. |
Unlock Proximity | Sets the unlock proximity:
• Immediate—Phone needs to touch the reader.
• Near—The phone needs to be around 2–3 ft (.6–0.9mm) from the reader
• Far—The phone needs to be around 7–8 ft (2.1–2.4mm) from the reader.
• Custom—Set your own Received Signal Strength Indicator (RSSI) value.
|
Remote Unlock | Toggle on to allow eligible Verkada Pass app users to unlock this door via the Pass app. |
Bluetooth Cooldown | Set the interval between Bluetooth door unlocks. |
Beep on Bluetooth Unlock | Eligible Verkada reader will beep when unlocked via Bluetooth. |
Daha fazla göster
I/O Settings (DPI)
Setting | Description |
DPI | Toggle on if a DPI button is installed. You can configure using Input 1 of the intercom: On the dropdown, select DPI (Door Position Indicator). |
Ignore DPI relock | The door does not relock when the DPI sends an opened signal. |
Monitor DHO | Triggers an event when a door is held open (DHO). |
DHO Threshold | The time it takes to trigger a DHO event. |
Daha fazla göster
I/O Settings (REX)
Setting | Description |
REX | Toggle on if a REX button is installed. You can configure using Input 2 of the intercom: On the dropdown, select REX (Request to Exit). |
REX Unlocks Door | When the REX is triggered, unlock the door. |
Duration of REX Unlock | How long to keep the door unlocked when REX is unlocked. |
Monitor DFO | Toggle on if the door should alert is forced open (DFO). |
How long to delay DFO events after a valid door open | Set how long the door should be held open before an alert is sent. |
Daha fazla göster
Assign user access to an intercom door
After you add a door to an intercom in Command, you can assign access levels in the access control menu, like any other door.
Intercom Deployment Best Practices Guide
Intercom Deployment Best Practices Guide
Learn how to prepare for an Intercom device installation and troubleshoot issues
Updated over a week ago
When you install your Verkada Intercom for the first time, you might encounter issues with network, hardware, or misconfiguration. Use this guide to prevent installation challenges and troubleshoot them if/when they occur.
Prepare Command for install
A Verkada Command organization is required to manage and troubleshoot Verkada devices.
Required. Verkada Support requires an Admin to generate a support token to troubleshoot Verkada devices. The installer must be an Org Admin, Access Admin, and Access Site Admin on all relevant sites. This allows the installer to confirm all devices are working and provide a support token for troubleshooting. Learn more about Roles and Permissions for Intercom.
Before you begin
Take these steps before each deployment:
Note: Keep note of the device’s serial number and ensure you see that serial number in Command before contacting Verkada Support.
Stage hardware
Staging is the process of verifying that devices function properly before installing them at customer sites. Once the intercom is staged, further troubleshooting can focus on physical and network problems rather than hardware.
Note: When you stage devices, it helps you avoid the costs and difficulties of troubleshooting a faulty intercom after it has been installed.
To stage the hardware:
Finalize the deployment
The most important aspect of an installation is to provide a working solution to your customer so that they can maintain the deployment and get help when you leave. This means demonstrating to them that they have access to all of the devices they purchased and that the devices are fully functional.
Complete the checks below to demonstrate that the installation was successful before you leave the site.
Hardware
Software
Troubleshoot deployment
Regular operation
When the LED on your Verkada intercom is solid blue, and the button LED is the only other illuminated light, this means that the intercom is in a normal operating state.
During regular operation, the intercom uses only 1 color to communicate its status:
When an intercom is unable to reach the required endpoints and services for regular operation, it runs network tests and displays the result using a combination of LEDs.
Note: This feature only works if the intercom has upgraded firmware from the factory version. Staging before install guarantees devices will be on the newest firmware.
Blue+orange LED statuses
Color Combinations | LED Status | Verification Process |
1 Blue
1 Orange |
Intercom is connected with PoE, but is unable to connect to the switch. | Verifies the physical layer status of the intercom’s Ethernet interface. |
1 Blue
2 Orange |
Intercom has not received an IP address. | Verifies if the intercom has received an IP assignment by a Dynamic Host Configuration Protocol (DHCP) server. |
1 Blue
3 Orange |
Intercom is unable to reach the configured gateway. | Sends an Address Resolution Protocol (ARP) request to the gateway. |
1 Blue
4 Orange |
Intercom has detected duplicate IP addresses on the local area network (LAN). | Sends an ARP request for the IP assigned to the intercom. If any other device replies to that ARP request, this status is shown. |
1 Blue
5 Orange |
Intercom is unable to resolve Verkada hostnames. | Looks up a domain name system (DNS) of the relevant intercom endpoints. |
1 Blue
6 Orange |
Intercom is unable to receive a response from the Network Time Protocol (NTP) server. | Attempts to get time synchronized via Network Time Security (NTS) or NTP. |
1 Blue
7 Orange |
Intercom is unable to certify the Secure Sockets Layer (SSL) connection, likely due to SSL inspection. | Validates the certificate presented to the intercom while attempting a Transport Layer Security (TLS) handshake with Verkada endpoints |
1 Blue
8 Orange |
Verkada endpoints are not reachable after booting up.
Note: This LED status is only shown if (at least) 1 endpoint is unreachable. |
Sends Hypertext Transfer Protocol Secure (HTTPS) requests to Verkada endpoints. |
Daha fazla göster
Network diagnostic tests
This simple battery of tests uses your laptop and the IP address used by the intercom to confirm the network is configured to work with Verkada.
If all the above tests succeed and you’re still experiencing problems, see Roles and Permissions for Intercom and verify that every endpoint is allowlisted.
Loss of Network Connection for Intercom
Loss of Network Connection for Intercom
Learn what happens to Verkada Intercom’s functionality during an internet outage
Updated over a week ago
When a Verkada Intercom loses connectivity, here’s what you can expect:
Impact on calling
Verkada Intercoms require an internet connection to place calls with one exception: local Session Initiation Protocol (SIP). If the SIP server is reachable over the local network, then calling functions as usual, even during an internet outage.
Important. Any other receiver type cannot receive calls from, or place calls to an intercom without an internet connection.
Impact on unlocking
If the intercom is operating as a single door controller, or if the unlock output is being used:
If the intercom is paired to a door in Command that is wired to a Verkada access controller: