Ozone value

The Ozone value condition passes when an ozone (O3) sensor’s reading meets a specific level. Ground-level ozone is a key component of smog and tends to spike on hot, sunny afternoons. This condition helps your automation make smarter ventilation decisions, keeping the windows shut during a smog alert but allowing fresh air in after the ozone reading decreases to a comfortable level.

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 air quality sensor is in (like your living room or bedroom). You can also select a floor, a device, a specific entity, or a label.
5. From the conditions shown for that target, select Ozone value.
6. Under Threshold type, set the ozone level the condition checks against.
7. Under Condition passes if (see Behavior), pick Any or All.
8. 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.

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

condition: air_quality.is_ozone_value
target:
  entity_id: sensor.outdoor_ozone
options:
  threshold: 100
  behavior: any

This passes when the outdoor ozone sensor reads at or above 100 µg/m³.

Options in YAML

YAML sometimes provides additional options for more complex use cases that are not available through the UI.

Targets

This condition supports targets. A target tells Home Assistant what the condition should check. 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 evaluates 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 condition. For example, combine a specific entity with an area to check 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 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 (unavailable) or have an unknown state (unknown) are skipped for Any and fail for All.
• Ozone levels tend to peak on hot, sunny afternoons. Pair this condition with time-based triggers to limit outdoor ventilation during those hours.

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.

Automation: only open windows in the afternoon if ozone is low enough

On hot summer days, ozone builds up through the afternoon and peaks around 3 PM. This automation triggers at that time and checks whether outdoor ozone is at or above 100 μg/m3. If the reading is still high, the windows stay shut, and you get a notification explaining why. On breezy days with lower ozone, the automation does nothing, and you enjoy fresh air as usual.

• Trigger: Time: 15:00
• Condition: Air Quality: Ozone value
• Target: Outdoor ozone sensor
• Threshold type: 100
• Condition passes if: Any
• Action: Cover: Close cover, then notify

alias: "Keep windows shut on high ozone afternoons"
triggers:
  - trigger: time
    at: "15:00:00"
conditions:
  - condition: air_quality.is_ozone_value
    target:
      entity_id: sensor.outdoor_ozone
    options:
      threshold: 100
      behavior: any
actions:
  - action: cover.close_cover
    target:
      area_id: living_room
  - action: notify.mobile_app_phone
    data:
      title: "Ozone is high outside"
      message: >
        Outdoor ozone is above 100. Windows
        are staying closed this afternoon.

Still stuck?

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

These conditions work well alongside this one:

• Nitrogen dioxide value - Tests the nitrogen dioxide level of one or more entities.

• Volatile organic compounds value - Tests the volatile organic compounds level of one or more entities.