Contact Support

Cross-Device Local Connections for Access Control

How access controllers communicate directly with other Verkada devices over the LAN

Verkada access controllers can use local connections to communicate directly with other Verkada devices over their shared local area network (LAN). Local connections allow cross-device features to continue to operate even if they lose their connection to the Verkada cloud.

When a Verkada access controller is offline, local connections only apply to the operation of the access controller’s cross-device configurations. See Verkada Access Offline Operation for information on access controller offline behavior without local connections.

How cross-device local connections work

Verkada access controllers automatically establish local connections with relevant devices when you configure cross-device features that support local connections.

The devices an access controller establishes a local connection with depends on the type of cross-device feature.

  • For LPR Unlock, the access controller establishes a local connection with an LPR camera.

  • For AUX inputs/outputs (I/O), the access controller establishes a local connection with other Verkada access controllers.

Devices communicate via local connections by default (when available) because local connections are generally faster than cloud connections.

If one or both of the devices with a local connection lose their cloud connection, any relevant device connections continue to operate as long as they both still have a local connection.

Supported cross-device features

License Plate Recognition (LPR) unlock

LPR unlock allows a Verkada access controller to grant access to an entrance based on license plates recognized by a Verkada LPR camera.

An access controller establishes a local connection with an LPR camera over their shared LAN to exchange information about detected license plates for granting or rejecting access to an entrance.

See Configure License Plate Recognition for more information.

AUX inputs

AUX inputs can be used to trigger the following actions when a device wired into the AUX input is triggered (such as a third-party intercom or button):

AUX inputs can trigger these actions for doors on different access controllers than the one where the AUX input is physically located by establishing a local connection between the two controllers. For example, you can use AUX inputs on a Verkada AX11 I/O controller to trigger a lockdown on doors wired to a Verkada AC42 or AC62.

See Unlock a Door from a 3rd-Party Intercom System or Button and Emergency Lockdowns for more information.

AUX outputs

AUX outputs can activate or deactivate based on various access events.

AUX outputs can respond to events originating from access controllers (other than the one where the AUX output is physically located) by establishing a local connection between the two controllers. For example, you can use a door forced open (DFO) event on one access controller to activate an AUX output on another access controller.

See Configure an AUX Output on an Access Controller for more information.

Check local connection status

LPR unlock

Navigate to the door configured for LPR unlock.

  • If the door’s access controller has a local connection with the LPR camera, it should function as expected.

  • If the door’s access controller loses its local connection to the LPR camera, the message LPR Camera Connection Degraded will display at the top of the camera feed.

AUX inputs and outputs

1

A Device Connections icon indicates a local connection is established between two or more access controllers. You can find the icon in the following places:

  • On the AUX I/O page.

  • On the Access > Doors page where the AUX output is listed.

  • On the Access Controller page, where the AUX output is listed.

2

Click to display the cross-device connections.

3

Under Connection Status, you can see the current cross-device connection status. See the connection status table for more detailed descriptions.

4

Under Connections, you can see the connection status for each device connected to the AUX I/O. There are 2 connection statuses:

  • Cloud : connection between the AUX I/O’s access controller and the other access controller through the Verkada cloud.

  • Local : connection between the AUX i I/O’s access controller and the other access controller through their shared LAN.

Connection status

Status

Description

Devices Fully Connected

Cloud and local connections are available between the AUX I/O’s access controller and all other relevant access controllers.

Device Connection Issues

Some relevant access controllers are disconnected from the AUX I/O either over the cloud or the LAN.

Some Devices Fully Disconnected

Some relevant access controllers are disconnected from the AUX I/O’S access controller over both the cloud and the LAN. The AUX I/O is not working correctly and the issues with the cloud or local connection must be resolved.

AUX inputs and outputs with cross-device configurations continue to operate without a local connection by using a cloud connection as a fallback (if one is available).

Troubleshoot local connection issues

What ports are used for cross-device local connections?

Verkada devices use the following ports for cross-device local connections:

  • 50000-60000: WebRTC connections chose a port from this range for new connections.

  • 5353: Default port for multicast DNS (mDNS).

  • 4929: Devices’ locally advertised HTTPS server.

What if 2 devices cannot establish or lose a local connection?

Confirm that both Verkada devices are powered on and connected to the same LAN.Check that the LAN is not configured in a way that blocks communication between devices through the ports used for local connections (see specific ports above).

What if 2 devices with a local connection lose their cloud connection?

As long as there is still a local connection, devices with cross-device configurations continue to operate without a cloud connection.

If the local connection is lost:

Confirm that devices can connect to the internet.Check the network settings and confirm they have not been changed to prevent cloud communication. See Access Control Network Settings for more information.

For general information on offline access control behavior, see Verkada Access Offline Operation.

What if 2 devices become fully disconnected (no cloud or local connection)?

Devices with cross-device configurations will not operate correctly without a cloud or local connection.

To restore operation and to resolve the issues with cloud or local connection, follow these troubleshooting steps:

Prefer to see it in action? Check out the video tutorial.

Need more help? Contact Verkada Support.

Last updated

Was this helpful?