IoT Air Quality Sensors Explained

A modern IoT air quality node packages one or more sensors (CO₂, PM, TVOC, T/RH typically) with a microcontroller, a radio, a battery or PoE feed, and a small amount of local storage. Quality varies enormously.

The questions that matter at node level are: sensor technology and traceable calibration; sampling rate and on-device averaging; local data buffering for network outages; firmware update path; tamper and ingress protection; and physical mounting that does not bias the reading. A consumer-grade WiFi monitor in a plastic enclosure will not survive a year in a school corridor; a properly engineered industrial node will run for a decade.

Wi-Fi. Convenient for indoor deployments where IT will allocate an IoT VLAN. High bandwidth, short range, frequent reconnections, high battery cost.

LoRaWAN. Sub-GHz long-range protocol with a small payload (~50 bytes) and an asymmetric duty cycle. A single LoRaWAN gateway covers a building or campus; battery life on the node side runs into years. Standard choice when IT will not sanction Wi-Fi or when sensors are scattered across a wide footprint.

Cellular (NB-IoT, LTE-M). Direct connection to mobile networks; no gateway needed. Standard for outdoor sensors, roadside air quality mapping deployments and isolated sites.

Bluetooth, Zigbee, Thread. Niche for very local mesh deployments; less common in commercial AQ work.

The wrong protocol is usually the one that "should just work" — Wi-Fi sensors in buildings whose IT department changes the SSID every month, or LoRaWAN sensors with no gateway plan.

The cloud layer is where data becomes useful. A serious platform provides: ingest at the scale of your fleet; per-device authentication and metadata; time-series storage with months-to-years retention; configurable rule-based alerting; dashboard composition; API access for external integration; and audit logging.

Vendor-locked dashboards age badly. The most durable architectures expose raw data over a documented API so the visualisation layer can be replaced or extended without re-deploying sensors. See our air quality dashboard approach.

A fleet of 10 sensors is a project. A fleet of 500 sensors is an operations problem. Device management capability — provisioning, remote configuration, OTA firmware, health monitoring, decommissioning — separates serviceable IoT platforms from unserviceable ones.

The fleet metrics worth dashboarding are: heartbeat rate per device, battery state of charge, last successful uplink, firmware version distribution, calibration due date and signal quality. A dropped heartbeat that goes unnoticed for weeks is invisible data loss with potentially compliance-affecting consequences.

Air quality data is rarely personal data, but the sensors are connected devices on a corporate network — which makes the security posture an IT problem, not just an air quality problem. The minimum bar is TLS in transit, AES at rest, per-device credentials, signed firmware and a published responsible-disclosure policy.

Occupancy and motion data, when combined with timestamps, can become personal data under UK GDPR. Treat the data accordingly: minimise collection, set retention windows and document the lawful basis if you process it.

The unglamorous half of an IoT deployment is keeping it running. Batteries die, sensors drift, gateways fail, firmware ages out, IT changes break connections. A sustainable programme budgets at least 15–25 % of the capex annually for opex — battery replacement, recalibration, site visits, firmware lifecycle, platform fees.

Calibration in particular cannot be skipped. See how air quality sensors are calibrated for the methodology and environmental monitoring systems for the full-lifecycle service view.

• What is the difference between LoRaWAN, Wi-Fi and cellular for air quality sensors?

  Wi-Fi is the default indoors but reuses the corporate network and can be locked down by IT. LoRaWAN is long-range, low-power and uses a separate dedicated gateway — useful for buildings where IT will not sanction Wi-Fi sensors. Cellular (typically NB-IoT or LTE-M) is the fallback for sites with no fixed network, common for outdoor and roadside deployments.

• How long do IoT air quality sensor batteries last?

  Battery life ranges from a few months for high-density Wi-Fi sensors with frequent uplinks to 5–10 years for LoRaWAN sensors transmitting hourly. Power budget is dominated by radio transmission, not sensing, so the protocol choice usually drives the battery decision.

• Is sensor data secure in transit and at rest?

  Reputable IoT platforms use TLS in transit and AES at rest, with per-device certificates or pre-shared keys for authentication. Verify the vendor's documentation on key management, certificate rotation and tenant isolation before deployment, and never accept a platform that exposes raw MQTT brokers on the public internet.

• How are firmware updates handled in a fleet?

  Over-the-air (OTA) firmware management is standard for modern IoT sensors. Insist on staged rollouts, rollback capability and signed firmware images. A fleet of 200 sensors with no OTA path is a fleet that will fall out of compliance the first time a vulnerability is published.