# Configure BACnet on Air Quality Sensors Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) enable your organization to monitor essential indoor air quality factors, including [CO2](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), [CO](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), [PM 2.5](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), [PM 4.0](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), [PM 10.0](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), [AQI](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), [TVOC](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings), and [formaldehyde](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings). The [Building Automation and Control Networks (BACnet)](https://www.ashrae.org/technical-resources/technical-faqs/question-51-what-is-bacnet) integration allows Verkada sensors to inform a building’s Heating, Ventilation, and Air Conditioning (HVAC) system about air quality metrics or any sensor readings, enabling the building's HVAC to respond to these indoor air quality conditions. Verkada sensors can integrate with the Building Management System (BMS) protocol, BACnet. By integrating Verkada’s sensors with this protocol, your organization’s HVAC systems can now automatically respond to suboptimal air conditions. Learn more about [BACnet for Verkada Air Quality Sensors](https://help.verkada.com/air-quality/configuration/bacnet-for-verkada-air-quality-sensors). {% hint style="danger" %} To use this integration, your building must have a Building Automation System (BAS) that is compatible with BACnet IP. We recommend that you contact your HVAC specialist to understand if your system is supported. If you are unsure or need help, contact [Verkada Support](https://www.verkada.com/contact/). {% endhint %} *** ## Enable BACnet for your organization To activate the BACnet functionality on your sensors, you first need to enable the BACnet feature for your organization. {% stepper %} {% step %} **In Verkada Command, go to All Products > Admin.** {% endstep %} {% step %} **Select Feature Manager.** {% endstep %} {% step %} **Under Air Quality, enable Sensor BACnet.** {% endstep %} {% endstepper %} *** ## Enable BACnet on a sensor Once the BACnet feature is enabled for your organization, you’re ready to enable it on your devices. {% hint style="danger" %} BACnet is only available on the [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf), [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf), and [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) sensors. {% endhint %} {% stepper %} {% step %} **In Verkada Command, go to All Products > Air Quality.** {% endstep %} {% step %} **Select your sensor.** {% endstep %} {% step %} **At the top right, click** **.** {% endstep %} {% step %} **Under BACnet:** 1. Click the dropdown and select **Enable**. 2. Assign a unique **BACnet** **Device ID** to identify your sensor in your BAS/BMS. The Device ID identifies the device on the BACnet network; therefore, each Verkada sensor should have a unique Device ID in the range of 0–4194302. 3. Assign a **BACnet port**. The default BACnet port is **47808**, a commonly used UDP port for BACnet/IP, but it can also be any number in the range 47808–47823. We recommend keeping the UDP port unchanged, as the default value is widely used. 4. Click **Apply** to save your changes. {% endstep %} {% endstepper %} The BACnet server can now poll the device for properties. *** ## Disable BACnet on a sensor {% stepper %} {% step %} **In Verkada Command, go to All Products > Air Quality.** {% endstep %} {% step %} **Select your sensor.** {% endstep %} {% step %} **At the top right, click** **.** {% endstep %} {% step %} **Under BACnet:** 1. Click the dropdown and select **Disable**. 2. Click **Apply** to save your changes. {% endstep %} {% endstepper %} *** ## BACnet [PICS](https://www.bacnetinternational.net/catalog/manu/siemens/CM110665en_06_001.pdf) ### 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 (C) | AnalogInput | 2 | Degrees Celsius | | SV21, SV23, SV25 | Humidity | AnalogInput | 3 | % Relative Humidity | | SV21, SV23, SV25 | CO2 | AnalogInput | 4 | ppm | | SV25 | Carbon Monoxide | AnalogInput | 5 | ppm | | SV23, SV25 | Noise | AnalogInput | 6 | dB | | SV23, SV25 | AQI | AnalogInput | 7 | No Units | | SV23, SV25 | TVOC Index | AnalogInput | 8 | No Units | | SV23, SV25 | PM 2.5 | AnalogInput | 9 | μg/m^3 | | SV21, SV23, SV25 | Tamper | AnalogInput | 10 | No Units | | SV23, SV25 | Motion | AnalogInput | 11 | No Units | | SV25 | Light | AnalogInput | 12 | Lux | | SV25 | Pressure | AnalogInput | 13 | Hectopascal | | SV25 | Formaldehyde | AnalogInput | 14 | ppb | | SV23, SV25 | PM 4.0 | AnalogInput | 15 | μg/m^3 | | SV23, SV25 | PM 10.0 | AnalogInput | 16 | μg/m^3 | | SV21, SV23, SV25 | Heat Index | AnalogInput | 17 | Degrees Celsius | | SV21, SV23, SV25 | Dew Point | AnalogInput | 18 | Degrees Celsius | | SV21, SV23, SV25 | Humidex | AnalogInput | 19 | No Units | | SV21, SV23, SV25 | Mold Risk Index | AnalogInput | 20 | No Units | | SV23, SV25 | Reset Viral Index | AnalogInput | 21 | % | **Device** | | | | | --------------- | ------------------------------- | ----------------------- | | **Object Type** | **ID** | **Object Name** | | Device: | \ | \ | 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)