Fan turned off

The Fan turned off trigger is useful when you want to react after a fan stops. Use it to end a related routine, restore another device to its normal state, or send a reminder if a fan shuts down when you did not expect it to.

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:

1. Go to Settings > Automations & scenes.
2. Open an existing automation, or select Create automation > Create new automation.
3. In the When section, select Add trigger.
4. Select what you want to monitor. Under By target (see Targets), pick the fan you want to monitor. You can also select an area, a floor, a device, or a label.
5. From the triggers shown for that target, select Fan turned off.
6. Under Trigger when (see Behavior), pick Each, First, or All.
7. Under For at least, set how long the fan must stay off before the trigger fires.
8. Select Save.

Options in the UI

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 fan.turned_off. A basic example looks like this:

trigger: fan.turned_off
target:
  entity_id: fan.kitchen
options:
  behavior: any
  for: "00:10:00"

This fires when fan.kitchen has been off for 10 minutes.

Options in YAML

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 fan entity behind that target.

• Entity: one specific fan entity, such as fan.living_room.
• Device: every fan entity that belongs to a device.
• Area: every fan entity in a room or area.
• Floor: every fan entity on a floor.
• Label: every fan 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 (any in 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 (first in 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 (last in 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

• A fan in the unknown or unavailable state does not count as turned off.
• If the fan turns on again before the For at least time finishes, the timer resets.
• To react when a fan starts instead, use Fan turned on.

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.

Automation: switch the hallway light back to normal after the fan stops

You might raise the hallway light while the fan is running to make a late-night bathroom trip easier. When the fan stops, this automation restores the light to its usual setting.

• Trigger: Fan turned off
• Target: Bathroom fan
• Trigger when: Each
• For at least: 00:00:00
• Action: Turn on light

alias: "Restore hallway light after bathroom fan"
triggers:
  - trigger: fan.turned_off
    target:
      entity_id: fan.bathroom
    options:
      behavior: any
      for: "00:00:00"
actions:
  - action: light.turn_on
    target:
      entity_id: light.hallway
    data:
      brightness_pct: 30

Automation: notify if the nursery fan stops overnight

If you rely on airflow for comfort at night, a notification can tell you when the nursery fan has stopped for a few minutes.

• Trigger: Fan turned off
• Target: Nursery fan
• Trigger when: Each
• For at least: 00:05:00
• Action: Send a notification via mobile_app_phone

alias: "Nursery fan stopped overnight"
triggers:
  - trigger: fan.turned_off
    target:
      entity_id: fan.nursery
    options:
      behavior: any
      for: "00:05:00"
actions:
  - action: notify.mobile_app_phone
    data:
      message: "The nursery fan has been off for 5 minutes."

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.

Related triggers

These triggers work well alongside this one:

• Fan turned on: Triggers after one or more fans turn on.