Valve closed

The Valve closed trigger fires after a valve 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] transitions to the closed state. Valve entities represent water, gas, or air valves in your home.

Use it to react the moment a valve is closed, whether it was closed manually, by a schedule, through an automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more], or by a voice command. For example, you can create an automation to log when irrigation ends, confirm that a gas valve has been shut off, or chain follow-up actions after a valve closes.

Labs

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:

  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, pick the area your valve is in, such as your garden or utility room. You can also select a device, a specific entity, or a label, as described in Targets.
  5. From the triggers shown for that target, select Valve closed.
  6. Under Trigger when, pick Each, First, or All to control how the trigger behaves when multiple valves are targeted, as described in Behavior.
  7. Under For at least, set how long the valve must stay closed before the trigger fires. Leave it at zero to fire immediately.
  8. Select Save.

Options in the UI

Trigger when

When multiple valves are targeted, controls when the trigger fires:

  • Each (default) fires every time any targeted valve closes.
  • First fires only when the first of a group closes.
  • All fires only after every targeted valve is closed.
For at least

How long the valve must stay closed before the trigger fires. Default is 0 (fires immediately). Useful to ignore brief, momentary closures.

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

TriggerA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more]
trigger: valve.closed
target:
  entity_id: valve.garden_irrigation

This fires every time valve.garden_irrigation transitions to the Closed state.

Options in YAML

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

behavior string

When multiple valves are targeted, controls when the trigger fires:

  • any: fires every time any targeted valve closes.
  • first: fires only when the first valve in the group closes.
  • last: fires only after every targeted valve is closed.
for string

How long the valve must stay closed before the trigger fires. Accepts a duration string in HH:MM:SS format. For example, 00:00:10 fires only after the valve has stayed closed for 10 seconds, which helps ignore brief or accidental closures.

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

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

  • The trigger fires when the valve reaches the Closed state. It does not fire during the transitional Closing state while the valve is still moving. You can check the available states in The state of a valve entity.
  • Valves that report position (0 to 100%) are considered closed only when their position reaches exactly 0.
  • Use the For at least option to avoid false alarms from brief or accidental closures, such as a momentary sensor glitch that causes a valve to flicker to closed and back.
  • This trigger works with any valve entity in Home Assistant, including water, gas, and air valves from integrations such as MQTT, Z-Wave, Zigbee, and ESPHome.
  • You can use this trigger to track your water consumption. Create an automation that records the elapsed time since it opened (using a helper or template sensor) and build a daily watering log when a valve closes. Awareness of actual usage is the first step towards reducing it.
  • Use this trigger to confirm gas valves are safely shut off. Create an automation that sends a confirmation notification when a gas valve closes, giving you peace of mind and a clear audit trail that no gas is flowing when the system is idle.

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.

Tip

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: Log total watering time and estimate water used

A water-awareness automation that calculates how long the irrigation valve was open each time it closes, logs the result, and estimates the volume of water used. Over time, this record helps you identify patterns, spot waste, and set more efficient watering schedules.

  • Trigger: Valve closed
    • Target: valve.garden_irrigation
  • Action: Define variables (configured in YAML editor only)
  • Action: Activity: log activity
  • Action: Send a notification message
    • Target: My Device (notify.my_device)
YAML example for logging total watering time and estimated water use
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Log watering time and estimated water use"
triggers:
  - trigger: valve.closed
    target:
      entity_id: valve.garden_irrigation
actions:
  - variables:
      duration_min: >
        {{
          (
            (trigger.to_state.last_changed
            - trigger.from_state.last_changed).total_seconds() / 60
          ) | round(1)
        }} 
      liters_used: >
        {{ (duration_min * 12) | round(0) }}
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      title: "🌿 Irrigation finished"
      message: >
        Valve closed after {{ duration_min }} min.
        Estimated water used: {{ liters_used }} L.
        Consider adjusting the schedule if the garden looks saturated.
  - action: logbook.log
    data:
      name: "Irrigation"
      message: "Valve open for {{ duration_min }} min — ~{{ liters_used }} L used."
      entity_id: valve.garden_irrigation

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.

Tip

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: