Humidifier is off

The Humidifier is off 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 off. Use it to prevent automations from running actions that only make sense on a powered-on device, or to send a reminder when a humidifier that should be running has been left off.

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 off, or demand that all of them are.

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 off 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 off.
6. Under Condition passes if (see Behavior), pick Any or All to control how the check behaves when multiple humidifiers are targeted.
7. Under For at least, set how long the humidifier must have been off before the condition passes. Leave it at zero to pass immediately.
8. Select Save.

Options in the UI

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 off is referred to as humidifier.is_off. A basic example looks like this:

condition: humidifier.is_off
target:
  entity_id: humidifier.bedroom

This passes when the bedroom humidifier is currently off.

Options in YAML

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

• Humidifiers that are unavailable (unavailable) or have an unknown state (unknown) do not count as off. 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 on instead, use Humidifier is on.

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.

Automation: send a bedtime reminder if the humidifier is still off

At 22:30 on weeknights, check whether the bedroom humidifier has been left off. If so, send a reminder so you can switch it on before you sleep.

• Trigger: Time: 22:30
• Condition: Day of the week is Monday to Friday
• Condition: Humidifier is off
• Target: Bedroom humidifier
• Condition passes if: Any
• Action: Notify mobile app

alias: "Bedtime reminder if humidifier is off"
triggers:
  - trigger: time
    at: "22:30:00"
conditions:
  - condition: time
    weekday:
      - mon
      - tue
      - wed
      - thu
      - fri
  - condition: humidifier.is_off
    target:
      entity_id: humidifier.bedroom
    options:
      behavior: any
actions:
  - action: notify.mobile_app_phone
    data:
      message: >
        The bedroom humidifier is off.
        Switch it on before you sleep.

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.

Related conditions

These conditions work well alongside this one:

• Humidifier is on: Tests if one or more humidifiers are on.

• Humidifier is humidifying: Tests if one or more humidifiers are humidifying.

• Humidifier is drying: Tests if one or more humidifiers are drying.