Why Does Indoor Air-Quality Data Look Different Near Windows and HVAC Vents?
Air-quality readings differ near windows and vents because local airflow carries, dilutes, heats, cools, or deposits pollutants before the room fully mixes.
A CO2 sensor beside a supply vent may fall quickly while another across the room changes slowly, and a window sensor may track outdoor particles. Neither reading must be wrong. Each device samples a small air parcel shaped by nearby flow, source distance, and mixing time.
Windows Couple the Room to a Changing Outdoor Source
An open or leaky window exchanges air according to wind, temperature difference, and pressure. Outdoor particles or ozone may rise near the opening while indoor-generated CO2 falls. The direction can reverse as conditions change, so “fresh air” is not one fixed chemical input.
A residential comparison reports that opening or tilting windows raises indoor-outdoor particle ratios for particulate matter relative to closed conditions. That supports a real spatial gradient near the outdoor boundary.
The window sensor reacts first because transport time is short. A central sensor sees a diluted, delayed version after mixing and deposition. Averaging them erases useful location information, while treating either as the whole-room truth overstates its representativeness.
HVAC Jets Create Clean, Stale, Warm, and Cool Pockets
Supply air forms a jet that entrains room air as it travels; return vents pull a broader mixture. A sensor placed directly in supply flow can report the system output rather than occupant exposure. Temperature and humidity shifts also affect some low-cost gas and particle sensors.
Research on spatial air-quality patterns shows distributed low-cost networks can reveal where and when pollutants enter buildings. Multiple positions are valuable precisely because indoor air is not perfectly mixed.
Intermittent fans create sawtooth data: the vent sensor changes quickly at startup, while room-center readings follow later. A kitchen or occupied zone may move in the opposite direction if local sources continue. More sensors do not automatically create disagreement; they reveal transport.
Where Placement Is Not the Only Explanation
Real gradients do not excuse uncalibrated sensors. Different warm-up times, humidity compensation, aging, dust loading, and vendor algorithms can create offsets even side by side. A window may also expose one unit to sun or condensation, altering electronics rather than sampled air.
A residence study using low-cost sensor networks demonstrates the value of networks for characterizing indoor conditions, but comparable placement and quality control remain necessary before interpreting differences as airflow.
The airflow explanation fails when sensors remain separated after a 24-hour side-by-side co-location, or when one device steps without any environmental change. It also fails for a pollutant the sensor does not directly measure. Composite air-quality indexes can diverge because vendors weight inputs differently.
Co-Locate Sensors Before Mapping Airflow Gradients
Co-locate every sensor for at least a day away from windows, vents, sun, and sources, then move them to window, supply, return, breathing-zone, and room-center positions. Log HVAC state, window state, occupancy, cooking, outdoor conditions, temperature, and humidity at the same cadence.
Use the distributed sensor data concept to keep sensor traffic and timestamps consistent; transport or database gaps should not masquerade as air movement. Preserve raw channels, not only a composite index.
Subtract co-location offsets before mapping gradients. If differences follow fan or window state with plausible delays, local transport is causal. If one device keeps the same offset everywhere, calibrate it. Choose sensor position according to the question: system output, source detection, or representative occupant exposure.
Recommended products
Tech & AI HUB
More to Read
How to Measure Local RAG Retrieval Quality and Interpret Recall, Precision, and Citation Coverage
Build a local RAG test set, calculate core retrieval metrics, interpret their tradeoffs, and audit whether answer claims are supported by cited evidence.
Why Does Smart Home Feature Computation Matter More as Sensor Count Increases at the Same Sampling Rate?
Trace per-sensor and cross-sensor compute as device count rises, identify nonlinear fusion costs, and benchmark the feature pipeline before automations lag.
Why Does RAG Evaluation Cost Matter More as the Document Library Grows at the Same Query Volume?
Understand why corpus growth raises RAG evaluation effort without more user queries and how stratified tests keep cost tied to risk.
