Media player is muted

The Media player is muted condition passes when the selected media player is muted. Use it when an automation should continue only if sound is currently silenced.

Use Media player is muted to avoid sending spoken announcements over a muted speaker, to change lighting only during quiet listening, or to branch into a different action when a TV is muted.

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 Media player is muted 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 media player you want to evaluate. You can also select an area, a floor, a device, or a label.
  5. From the conditions shown for that target, select Media player is muted.
  6. Under Condition passes if (see Behavior), choose how multiple targeted media players should behave. The default is Any.
  7. Under For at least, enter how long the media player must stay muted before the condition passes. The default is 0.
  8. Select Save.

Options in the UI

Condition passes if

When multiple media players are targeted, controls how results combine:

  • Any: Passes if at least one targeted media player is muted (default).
  • All: Passes only when every targeted media player is muted.
For at least

How long the media player must stay muted before the condition passes. The 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, refer to this condition as media_player.is_muted. 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: media_player.is_muted
target:
  entity_id: media_player.office_speaker

This passes when the office speaker is muted.

To require all targeted media players to stay muted for 5 minutes:

ConditionConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more]
condition: media_player.is_muted
target:
  area_id: upstairs
options:
  behavior: all
  for: "00:05:00"

Options in YAML

behavior string

When multiple media players are targeted, controls how results combine:

  • any (Any in the UI, default): passes if at least one targeted media player is muted.
  • all (All in the UI): passes only when every targeted media player is muted.
for string

How long the media player must stay muted before the condition passes. 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 media_player entity behind that target.

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

  • This condition depends on the media player reporting its mute state.
  • Media players that are unavailable or unknown are skipped for Any and fail for All.
  • If you want the opposite test, use Media player is not muted.

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: send a text alert only when the TV is muted

When the doorbell rings, send a mobile notification only if the living room TV is muted.

  • Trigger: Doorbell pressed
  • Condition: Media player is muted
    • Target: Living room TV
  • Action: Send a notification message
    • Target: My Device (notify.my_device)
YAML example for a notification that checks whether the TV is muted
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Notify me when the doorbell rings and the TV is muted"
triggers:
  - trigger: state
    entity_id: binary_sensor.front_doorbell
    to: "on"
conditions:
  - condition: media_player.is_muted
    target:
      entity_id: media_player.living_room_tv
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      message: >
        Someone is at the front door.

Automation: set a quiet scene only when every bedroom speaker is muted

At bedtime, turn off a reading light only if all bedroom speakers are already muted.

  • Trigger: Time: 22:30
  • Condition: Media player is muted
    • Target: Bedroom area
    • Condition passes if: All
  • Action: Turn off light
    • Target: Reading light
YAML example for a quiet bedtime scene
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Turn off the reading light when all bedroom speakers are muted"
triggers:
  - trigger: time
    at: "22:30:00"
conditions:
  - condition: media_player.is_muted
    target:
      area_id: bedroom
    options:
      behavior: all
actions:
  - action: light.turn_off
    target:
      entity_id: light.reading_light

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: