Humidifier turned off
The Humidifier turned off trigger fires after a humidifier 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] turns off. Use it to react the moment the device shuts down, whether it was switched off manually, by a schedule, or because the target humidity was met and the device powered down automatically.
When you target more than one humidifier, the Trigger when option controls when it fires. You can have it fire the first time any targeted humidifier turns off, only after all targeted humidifiers have turned off, or every single time any of them turn off.
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 Humidifier turned off 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 humidifier is in (like your bedroom or living room). You can also select a device, a specific entity, or a label.
- From the triggers shown for that target, select Humidifier turned off.
- Under Trigger when (see Behavior), pick Each, First, or All to control how the trigger behaves when multiple humidifiers are targeted.
- Under For at least, set how long the humidifier must stay off before the trigger fires. Leave it at zero to fire immediately.
- Select Save.
Options in the UI
When multiple humidifiers are targeted, controls when the trigger fires:
-
Each (
anyin YAML, default): fire every time any targeted humidifier turns off. -
First (
firstin YAML): fire only when the first of a group turns off. -
All (
lastin YAML): fire only after every targeted humidifier is off.
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, Humidifier turned off is referred to as humidifier.turned_off. A basic example looks like this:
trigger: humidifier.turned_off
target:
entity_id: humidifier.bedroom
This fires every time humidifier.bedroom transitions from on to off.
Options in YAML
YAML sometimes provides additional options for more complex use cases that are not available through the UI.
When multiple humidifiers are targeted, controls when the trigger fires:
-
any(Each in the UI, default): fire every time any targeted humidifier turns off. -
first(First in the UI): fire only when the first of a group turns off. -
last(All in the UI): fire only after every targeted humidifier is off.
Targets of the trigger
This trigger requires a target. The target is the object that Home Assistant will watch. You can select 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 as a target, and Home Assistant will watch every matching humidifier entity behind that target.
-
Entity: one specific humidifier entity, such as
humidifier.living_room. - Device: every humidifier entity that belongs to a device.
- Area: every humidifier entity in a room or area.
- Floor: every humidifier entity on a floor.
- Label: every humidifier entity that shares a label.
You can also select different target types in one trigger. For example, you can add a specific entity and an area as targets in the same trigger to monitor both of them 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:
-
Each (
anyin YAML, 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 (
firstin YAML): 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. -
All (
lastin YAML): 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 humidifier transitions from a known, valid state. Transitions from the Unavailable or Unknown state to off do not count.
- To react to the opposite transition, use Humidifier turned on.
- Pair Humidifier turned off with the
lastbehavior to do something only after every humidifier in an area has stopped. For example, send a single notification when all humidifiers in the house are off.
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: send an alert when the bedroom humidifier turns off unexpectedly
If the bedroom humidifier turns off during the night, send a notification so you can check whether it ran out of water or was switched off by accident.
- Trigger: Humidifier turned off
- Target: Bedroom humidifier
- Trigger when: Each
- For at least: 00:00:00
- Condition: Time is between 22:00 and 07:00
- Action: Send a mobile notification
YAML example for an overnight humidifier-off alert
alias: "Alert when bedroom humidifier turns off at night"
triggers:
- trigger: humidifier.turned_off
target:
entity_id: humidifier.bedroom
options:
behavior: any
for: "00:00:00"
conditions:
- condition: time
after: "22:00:00"
before: "07:00:00"
actions:
- action: notify.mobile_app_phone
data:
message: "Bedroom humidifier turned off."
Automation: turn off the fan when the last humidifier stops
When all humidifiers in the house turn off, turn off the ventilation fan as well, since there is nothing left to support.
- Trigger: Humidifier turned off
- Target: All humidifiers (by label)
- Trigger when: All
- For at least: 00:00:00
- Action: Fan: Turn off
YAML example for turning off the fan when all humidifiers stop
alias: "Turn off fan when all humidifiers off"
triggers:
- trigger: humidifier.turned_off
target:
label_id: all_humidifiers
options:
behavior: last
for: "00:00:00"
actions:
- action: fan.turn_off
target:
entity_id: fan.ventilation
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:
-
Humidifier turned on: Triggers after one or more humidifiers turn on.
-
Humidifier started humidifying: Triggers after one or more humidifiers start actively humidifying.
-
Humidifier started drying: Triggers after one or more humidifiers start actively drying (dehumidifying).