Remote turned off

The Remote turned off trigger fires after a remote 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 when a media remote, IR blaster, or RF bridge stops being active, for example to clean up a related scene or shut down other devices.

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 remote 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 Remote turned off.
6. Under Trigger when (see Behavior), pick Each, First, or All.
7. Under For at least, set how long the remote must stay off before the trigger fires. Leave it at zero to fire immediately.
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, Remote turned off is referred to as remote.turned_off. A basic example looks like this:

trigger: remote.turned_off
target:
  entity_id: remote.living_room

This fires every time remote.living_room transitions to the off state.

Options in YAML

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

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

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

• Remotes that are unavailable (unavailable) or have an unknown state (unknown) are skipped and do not count as turning off. The trigger only fires on a transition from a known, valid state to off.
• If the remote turns on again before the For at least time finishes, the timer resets.
• To react when a remote starts instead, use Remote 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: restore the lights when the living room remote turns off

When you turn the living room remote off, restore the lights to their normal evening level.

• Trigger: Remote turned off
  • Target: Living room remote
• Action: Turn on light
  • Target: Living room lights

alias: "Restore lights when living room remote turns off"
triggers:
  - trigger: remote.turned_off
    target:
      entity_id: remote.living_room
actions:
  - action: light.turn_on
    target:
      entity_id: light.living_room
    data:
      brightness_pct: 80

Automation: send a notification once every remote in the house is off

When the last remote in the house has been off for five minutes, send a phone notification so you know the entertainment area is fully shut down.

• Trigger: Remote turned off
  • Target: All remotes (by label)
  • Trigger when: All
  • For at least: 00:05:00
• Action: Send a notification message
  • Target: My Device (notify.my_device)

alias: "Notify when every remote is off"
triggers:
  - trigger: remote.turned_off
    target:
      label_id: all_remotes
    options:
      behavior: all
      for: "00:05:00"
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      message: "All remotes are off."

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:

• Remote turned on: Triggers after one or more remotes turn on.