How to test the vape detection feature
This guide covers how to properly test vape detection on your Triton sensor, what to expect, and why manual tests often produce misleading results. Before testing, please read this guide fully — most "failed" tests are caused by improper technique, not a sensor issue. For a visual walkthrough including a video demonstration, follow the Scribe guide linked below.
→ Full testing guide with video
For a deeper dive into how the detection technology works, see our Vape Detection Technology: Operational Reference Guide and FAQs.
Why do manual vape tests often produce inconsistent results?
Triton's vape detection algorithms are trained on thousands of real-world vaping events — they're built to detect how people actually vape in bathrooms and enclosed spaces, not artificial test conditions. Common testing mistakes include blowing vapor directly into the sensor (which overwhelms it and triggers a "masking" event instead), not accounting for the cooldown timer between alerts, or emitting too little vapor to reasonably reach the sensor.
These issues make the sensor appear less effective than it actually is. For this reason, we strongly recommend against using manual vape tests as your primary measure of sensor performance. Real-world usage and Triton Cloud reporting are far more reliable indicators.
That said, if you want to run a test, follow the procedure below carefully.
What do I need to do before testing?
Allow a warm-up period. Give the sensor 15–20 minutes after booting up to stabilize before testing.
Understand the cooldown timer. There is a built-in 15-minute lockout between vape and masking alerts. If the sensor just triggered, it will not alert again until the air clears and the timer resets. Wait the full 15 minutes before retesting.
Know your coverage area. Coverage is typically 12ft x 12ft at an 8.5ft ceiling height. For every 1ft of additional ceiling height, the range decreases by 2ft in all directions. The maximum recommended mounting height is 11–12 feet — above that, vapor dissipates before reaching the sensor. Extension poles are available to lower the device if needed, and wall mounting is possible but will reduce coverage area by roughly half and impact people counting and loitering accuracy.
Set up real-time monitoring. Log into your Triton Cloud or on-prem dashboard so you can watch the results live:
- Triton Cloud: Make sure the alert slider for vaping is turned on, add users to receive alerts, and optionally configure the Speaker and Light for audio/visual verification.
- On-prem dashboard: Log in to the sensor's IP address and go to Actions → Action Settings to set up visual or auditory alerts.
How do I properly test vape detection?
- Use a disposable vape. If you don't want to inhale, you can blow into the air intake hole at the bottom of most disposables to force vapor out of the mouthpiece.
- Stand 2–3 feet away from the sensor.
- Blow a significant cloud of vapor toward the sensor — but do not blow directly into it.
- Be patient. It takes time for the vapor to travel through the air and for the algorithm to process the data. You can watch the sensor values change on the dashboard in real time. Once the values change, the device will run the data through its algorithm and determine whether to trigger an alert.
What if the test doesn't trigger an alert?
Check the cooldown timer. If the sensor triggered a vape or masking alert within the last 15 minutes, it won't alert again until the timer resets.
Check the event history. Look at the "History" tab in the cloud or on-prem dashboard. If you see a "Masking" event instead of a vape event, the vapor was blown too hard or too directly into the sensor.
Check your alerting schedule. For Triton Cloud customers, alerts are often set by default to Weekdays, 7:30 AM – 3:30 PM. If you're testing after hours or on a weekend, the system may suppress the notification even though the event was detected. Check the History tab to confirm.
Not enough vapor. If nothing registers at all, you may not have produced enough vapor to reach the sensor's threshold at that distance.
Quick troubleshooting reference:
- No alert → Device is likely in the 15-minute cooldown, or not enough vapor was used.
- "Masking" event instead of vape → Vapor was blown too hard or directly into the sensor.
- Slow response → Air currents may be moving the vapor away from the sensor's intake.
- No text/email notification but event shows in history → Alerting schedule is suppressing notifications outside of configured hours.
What about sensitivity?
Triton sensors are intentionally calibrated to be moderate in sensitivity out of the box. During the first two weeks, customers are often surprised by the volume of alerts — we keep sensitivity moderate initially so you aren't overwhelmed while still setting up response protocols.
Every environment is different. If you find the sensors aren't catching enough activity for your facility, we can adjust sensitivity remotely. Just reach out to support@tritonsensors.com and we'll fine-tune your devices.
Best practices for validating sensor performance
Trust the placement guide. Following the recommended height, coverage, and location guidelines ensures optimal performance.
Use Triton Cloud reporting. Real-time alerts, event history, and reports provide far more useful proof of performance than forced tests. Use them to identify hotspots, time-of-day patterns, and alert trends.
Allow time for real use. The most accurate "test" is when real vaping events occur in the building. Give the sensors a few weeks of real-world operation before drawing conclusions.
Need help or want sensitivity adjusted? Contact us at support@tritonsensors.com or call 800-305-1617.