Carbon monoxide (CO) card

Who it’s for

Environmental health officers, air quality managers, and smart city operators ask “is carbon monoxide at this monitoring point within safe limits right now?” They embed this widget in air quality dashboards to catch CO spikes from traffic, industrial sources, or combustion equipment before concentrations reach dangerous levels.

What it does

A monitoring station reporting carbon = 3.2 mg/m³ displays the reading on a color-coded card: green for Good (0–5 mg/m³), light green for Moderate (5–10 mg/m³), orange for Elevated (10–25 mg/m³), dark orange for High (25–50 mg/m³), and red for Hazardous (above 50 mg/m³).

• Live CO reading in mg/m³ with automatic color coding across five severity bands
• Severity bands follow WHO and EU air quality guideline thresholds for carbon monoxide
• Shows one sensor’s reading per widget; add multiple widgets to monitor stations across a network

How to set up

Data keys

Key	Role	Type	Description
carbon	Main value	Timeseries	Carbon monoxide concentration in mg/m³; change the key name to match your device’s telemetry key

The widget ships with a simulated function datasource key labeled Carbon monoxide, so it draws random values until you point the datasource at a device and rename the key.

To point it at your own device: open the dashboard in edit mode, open the widget’s Datasources, pick the entity or entity alias, and replace the function key with the key your device reports.

Value ranges

Range	Level	Color
0–5	Good	Green
5–10	Moderate	Light Green
10–25	Elevated	Orange
25–50	High	Dark Orange
50+	Hazardous	Red

How to customize

• To change the severity thresholds — edit Icon color ranges and Value color ranges; set the same boundaries in both so the icon and the number always agree.
• To change the band colors — edit the color for each severity level in the widget settings to match your organization’s color scheme.
• To rename the units label — change the Units field in the widget settings if your sensor reports in ppm instead of mg/m³.

Tips

• Store the sensor calibration date as a device attribute and display it alongside this widget — a drifting baseline is often a calibration issue rather than a real emission event.
• For compliance reporting, pair this card with a CO chart card so inspectors see both the current reading and the daily trend without switching views.