Air Quality Sensors · Troubleshooting guide
An air-quality sensor is offline—are readings and alerts still working?
Understand the monitoring gap, preserve useful evidence and restore the sensor’s network connection.
Draft · Nov 13, 2026 · 4 min read
Editorial review pending. This sample article demonstrates the design; verify model-specific instructions before use.
Before you start
For Verkada SV-series air-quality sensors. Offline behavior differs between SV11 and SV20-series models, especially after a reboot; do not assume every outage can be backfilled.
Find the right troubleshooting path
| What you observe | What to investigate | Next check |
|---|---|---|
| Sensor offline but powered | Cloud communication is interrupted | Check network and last known reading time. |
| No power or repeated restarts | Recording continuity is uncertain | Check PoE source and outage history. |
| Online again; historical gap remains | Recovery depends on model and power history | Document the exact gap before escalating. |
Use these observations to narrow the cause; they are not a definitive diagnosis.
Work through the checks
Treat offline status as a monitoring gap
Verkada states that sensor alerts/events do not trigger while the sensor is offline. Follow the site’s alternate response procedure rather than assuming staff will receive a delayed real-time warning. Record the last online time and notify the person responsible for that area.
Reference: Loss of Network Connection for Air Quality Sensors (opens in a new tab)Identify the model and power history
Record whether the unit is an SV11 or SV20-series sensor, and whether it stayed powered, rebooted or lost power. The official outage reference describes different recording behavior by model and includes model-specific qualifications. Preserve those facts instead of promising complete historical recovery.
Reference: Loss of Network Connection for Air Quality Sensors (opens in a new tab)Check PoE and the network assignment
Have the network team confirm the switch port, compatible PoE supply and device address by MAC. Sensors need IPv4 connectivity and DNS. Confirm the actual sensor network is being tested; connectivity from an unrelated office workstation does not establish the same path.
Reference: Air Quality Sensor Network Settings (opens in a new tab)Check regional endpoints and static-IP assumptions
Use the sensor-specific network reference and the correct organization region. For SV20-series units with static configuration, account for the documented DHCP fallback when connectivity checks fail. Look for the current lease before treating a changed address as a missing device.
Reference: Air Quality Sensor Network Settings (opens in a new tab)Restore connectivity before disruptive resets
Avoid repeated power cycles while trying to preserve measurements from an outage. If power or network corrections do not restore the unit, contact support with the model and timeline. After recovery, inspect both fresh readings and the affected history interval; an online badge alone is not a complete test.
Reference: Loss of Network Connection for Air Quality Sensors (opens in a new tab)
Verify the result
Confirm current readings have fresh timestamps and inspect the outage interval for gaps. Review the existing offline-alert configuration and responsible recipients. Use a controlled, approved test procedure; do not create smoke or vape exposure just to test notifications.
If the issue remains
Provide model, serial, outage and reboot times, PoE observations, IP-assignment results and missing intervals. Ask support to assess recovery for that exact model rather than applying another generation’s behavior.
Official documentation
Sources checked November 13, 2026. Monarch’s diagnostic sequence combines these references with practical verification checks. Editorial review pending.
Join the conversation
Share what worked for you, or ask a follow-up. No account needed.
Building operations
Knowing whether power stayed on belongs in the outage ticket. We normally only note when the network came back.
School IT
I would make “fresh timestamp” part of the recovery check instead of stopping at the green online status.