All Collections
Air Quality Sensors
Configuration and Setup
How to configure BACnet on Verkada Air Quality Sensors
How to configure BACnet on Verkada Air Quality Sensors

Verkada allows customers to integrate their sensors with their building management system (BMS) using the popular BACnet protocol.

Updated over a week ago

Verkada Air Quality sensors offer organizations a way to monitor essential indoor air quality factors such as CO2, CO, PM2.5, AQI, TVOC, and formaldehyde. BACnet integration allows Verkada Air Quality sensors to inform a building’s HVAC system about an air quality metric, or any sensor reading for that matter, thus allowing the building HVAC to respond to these indoor air quality conditions. Verkada air quality sensors can integrate with the popular building management system (BMS) protocol BACnet. By integrating Verkada's air quality sensors with this popular protocol, organizations’ HVAC systems can now automatically respond to suboptimal air conditions.

Your building must have a Building Automation System which is compatible with BACnet IP to use this integration.


Verkada recommends you talk with your HVAC specialist to understand if your system is supported.

If you are unsure or need help, please contact Verkada Support.

Learn more about Verkada's BACnet integration here.

In this article:

How to enable BACnet for your organization using the Feature Manager

To be able to activate the BACnet functionality on your sensors, you first need to enable the BACnet feature for your organization.

  1. From the All Products menu, select the Admin page

  2. Select the Privacy & Security tab

  3. Click on the Feature Manager

  4. Under the Air Quality section, find Sensor BACnet and change it from Disable to Enable

How to enable BACnet on a Verkada Air Quality Sensor

To enable BACnet for your sensors, you will first need to navigate to the sensors dashboard from the All Products menu.

  1. From the All Products menu, select Air Quality

  2. Click on the sensor you want to enroll into BACnet

  3. Edit its settings by clicking on the gear icon from the top right corner of the page

  4. The option for BACnet should be available on the left-hand pane (if you do not see the BACnet option, ensure the device is an SV21, SV23, or SV25 and ensure BACnet is enabled for your organization).

    1. Select Enable from the dropdown to enable the feature for the sensor

    2. Next, assign a unique BACnet Device ID so that your sensor can be identified on your BAS/BMS

      1. The Device ID is used to identify the device on the BACnet network, therefore, each Verkada Sensor should have a unique Device ID in the range of 0 - 4194302.

    3. Then, assign a BACnet port.

      1. The default BACnet port is 47808, which is a commonly used UDP port for BACnet/IP, but it can also be any number in the range of 47808–47823. It is recommended that the UDP port stays unchanged since the default value is mainly used.

  5. Click Apply to save your changes

  6. BACnet should now be enabled on the device

    1. Anything on the BACnet server can now poll the device for properties

How to disable BACnet on a Verkada Air Quality Sensor

To disable BACnet for your sensors, you will first need to navigate to the sensors dashboard from the All Products menu.

  1. From the All Products menu, select Air Quality

  2. Click on the sensor you want to disable BACnet for

  3. Edit its settings by clicking on the gear icon from the top right corner of the page

  4. Click BACnet on the left-hand pane

  5. Select Disable from the dropdown to disable the feature for the sensor

  6. Click Apply to save your changes

  7. BACnet is now disabled on your device

BACnet PICS

BACnet Standardized Device Profile (Annex L):

  • Smart Sensor BIBB Device profile: B-SS

List all BACnet Interoperability Building Blocks Supported (Annex K):

Data sharing & Device and network management services

  • DS-RP-B

  • DM-DDB-B

  • DM-DOB-B

Segmentation Capability

  • Segmented requests supported: No Window Size

  • Segmented responses supported: No Window Size

Standard Object Types Supported:

An object type is supported if it is present in the device.

Supported Models

Name

Object Type

Instance

Units

SV23, SV25

Vape Index

AnalogInput

1

No Units

SV21, SV23, SV25

Temperature (F)

AnalogInput

2

Degrees Fahrenheit

SV21, SV23, SV25

Temperature (C)

AnalogInput

3

Degrees Celsius

SV21, SV23, SV25

Humidity

AnalogInput

4

% Relative Humidity

SV21, SV23, SV25

CO2

AnalogInput

5

ppm

SV25

Carbon Monoxide

AnalogInput

6

ppm

SV23, SV25

Noise

AnalogInput

7

dB

SV23, SV25

AQI

AnalogInput

8

No Units

SV23, SV25

TVOC Index

AnalogInput

9

No Units

SV23, SV25

PM 2.5

AnalogInput

10

μg/m^3

SV21, SV23, SV25

Tamper

AnalogInput

11

No Units

SV23, SV25

Motion

AnalogInput

12

No Units

SV25

Light

AnalogInput

13

Lux

SV25

Pressure

AnalogInput

14

Hectopascal

SV25

Formaldehyde

AnalogInput

15

ppb

Device

Object Type

ID

Object Name

Device:

<user-specified-id-in-command>

<device-serial-number>

Dynamically Creatable: No

Dynamically Deletable: No

Data Link Layer Options:

  • BACnet IP, (Annex J)

Device Address Binding:

Is static device binding supported? (This is currently necessary for two-way communication with MS/TP slaves and certain other devices.)

  • No

Character Sets Supported:

Indicating support for multiple character sets does not imply that they can all be supported simultaneously.

  • ISO 10646 (UTF-8)

Did this answer your question?