Skip to main content
All CollectionsAir Quality SensorsConfiguration and Setup
Third-Party VMS Integrations for Air Quality Sensor Events
Third-Party VMS Integrations for Air Quality Sensor Events

Receive and view sensor event alerts from an on-premise video management system

Updated this week

Air Quality sensors offer your organization a way to monitor essential indoor air quality factors, such as vape index, temperature, humidity, and more.

Third-party video management system (VMS) integrations allow Verkada sensors to send alert events to on-premise VMS, such as Milestone X-Protect, Wisenet WAVE, or exacqVision. These integrations allow you to receive and view sensor event data within your VMS system, eliminating the need to build custom APIs or manually match sensor events to camera footage.

Each VMS integration varies based on integration prerequisites set by the manufacturer. You will receive an alert that can be easily linked to a camera and includes the sensor name, sensor reading, reading value, threshold surpassed, and timestamp.

At this time, the video integration feature only sends alert event data. It does not send time-series data or graph data.

Supported third-party VMS providers

  • Milestone X-Protect

  • Wisenet WAVE

  • exacqVision


Enable third-party VMS integrations

You need Org Admin permissions and Site Admin permissions for each site that the sensors are located in to enable this feature.

To activate the Third-Party VMS Integration functionality on your sensors, you first need to enable the feature for your organization.

  1. In Verkada Command, go to All Products > Admin .

  2. Select Privacy & Security> Feature Manager.

  3. Under Air Quality > Third-Party VMS Integration, select Enable from the dropdown.

Set up a third-party VMS integration

A sensor may only be connected to a single VMS server. Once integrated, the device will appear as Unavailable if a different video integration is initiated.

Sensor must be on the same local network and VLAN as the third-party VMS server.

  1. In Command, go to All Products > Air Quality.

  2. On the left navigation, click VMS Integration .

  3. Select a Video Management System.

    1. Click Submit a suggestion to send a suggestion to our product team.

    2. In the top right, click + Add Integration select another supported VMS

  4. Each VMS integration will be slightly different, but you will need to enter the following:

    1. Server IP Address: The IP address of your VMS server.

    2. Server Port Number: The port on your VMS server which will be able to receive events.

    3. (If applicable) Username: A configured username that is capable of receiving alerts into the system.

    4. (If applicable) Password: Password for the configured user above.

  5. Select the sensors you would like to connect and click Integrate.

  6. The devices will begin to receive the configuration and attempt to establish a connection to the VMS server. This may take a few minutes to complete.


Status indicators on Command

  • Green: Successfully connected or submitted an event.

  • Orange: The device may be offline or has not yet submitted a status to the backend.

  • Red: Failed to connect or failed to submit an event to the VMS server.

The Refresh button checks if any of the devices have submitted any events or attempted connections to the server. It does not force the device to connect to the server.


Mange Third-Party VMS Integration

Edit integration

  1. In Command, go to All Products > Air Quality.

  2. On the left navigation, click VMS Integration .

  3. You will see a list of existing integrations

  4. Next to the integration you want to edit click > Edit Integration.

    1. Modify the configuration as needed.

    2. Click Edit Devices.

    3. Click Save Changes.

Delete integration

  1. In Command, go to All Products > Air Quality.

  2. On the left navigation, click VMS Integration .

  3. Next to the integration you want to delete click > Delete Intergration.

    1. Enter the confirmation code.

    2. Click Delete.


What needs to be done on the VMS Server Side?

The process differs between each VMS. Refer to their documentation for precise instructions.

In general, the following steps must be completed:

  • Create generic or user defined events for each device & reading.

  • Create alarms for the events.

  • Create rules to set up custom actions such as trigger camera recording or notifications.

  • Create mappings between these different elements:

    • Event → Alarms → Rules → 3rd Party Camera Association

You may need to repeat these steps for each device.


Need more help? Contact Verkada Support.

Did this answer your question?