Carbon monoxide cleared
The Carbon monoxide cleared trigger fires after a carbon monoxide sensor entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] stops detecting carbon monoxide, confirming that the air in your home is safe again. After the urgency of a CO alarm, knowing exactly when the danger has passed brings real peace of mind. Use this trigger to silence a siren, send an all-clear notification to everyone in the household, or restore your home to its normal state so you and your family feel safe resuming everyday life.
Requires the Purpose-specific triggers and conditions Labs preview feature. Enable it at Settings > System > Labs.
Using this trigger from the user interface
If you prefer building automations visually, Home Assistant walks you through this trigger step by step. You pick what to watch, tweak a few options, and save. No YAML knowledge required.
To use this trigger in an automation:
- Go to Settings > Automations & scenes.
- Open an existing automation, or select Create automation > Create new automation.
- In the When section, select Add trigger.
- Select what you want to monitor. Under By target (see Targets), pick the area your CO sensor is in (like your kitchen or garage). You can also select a floor, a device, a specific entity, or a label.
- From the triggers shown for that target, select Carbon monoxide cleared.
- Under Trigger when (see Behavior), pick Any, First, or Last to control how the trigger behaves when multiple sensors are targeted.
- Under For at least, set how long the sensor must stay in the cleared state before the trigger fires. Leave it at zero to fire immediately.
- Select Save.
Options in the UI
When multiple sensors are targeted, controls when the trigger fires. Pick Any to fire every time any targeted sensor clears, First to fire only when the first sensor in a group clears, or Last to fire only after every targeted sensor has cleared.
Using this trigger in YAML
If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.
In YAML, refer to this trigger as air_quality.co_cleared. A basic example looks like this:
trigger: air_quality.co_cleared
target:
entity_id: binary_sensor.hallway_co
This fires every time binary_sensor.hallway_co transitions to the cleared state.
Options in YAML
YAML sometimes provides additional options for more complex use cases that are not available through the UI.
Targets
This trigger supports targets. A target tells Home Assistant what the trigger should watch. You can point it at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant watches every matching air_quality entity behind that target.
-
Entity: one specific air_quality entity, such as
air_quality.living_room. - Device: every air_quality entity that belongs to a device.
- Area: every air_quality entity in a room or area.
- Floor: every air_quality entity on a floor.
- Label: every air_quality entity that shares a label.
You can also mix target types in one trigger. For example, combine a specific entity with an area to watch both at once.
Behavior with multiple targets
When you target more than one entity (or select an area, floor, or label that contains several), the Trigger when option controls how the trigger responds:
- Any (default): the trigger fires every time any one of the targeted entities transitions. For example, if you monitor three motion sensors in the living room and someone walks past sensor 1, the automation fires. When they walk past sensor 2 a moment later, it fires again. Every individual event counts.
- First: the trigger fires only on the first transition in the targeted group, then waits until all targeted entities have reset before it fires again. For example, if you monitor the same three motion sensors, the automation fires when the first one picks up movement (someone entered the room). The other two firing afterward are ignored, so you get one notification per “someone walked in” event instead of three.
- Last: the trigger fires only after the last targeted entity in the group has fired, meaning all of them are now in the expected state. For example, if you monitor the lights in the living room, bedroom, and hallway, the automation fires only once all three have turned off. This is useful for scenarios like “start the robot vacuum only after every light on the floor is off,” so you know the room is truly empty.
Good to know
- The trigger only fires when a sensor transitions from a known, valid state. If a sensor comes back from being unavailable (
unavailable) or having an unknown state (unknown), the trigger does not fire for that recovery. - Use the For at least option to confirm the air has truly cleared before taking action. A delay of ten or fifteen minutes helps avoid premature all-clear alerts.
- To react to the opposite transition, use Carbon monoxide detected.
Try it yourself
Ready to test this? Go to Settings > Automations & scenes, create a new automation, and add this trigger. Save the automation, then change the state of the targeted entity to watch the trigger fire on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more].
More examples
Real scenarios where this trigger fires in automations and scripts. Copy any example and adapt it to your setup.
You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.
Automation: silence the siren and let everyone know it is safe
After a carbon monoxide alarm, a blaring siren and anxious waiting are the last things your family needs once the danger is over. This automation waits until every CO sensor in the house has been clear for fifteen minutes, then silences the siren and sends a reassuring all-clear notification to your phone. No more wondering whether it is truly safe to go back to sleep or return home.
- Trigger: Carbon monoxide cleared
- Target: All CO sensors (by label)
- Trigger when: Last
- For at least: 00:15:00
- Action: Siren: Turn off
- Action: Send a mobile notification
YAML example for silencing the siren after CO clears
alias: "Silence siren after CO clears"
triggers:
- trigger: air_quality.co_cleared
target:
label_id: co_sensors
options:
behavior: last
for: "00:15:00"
actions:
- action: siren.turn_off
target:
entity_id: siren.home_alarm
- action: notify.mobile_app_phone
data:
message: "All CO sensors are clear."
title: "CO all-clear"
Still stuck?
The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the trigger you’re using and what you expected to happen, or share on our subreddit /r/homeassistant.
AI assistants like ChatGPT or Claude can also explain triggers or suggest the right one when you describe what you want in plain language.
Related triggers
These triggers work well alongside this one:
- Carbon monoxide detected - Triggers after one or more carbon monoxide sensors start detecting carbon monoxide.