Moisture detected

The Moisture detected trigger fires when one or more moisture binary sensors start detecting water. Use it with leak sensors under a sink, behind a dishwasher, next to a washing machine, or in a basement to react the moment water is present.

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. From the search box, search for and select Moisture detected.
  5. Select Add target (see Targets) and pick the leak sensor you want to watch. You can also select an area, a floor, a device, or a label.
  6. Under Trigger when (see Behavior), pick Each, First, or All to control how the trigger behaves when multiple sensors are targeted.
  7. Under For at least, you can set how long the sensor must keep detecting moisture before the trigger fires. Leave it at zero to fire immediately.
  8. Select Save.

Options in the UI

Trigger when (Optional)

When multiple moisture sensors are targeted, controls when the trigger fires:

  • Each (default): fires every time any targeted sensor starts detecting moisture.
  • First: fires only when the first sensor starts detecting moisture.
  • All: fires only after every targeted sensor starts detecting moisture.
For at least (Optional)

How long the sensor or sensors must keep detecting moisture before the trigger fires. The default is 0 (fires immediately).

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 moisture.detected. 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: moisture.detected
target:
  entity_id: binary_sensor.kitchen_sink_leak

This fires when the leak sensor under the kitchen sink detects water.

Options in YAML

behavior string

When multiple moisture sensors are targeted, controls when the trigger fires:

  • any (Each in the UI, default): fires every time any targeted sensor starts detecting moisture.
  • first (First in the UI): fires only when the first sensor starts detecting moisture.
  • last (All in the UI): fires only after every targeted sensor starts detecting moisture.
for string

How long the sensor or sensors must keep detecting moisture before the trigger fires. Accepts a duration string in HH:MM:SS format or a time period mapping in hours, minutes and seconds.

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

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

  • This trigger works with binary sensors that have the moisture device class, such as water leak sensors.
  • A sensor in the unknown or unavailable state does not count as detecting moisture.
  • To react when a leak clears instead, use Moisture cleared.
  • For percentage-based moisture sensors (such as soil moisture probes), use Moisture content changed or Moisture content crossed threshold.

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: shut off the water main when a leak is detected

When any leak sensor in the house detects water, close the smart water shutoff valve and send a critical notification.

  • Trigger: Moisture detected
    • Target: All leak sensors (by label)
    • Trigger when: Each
  • Action 1: Close valve
    • Target: Water main valve
  • Action 2: Send a notification message
    • Target: My Device (notify.my_device)
YAML example for a leak shutoff automation
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Shut off water on leak detection"
triggers:
  - trigger: moisture.detected
    target:
      label_id: leak_sensors
actions:
  - action: valve.close_valve
    target:
      entity_id: valve.water_main
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      message: "Leak detected! The water main has been closed."

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: