The Verkada SV11 is a multi-sensor, non-camera device with a wide range of applications for environmental monitoring. The device includes sensors for monitoring temperature, humidity, air quality, noise levels, and motion.
Use Cases for the Verkada Environmental Sensor
Monitoring temperature and humidity in IDF closets, server rooms, data centers, and other areas with sensitive equipment or supplies
Monitoring performance of air conditioning and air filtration systems with proactive alerting from temp, humidity, PM 2.5, and TVOC sensors
Monitoring motion/occupancy and noise levels to detect activity or disturbances in areas where cameras are not tolerated - private spaces, conference rooms, hotel rooms, managed properties, bathrooms, changing rooms, locker rooms, hospital rooms, etc.
What is the range of the SV11 for vape detection?
When mounted on an 8 ft ceiling, the SV11 can detect vaping events within a 150 sq ft area around the sensor, or a 7 ft radius. Higher ceilings or increased distance from the sensor will decrease detection accuracy, as the vape/smoke particles are less likely to reach the sensor in sufficient concentrations. The range for vape detection and other sensors is also dependent on airflow, ventilation, filtration systems, and other variables. In most cases, alert thresholds for all sensors can be calibrated to meet the unique needs of your environment.
What are the install requirements and considerations?
The SV11 has the same mounting plate as the Dome Series cameras and is compatible with all Dome Series mounts. The SV11 should be installed on ceilings, wall mounting is possible but will degrade performance for air quality (PM 2.5, TVOCs, Vape Index) measures. We recommend installing at a maximum height of 8ft for best air quality measurements. If air quality is not an intended use case, the device can be mounted at other heights or orientations.
The SV11 is not a life safety device, and should not be used as a smoke or carbon monoxide detector.
The SV11 Vape Index measures air quality events indicative of vaping and smoking, but cannot provide 100% proof of a vaping incident. School security and administrative teams should use the SV11 Vape Index and Verkada camera integration to help with investigations and monitor vaping activity and patterns, but use searches for physical evidence as the basis for further disciplinary/legal actions.
Common bathroom aerosols will not trigger the Vape Index, however; it’s possible that certain smoke or cooking fumes can be identified as a vape event. In practice, this is rare in typical school environments.
SV11 will be less able to detect vaping/smoking incidents if a person uses significant efforts to hide the activity, such as exhaling into a closed container, out of a window, etc. However, the more typical behavior of breathing into a shirt or jacket still results in a detected vape event in our testing.
How does it work?
As vaping occurs, users can see spikes in Verkada’s Vape Index, which measures against a range of different onboard sensors to identify the likelihood of vaping or smoking occurring on a scale of 1 to 100. Administrators can set custom thresholds to receive real-time alerts via SMS and email. When detected, an alert can also be sent to pre-selected faculty members and on-campus security, allowing teams to respond quickly.
All sensor data is accessible from Verkada’s Command platform and is put against a timeline to give administrators a complete view of when these events took place. Additionally, administrators can pair a Verkada camera with any sensor, providing a layer of visual evidence to see exactly what happened. For locations like bathrooms, cameras can be placed outside these private areas, giving administrators a non-invasive way to monitor these incidents.
This article explains how to add a device to your Command account. The Verkada SV11 will begin working immediately after it's claimed and plugged in, but you may want to tweak the settings. Before you do so, read through Verkada SV11 Settings Explained.
The Verkada SV11 outputs data to a graph in Command for quick viewing. Check out this article for examples and explanations of the data you'll get from your sensor.
NOTE: For temperature calibration, it typically takes 2-3 hours