メインコンテンツにスキップ
すべてのコレクションアクセスコントロール
Cross-Device Local Connections for Access Control
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.

Note: 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.

Note: 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

ナンバープレート認識(LPR)ロック解除

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.

手記: 詳細については 、ナンバープレート認識の設定 を参照してください。

AUX inputs

AUX inputs can unlock doors when a device wired into the AUX input is triggered, such as a third-party intercom or button.

AUX inputs can unlock doors controlled by access controllers (other 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 unlock doors wired to a Verkada AC42 or AC62.

AUX出力

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.


ローカル接続ステータスの確認

LPRロック解除

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 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.

接続ステータス

ステータス

説明

完全に接続されたデバイス

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

デバイス接続の問題

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

一部のデバイスが完全に切断されている

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.

Note: 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).


ローカル接続の問題のトラブルシューティング

クロスデバイスローカル接続にはどのポートが使用されますか?

Verkadaデバイスは、デバイス間のローカル接続に次のポートを使用します。

  • 50000-60000: WebRTC接続は、新しい接続のためにこの範囲からポートを選択しました。

  • 5353:マルチキャストDNS(mDNS)のデフォルトポート。

  • 4929: デバイスのローカルにアドバタイズされたHTTPSサーバー。

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

  1. 両方のVerkadaデバイスの電源がオンになっていて、同じLANに接続されていることを確認します。

  2. LANが、ローカル接続に使用されるポート(上記の特定のポートを参照)を介したデバイス間の通信をブロックする方法で構成されていないことを確認します。

ローカル接続を持つ2台のデバイスがクラウド接続を失った場合はどうなりますか?

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:

  1. Confirm that devices can connect to the internet.

  2. Check the network settings and confirm they have not been changed to prevent cloud communication. See Access Control Network Settings for more information.

オフラインアクセス制御の動作に関する一般的な情報については、「 Verkada Access Offline Operation」を参照してください。

2台のデバイスが完全に切断された(クラウドまたはローカル接続がない)場合はどうなりますか?

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:

関連資料


サポートが必要な場合はVerkadaサポートにお問い合わせください。

こちらの回答で解決しましたか?