Budget around 60 minutes. This lesson builds the spine for the whole module: two announcement tiers and a silence switch that every one of the next 15 lessons will build on. From here on I'll shorten Home Assistant to HA and Music Assistant to MA.

A Real-Life Problem: A Flood Alert During Movie Night

A flood sensor in the bathroom detects water. The phone is sitting in another room, on silent. The push notification waits unread for 40 minutes until the movie ends. In that time, water spreads across the floor. The opposite problem: HA "informs" you out loud through the living room speaker about every front door opening, every piece of mail, and every finished laundry load, until after a week you switch TTS off entirely, including for things that actually matter.

The fix for both problems is the same thing: separating priorities at the architecture level, not relying on good intentions inside every individual automation.

Two Announcement Tiers

This distinction isn't cosmetic: a critical announcement carries different permissions (it can override silence mode from Lesson 12), a different volume, and repeats if nobody reacts. A home announcement never overrides silence: news that the laundry finished can wait until morning.

The Module's Foundation Helpers

input_boolean:
  house_silence:
    name: "House silence"
    icon: mdi:volume-mute
    initial: false
  multimedia_automation_enabled:
    name: "Multimedia automation enabled"
    icon: mdi:cast-connected
    initial: true

input_number:
  announcement_volume_home:
    name: "Volume: home announcement"
    min: 0
    max: 100
    step: 5
    initial: 35
    unit_of_measurement: "%"
  announcement_volume_critical:
    name: "Volume: critical announcement"
    min: 0
    max: 100
    step: 5
    initial: 70
    unit_of_measurement: "%"

input_select:
  announcement_zone:
    name: "Announcement zone"
    options:
      - "Whole house"
      - "Downstairs"
      - "Upstairs"
      - "Kitchen and living room only"
    icon: mdi:map-marker-radius

input_select.announcement_zone lets you quickly limit home announcements to part of the house, for example when a child is asleep upstairs: in Lesson 12 we'll extend this logic with automatic switching based on the time of day.

The Home Announcement Script Skeleton

script:
  home_announcement:
    alias: "Home announcement"
    icon: mdi:bullhorn-outline
    mode: queued
    max: 5
    fields:
      message:
        description: "The message to speak"
        example: "Laundry is done"
    sequence:
      - condition: state
        entity_id: input_boolean.house_silence
        state: "off"
      - condition: state
        entity_id: input_boolean.multimedia_automation_enabled
        state: "on"
      # full TTS logic, volume snapshot, and speaker grouping
      # gets built out in Lessons 3, 5, and 6

mode: queued with a max: 5 limit makes sure several announcements triggered close together play one after another, instead of stacking on top of each other: without this, two automations firing in the same second would try to speak through the same speaker at once. This is deliberately a skeleton: we'll build the full, working version with a real TTS call in Lesson 5, after Lessons 2 through 4 introduce the media_player entity, Music Assistant, and the speakers themselves.

What's Worth Automating

What Not to Force

A Map of the Module

Lessons 2 through 4 are the technical foundation: the media_player entity, Music Assistant, and specific speaker brands. Lessons 5 through 8 are announcements: TTS, taking a snapshot and restoring music after an announcement, the tablet as a communicator, and the TV as an information hub. Lessons 9 through 12 are applications: multimedia notifications, home announcements (doorbell, gate, packages), multimedia scenes, and silence mode. Lessons 13 and 14 cover control without a phone and technical alerts as an audio layer. Lessons 15 and 16 close the module with a dashboard and a mini project.

The Multimedia Hardware Landscape: What Actually Exists on the Market

Before you go further, it's worth seeing the full map of options, because in this module you'll be choosing between genuinely different approaches, not a single correct standard. The market splits roughly into four groups of hardware.

You don't have to pick one approach for the whole house. A typical, mature setup mixes several: Sonos in the living room because you already own it, a cheap ESPHome speaker in the garage as an announcement point, and Music Assistant as the layer tying everything into one library and one set of controls.

Multimedia Ecosystems: Closed Versus Open

This module deliberately shows all three approaches, because few installations are fully uniform: a typical home combines one closed ecosystem (say, Sonos in the living room) with cheaper, open solutions elsewhere (a DIY ESPHome speaker in the garage or laundry room).

A Starter Budget for a Multimedia System: From Zero to a First Announcement

The Role of pyscript and AppDaemon in More Complex Multimedia Logic

Standard Home Assistant automations, built on triggers and conditions, are entirely sufficient for most scenarios in this module, but more complex logic, like dynamically matching an announcement's volume to background noise measured by a microphone, goes beyond what the standard automation editor comfortably handles. In cases like that, pyscript (which lets you write automation logic in Python) offers more flexibility than YAML, though it comes with an extra learning curve that goes beyond this course's basic scope.

A/B Testing Different Approaches to Home Announcements

Before you settle on a final format for your voice announcements (length, tone, level of detail), it's worth testing different variants on yourself and your household for a week or two: a short, factual announcement versus a fuller sentence with context. What seems optimal in theory often turns out, in practice, to be either too long (household members stop listening before it finishes) or too terse (missing the context of exactly what happened).

The House's Sound Profile: Why It's Worth Designing Deliberately

Before you start configuring individual announcements, it's worth designing an overall sound profile for the whole house: what voice, what tone, and what baseline volume announcements should carry at different times of day. A house where every automation has its own randomly chosen voice and volume feels chaotic, while a consistent, deliberate sound profile, applied consistently across the rest of this module's lessons, creates the impression of one coherent system, not a pile of independent gadgets.

The Order of Decisions Before Your First Multimedia Purchase

Common Cognitive Mistakes When Planning a Multimedia System

How to Test This Lesson

Key Takeaways

What's Next

Next lesson: The media_player Entity: TV, Speaker, Soundbar, Receiver, Tablet, and Player. You'll learn the entity structure the whole module is built on.