Skip to main content
All CollectionsCommand Connector
Add a non-Verkada camera to a Command Connector
Add a non-Verkada camera to a Command Connector

Connect non-Verkada cameras to Command with a Command Connector

Updated over a week ago

The Command Connector integrates non-Verkada cameras into Command. This allows you to view the camera live streams and access Verkada analytics and features.

User permission requirements

You need Organization Admin and/or Site Admin permissions for your Verkada Command organization to complete these actions.

Note: See Roles and Permissions for Command for more information.

Before you begin

Recommendation: Connecting a camera to multiple video security systems simultaneously can degrade streaming performance and lead to inconsistent video quality. Verkada recommends connecting each camera to a single system to maintain optimal performance and video integrity.

  1. Verify the non-Verkada camera datasheet states ONVIF Profile S compatibility. Check the Command Connector hardware compatibility list to make sure your model is compatible.

    Note: Verkada Command only supports I-frames and P-frames. B-frames are not supported.

  2. Verify the Command Connector and non-Verkada camera are on the same Local Area Network (LAN). Dynamic NAT or L3 translation is not supported between the devices.

  3. Verify the non-Verkada camera IP address is configured with one of the following:

    1. Static IP

    2. DHCP reservation

    The Command Connector communicates with cameras using IP addresses. If a camera's IP address changes, it will stop streaming.

  4. The Command Connector and non-Verkada camera need bidirectional traffic to communicate. Verify these ports are allowed on the network:

    1. TCP+UDP port 80 - needed for camera ONVIF HTTP web server access
      Note: If you are using a non-default port allow that port in TCP+UDP.

    2. TCP+UDP port 554 - needed for camera RTSP streams

  5. Ensure that the IP address, along with the admin username and password is available for each of the non-Verkada cameras that will be added to Command Connector


Add a camera to Command Connector

  1. In Command, go to All Products > Devices .

  2. Select a Command Connector.

  3. Under Connected Channels, click and select + Add Cameras.

  4. Cameras can be added in the following ways:

Network Discovery

If a non-Verkada camera is discoverable on the LAN, it can be added to the Command Connector via network discovery.

  1. Select Network Discovery to view the list of cameras discoverable to the LAN.

  2. Click the checkbox to select a camera. Then select + Credential and input the username and password.

  3. Select Continue to view the list of cameras successfully added.

CSV upload

A CSV template can be used to add cameras in bulk to the Command Connector.

Required. The IP address, username, and password fields are required. All other fields are optional.

  1. Download the csv template.

  2. Fill out the template.

    Note: The HTTP/ONVIF Port field is required if the camera is configured on a non-standard port.

  3. Select Upload CSV and upload your file.

Manually add cameras via IP address

  1. Select Manually Add IPs Instead. Input the IP address range and click Verify.

  2. Select the camera(s) you want to add and click Activate.


Verify non-Verkada camera ONVIF configuration

The Command Connector configures non-Verkada cameras through ONVIF. You can connect to the camera web server to validate the configuration.

  1. The Command Connector will create one administrator user with the username verkada.

  2. Two media profiles will be configured through ONVIF.

    1. An HQ stream labeled vkda-high.

    2. An SQ stream labeled vkda-low.

      Note: A pair of media profiles will be created per channel if the device is a multi-sensor and has multiple channels.

Note: The vkda-high profile will also be used for Verkada analytics and thumbnails.


Need more help? Contact Verkada Support.

Did this answer your question?