CO2, Temperature and Humidity Monitoring

How it works

Check that each sensor is reporting its expected measurements before setting up an alert. Use a descriptive rule name that includes the room and reading, and select the sensor or scope that the duty team can act on. Use a time filter to revisit a change and export the readings as CSV if another team needs to investigate the same period.

Set up the dashboard around the people who will use it. The operator checking conditions needs to find the relevant site, group and sensor quickly. The person responding to an incident also needs the time and reading that caused the alert. Agree on clear names and use the same names in rules so those two views make sense together.

Example alert rule

Configure a high-CO2 rule for a room and choose how long the reading must remain above the limit before it alerts. Email the responsible contact when the condition persists. The contact can review the room's CO2 history and any relevant temperature or occupancy readings, then assign someone to investigate and follow the incident until the condition clears.

Review readings and coordinate a response

Decide who should receive an email and who will take ownership when an incident opens. Acknowledge it to show that someone is responding, then assign it if another person needs to investigate. During planned work, use a maintenance or suppression window where appropriate. After the work, check that the expected readings are arriving again.

When reviewing an incident, use a time window that includes readings before the alert and after the condition cleared. Keep the measurement and unit consistent so the comparison is meaningful. A CSV export lets a colleague inspect the same readings, while the incident record keeps the response and assignment visible to the team.

Discuss your monitoring project

Tell us what you need to monitor, where the sensors are located and who should respond when conditions change.