Chime TTS Notify Entries

You can create and manage Chime TTS notification profiles in the Chime TTS sidebar panel. The panel writes the profiles to configuration.yaml; direct YAML configuration remains fully supported.

Beta

Panel-based Notification Profiles are currently in beta. Their panel workflow and configuration details may change between releases.

This allows you to create fully customized & reusable notify entries that can be tailored based on the time of day, who is home, or any other use case you can think of.

Configure profiles from the sidebar panel

1. Open Chime TTS from the Home Assistant sidebar.
2. Open the Notification Profiles section.
3. Select Add profile, or expand an existing profile to edit it.
4. Enter a profile name and one or more media-player targets, then choose the chimes, TTS provider, timing, playback, and optional script settings you need.
5. Save the profile. Chime TTS validates the values and writes the resulting notify entry to configuration.yaml.

After saving a profile named announcements, Home Assistant exposes it as notify.announcements. Use that action in automations and scripts, supplying only the message or any values that should override the profile defaults.

The panel is the recommended workflow. You can still add profiles directly in YAML when that better suits your setup.

Example Notify Entries

• An "evening" notify entry limited to play on specific media_players with a softer chime and low volume.

• An "announcement" notify entry for home-wide announcements at full volume with a loud chime.

• A "calendar" notify entry used for reminders for upcoming events, that repeats after 5 minutes.

Why Notify Entries?

Convenience: Configure any/all chime_tts.say parameter values (chime paths, media players, TTS platform, language, voice, etc) once for all your use-cases, and reuse.

Flexibility: Retain the ability to override the defined notify settings across your scripts & automations when needed.

Efficiency: Replace long complicated chime_tts.say action calls with simple, clean and predefined notify action calls.

Go from this...	...to this
action: chime_tts.say data: chime_path: soft offset: -2250 message: Someone's at the door tts_platform: google_translate language: en tld: com.au volume_level: 0.65 cache: true join_players: true unjoin_players: true announce: true target: entity_id: - media_player.kitchen - media_player.living_room - media_player.garage	action: notify.evening data: message: Someone's at the door

---

Notification-profile reference

This generated reference covers the current panel and YAML profile fields.

Field	Description	Default / example
name Name	Required notify service name.	—
entity_id Media players	Required target media player or list of media players.	—
chime_path Start chime	Optional chime before the message.	None
end_chime_path End chime	Optional chime after the message.	None
tts_platform TTS platform, language, voice and TLD	Provider selection and supported provider defaults.	Configuration defaults
offset Timing and TTS tuning	offset, crossfade, final_delay, tts_speed and tts_pitch.	Configuration defaults
playback Playback and audio options	volume_level, audio_conversion, options, announce, fade_audio, cache, join_players and unjoin_players.	false / provider defaults
scripts Playback scripts	pre_script and post_script accept a script entity or YAML with script and data.	Configuration defaults

Defaults, overrides, and restarts

Profiles can define start and end chimes (including Chime Sets), timing, TTS provider, language, voice, TLD, player targets, volume, cache, announcement and fade controls, audio conversion, and pre/post scripts. A value supplied under an action's data overrides the profile default; an omitted value uses the profile default.

action: notify.door_alert
data:
  message: "The front door is open."
  chime_path: Door alerts
  volume_level: 0.7

Adding, removing, or renaming a profile requires a Home Assistant restart because it changes the registered notify.* service. Editing an existing profile without changing its service name can be re-registered from the panel.

alias: Washer complete
trigger:
  - platform: state
    entity_id: sensor.washer_status
    to: complete
action:
  - action: notify.house_announcement
    data:
      message: "The washing machine has finished."
      announce: true
      fade_audio: true

alias: Night security alert
trigger:
  - platform: state
    entity_id: binary_sensor.garage_motion
    to: "on"
action:
  - action: notify.security_alert
    data:
      message: "Motion detected in the garage."
      chime_path: alarm chimes
      tts_platform: edge_tts
      voice: en-US-AriaNeural
      cache: false