Smoke cleared

The Smoke cleared condition passes when one or more smoke sensors are no longer detecting smoke. After a smoke event, the last thing you want is to restore normal lighting or send an all-clear while one room still has hazy air. This condition acts as your safety gate, letting your automation continue only after every sensor in the house confirms the air is clear again.

Using this condition from the user interface

If you prefer building automations visually, Home Assistant walks you through this condition step by step. You pick what to check, tweak a few options, and save. No YAML knowledge required.

To use this condition in an automation:

1. Go to Settings > Automations & scenes.
2. Open an existing automation, or select Create automation > Create new automation.
3. In the And if section, select Add condition.
4. Select what you want to check. Under By target (see Targets), pick the area your smoke sensor is in (like your kitchen or garage). You can also select a floor, a device, a specific entity, or a label.
5. From the conditions shown for that target, select Smoke cleared.
6. Under Condition passes if (see Behavior), pick Any or All to control how the check behaves when multiple sensors are targeted.
7. Select Save.

Options in the UI

Using this condition 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. For how an automation is built in YAML, refer to Automations in YAML.

In YAML, put the settings that are specific to this condition under options. Keep target, if the condition uses one, and general settings such as alias and enabled at the top level, next to condition.

In YAML, refer to this condition as air_quality.is_smoke_cleared. A basic example looks like this:

condition: air_quality.is_smoke_cleared
target:
  entity_id: binary_sensor.kitchen_smoke

This passes when the kitchen smoke sensor is no longer detecting smoke.

Options in YAML

Targets of the condition

This condition requires a target. The target is the object that Home Assistant will check. You can point the condition 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 will evaluate every matching smoke detector behind that target.

• Entity: one specific smoke detector, such as binary_sensor.hallway_smoke.
• Device: every smoke detector that belongs to a device.
• Area: every smoke detector in a room or area.
• Floor: every smoke detector on a floor.
• Label: every smoke detector that shares a label.

You can also select different target types in one condition. For example, you can add a specific entity and an area as targets in the same condition to check both of them at once.

To learn which entities Home Assistant includes for a device, area, floor, or label, and how it handles several entities, refer to Automation targets.

Behavior with multiple targets

When you target more than one entity (or select an area, floor, or label that contains several), the Condition passes if option controls how the results combine:

• Any (default): the condition passes if at least one of the targeted entities matches. For example, if you check three smoke sensors and only one of them detects smoke, the condition still passes. This is useful for questions like “is there smoke anywhere in the house?”
• All: the condition passes only when every targeted entity matches. For example, if you check the same three smoke sensors, the condition passes only once all three report cleared. This is useful for “is the entire house safe now?” checks, so your automation does not send an all-clear while one room still has a reading.

Good to know

• Sensors that are unavailable or unknown are skipped. With Any, the condition passes if at least one of the other targeted sensors matches. With All, it passes if all the other targeted sensors match. If all targeted sensors are unavailable or unknown, All passes and Any fails.
• To check whether smoke is currently detected, use Smoke detected.

Try it yourself

Ready to test this? Go to Settings > Automations & scenes, open an automation, and add this condition. Trigger the automation with and without the condition met, and watch whether it continues or stops.

More examples

Real scenarios where this condition gates an automation. Copy any example and adapt it to your setup. In the visual editor, select the UI options listed in the example or paste the YAML code.

Automation: only restore normal lighting once every smoke sensor has cleared

After a smoke event, you want to keep the emergency lights on until every room is safe. This automation triggers when you press the reset button, but the condition requires every smoke sensor to read clear before the normal lighting scene restores. If any sensor still detects smoke, the emergency lights stay on.

• Trigger: State changed: Reset lighting button pressed
• Condition: Smoke cleared
  • Target: All smoke sensors (kitchen, hallway)
  • Condition passes if: All
• Action: Activate scene (normal lighting)
• Action: Send a notification message
  • Target: My Device (notify.my_device)

alias: "Restore lights only after full smoke all-clear"
triggers:
  - trigger: state
    entity_id: input_button.reset_lighting
conditions:
  - condition: air_quality.is_smoke_cleared
    target:
      entity_id:
        - binary_sensor.kitchen_smoke
        - binary_sensor.hallway_smoke
    options:
      behavior: all
actions:
  - action: scene.turn_on
    target:
      entity_id: scene.normal_lighting
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      title: "Smoke all-clear"
      message: >
        Every smoke sensor reads clear.
        Normal lighting has been restored.

Still stuck?

To find out why the condition didn’t pass, check it live in the automation editor, and look at the trace of the run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.

If that doesn’t help, the Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the condition you’re using and what you expected to happen, or share on our subreddit /r/homeassistant.

Related conditions

Explore related conditions:

• Smoke detected: Tests if one or more smoke sensors are detecting smoke.