Media player muted
The Media player muted trigger fires when a media player becomes muted. Use it when you want Home Assistant to react when someone silences a TV, speaker, or receiver.
Use Media player muted to adjust nearby lighting for quiet listening, pause another routine that depends on audio, or send a notification when a shared media player is muted.
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 Media player muted in an automation:
- Go to Settings > Automations & scenes.
- Open an existing automation, or select Create automation > Create new automation.
- In the When section, select Add trigger.
- Select what you want to monitor. Under By target (see Targets), pick the media player you want to watch. You can also select an area, a floor, a device, or a label.
- From the triggers shown for that target, select Media player muted.
- Under Trigger when (see Behavior), choose how multiple targeted media players should behave. The default is Each.
- Under For at least, enter how long the media player must stay muted before the trigger fires. The default is
0. - Select Save.
Options in the UI
When multiple media players are targeted, controls how the trigger fires:
- Each: Fires every time any targeted media player is muted (default).
- First: Fires when the first targeted media player is muted.
- All: Fires when every targeted media player is muted.
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, this trigger is referred to as media_player.muted. A basic example looks like this:
trigger: media_player.muted
target:
entity_id: media_player.office_speaker
This fires when the office speaker becomes muted.
To wait until all targeted media players have stayed muted for 2 minutes:
trigger: media_player.muted
target:
area_id: living_room
options:
behavior: last
for: "00:02:00"
Options in YAML
When multiple media players are targeted, controls how the trigger fires:
-
any(Each in the UI, default): fires every time any targeted media player is muted. -
first(First in the UI): fires when the first targeted media player is muted. -
last(All in the UI): fires when every targeted media player is muted.
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 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 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 (
anyin 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 (
firstin 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 (
lastin 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 when the media player reports that it is muted. If the integration does not expose mute state changes, this trigger will not fire.
- Media players that are
unavailableorunknowndo not count as muted until they report a supported state again. - If you want to react when sound returns, use Media player unmuted.
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.
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: turn on a status light when a speaker is muted
When the office speaker is muted during a call, turn on a desk light so the room still has a visual cue.
-
Trigger: Media player muted
- Target: Office speaker
-
Action: Turn on light
- Target: Desk light
YAML example for a mute status light
alias: "Show a mute status light"
triggers:
- trigger: media_player.muted
target:
entity_id: media_player.office_speaker
actions:
- action: light.turn_on
target:
entity_id: light.office_desk
data:
color_name: "red"
brightness_pct: 50
Automation: pause a fan routine when the TV is muted for a while
If the living room TV stays muted for 10 minutes, turn off a noisy fan so the room stays quiet.
-
Trigger: Media player muted
- Target: Living room TV
- For at least: 00:10:00
-
Action: Turn off switch
- Target: Fan plug
YAML example for turning off a fan after the TV is muted
alias: "Turn off the fan when the TV stays muted"
triggers:
- trigger: media_player.muted
target:
entity_id: media_player.living_room_tv
options:
for: "00:10:00"
actions:
- action: switch.turn_off
target:
entity_id: switch.fan_plug
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.
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:
-
Media player unmuted: Triggers after one or more media players are unmuted.
-
Media player volume changed: Triggers after the volume of one or more media players changes.