Humidifier is on

The Humidifier is on condition passes when 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] is currently switched on. For example, you can adjust the target humidity only when the humidifier is ready to act on the change.

When you target more than one humidifier, the condition’s Condition passes if option controls how the check combines results. You can require any targeted humidifier to be on, or demand that all of them are.

Labs

Requires the Purpose-specific triggers and conditions Labs preview feature. Enable it at Settings > System > Labs.

Using this condition from the user interface

If you prefer building automations visually, Home Assistant walks you through this condition step by step. You pick what to check, tweak a few options, and save. No YAML knowledge required.

To use Humidifier is on in an automation:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation, or select Create automation > Create new automation.
  3. In the And if section, select Add condition.
  4. Select what you want to check. 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.
  5. From the conditions shown for that target, select Humidifier is on.
  6. If you targeted more than one humidifier, an extra option appears: under Condition passes if (see Behavior), pick Any or All to control how the check combines results.
  7. Under For at least, set how long the humidifier must have been on before the condition passes. Leave it at zero to pass immediately.
  8. Select Save.

Options in the UI

Condition passes if (Required)

Only shown when multiple humidifiers are targeted. Controls how results combine. Pick Any to pass if at least one targeted humidifier is on, or All to pass only when every targeted humidifier is on. Default is Any.

For at least (Required)

How long the humidifier must have been continuously on before the condition passes. Useful to confirm the device has been running for a meaningful amount of time before taking action. Default is 0 (passes immediately).

Using this condition 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 is on is referred to as humidifier.is_on. A basic example looks like this:

ConditionConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more]
condition: humidifier.is_on
target:
  entity_id: humidifier.bedroom

This passes when the bedroom humidifier is currently on.

Options in YAML

behavior string Required, default: any

Only relevant when multiple humidifiers are targeted. Controls how results combine. Use any to pass if at least one targeted humidifier is on, or all to pass only when every targeted humidifier is on.

for string Required, default: 00:00:00

How long the humidifier must have been continuously on before the condition passes. Useful to confirm the device has been running for a meaningful amount of time before taking action. Accepts a duration string in HH:MM:SS format.

Targets of the condition

This condition requires a target. The target is the object that Home Assistant will check. You can point the condition at 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, and Home Assistant will evaluate 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 condition. For example, you can add a specific entity and an area as targets in the same condition to check 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 Condition passes if option controls how the results combine:

  • Any (default): the condition passes if at least one of the targeted entities matches. For example, if you check three smoke sensors and only one of them detects smoke, the condition still passes. This is useful for questions like “is there smoke anywhere in the house?”
  • All: the condition passes only when every targeted entity matches. For example, if you check the same three smoke sensors, the condition passes only once all three report cleared. This is useful for “is the entire house safe now?” checks, so your automation does not send an all-clear while one room still has a reading.

Good to know

  • Being “on” does not mean the humidifier is actively running. A device that is on may idle once it reaches its target humidity and only resume when the air dries out. To check for an active humidification cycle, use Humidifier is humidifying.
  • Humidifiers that are unavailable (unavailable) or have an unknown state (unknown) do not count as on. With Any behavior, they are skipped. With All behavior, the condition fails if every targeted humidifier is unavailable.
  • To gate an automation on the humidifier being off instead, use Humidifier is off.

Try it yourself

Ready to test this? Go to Settings > Automations & scenes, open an automation, and add this condition. Trigger the automation with and without the condition met, and watch whether it continues or stops.

More examples

Real scenarios where this condition gates an automation. 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: adjust target humidity only when the humidifier is on

At 22:00, lower the bedroom humidity target for sleeping, but only if the humidifier is already on. Skip the action entirely if the device has been switched off.

  • Trigger: Time: 22:00
  • Condition: Humidifier is on
  • Target: Bedroom humidifier
  • Condition passes if: Any
  • Action: Humidifier: Set humidity
YAML example for a gated humidity adjustment
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Lower humidity at night if humidifier is on"
triggers:
  - trigger: time
    at: "22:00:00"
conditions:
  - condition: humidifier.is_on
    target:
      entity_id: humidifier.bedroom
    options:
      behavior: any
actions:
  - action: humidifier.set_humidity
    target:
      entity_id: humidifier.bedroom
    data:
      humidity: 45

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the condition 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 conditions or suggest the right one when you describe what you want in plain language.

Related conditions

These conditions work well alongside this one: