Ozone level crossed threshold
The Ozone level crossed threshold trigger fires when the ozone (O3) reading on one or more air quality sensors crosses a specific level. Ground-level ozone forms when sunlight reacts with pollutants from vehicles and industry, and it tends to peak on hot, sunny afternoons. High ozone levels irritate the lungs and are especially risky during outdoor exercise.
Imagine getting a notification before your afternoon run telling you ozone is too high to exercise outside today. Or having your ventilation system close its fresh-air intake automatically when ozone spikes, so your indoor air stays clean without you thinking about it. This trigger watches the sky for you and lets your home take action the instant conditions become unhealthy.
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 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.
- From the triggers shown for that target, select Ozone level crossed threshold.
- Under Threshold type, set the ozone level the reading must cross for the trigger to fire.
- Under Trigger when (see Behavior), pick Any, First, or Last to control how multiple targets interact.
- Under For at least, set how long the level must stay past the threshold before the trigger fires. Leave at the default to fire immediately.
- Select Save.
Options in the UI
The ozone concentration the reading has to cross for the trigger to fire. Can be a fixed number, or reference a helper entity that provides the value.
When multiple sensors are targeted, controls when the trigger fires. Pick Any to fire every time any targeted sensor crosses the threshold, First to fire only on the first crossing, or Last to fire only after the last crossing.
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.ozone_crossed_threshold. A basic example looks like this:
trigger: air_quality.ozone_crossed_threshold
target:
entity_id: sensor.backyard_ozone
options:
threshold: 100
behavior: any
This fires whenever the backyard ozone sensor crosses 100 in either direction.
Options in YAML
YAML sometimes provides additional options for more complex use cases that are not available through the UI.
The ozone concentration the reading has to cross for the trigger to fire. Accepts a number or a reference to an input_number, number, or sensor entity.
When multiple sensors are targeted, controls when the trigger fires. Accepts any, first, or last.
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 fires on any crossing, up or down. If you only want one direction, add a condition that checks whether the current ozone level is above or below your threshold.
- Ground-level ozone peaks on hot, sunny afternoons. Automations that close fresh-air intakes or notify household members before outdoor activities are common use cases.
- Pair this trigger with Ozone level changed if you also want to track smaller fluctuations between crossings.
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: remind yourself to exercise indoors on high-ozone days
On hot afternoons, ground-level ozone spikes without any visible sign. This automation sends a notification when your backyard ozone sensor crosses 100, giving you a friendly heads-up to take your workout inside.
- Trigger: Ozone level crossed threshold
- Target: Backyard ozone sensor
- Threshold type: 100
- Trigger when: Any
- Condition: Ozone is above 100
- Action: Notify mobile app
YAML example for ozone exercise advisory
alias: "Ozone exercise advisory"
triggers:
- trigger: air_quality.ozone_crossed_threshold
target:
entity_id: sensor.backyard_ozone
options:
threshold: 100
behavior: any
conditions:
- condition: numeric_state
entity_id: sensor.backyard_ozone
above: 100
actions:
- action: notify.mobile_app_phone
data:
title: "High ozone outside"
message: >
Ozone crossed 100. Consider
exercising indoors today.
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:
- Ozone level changed - Triggers after one or more ozone levels change.