Double TTS message?

All of my TTS messages are being doubled. Any help much appreciated. Testing details below.

This happens when I trigger TTS from Node Red, or using Developer tools > Actions, YAML Mode:

action: notify.mobile_app_myphone
data:
  message: TTS
  data:
    tts_text: Testing from developer tools
    media_stream: alarm_stream

Alarm stream or not, always doubled.
Happens on two different phones with Companion app.
Companion app is latest, 2025.11.4-full
HA is latest, Core: 2025.11.3, Supervisor: 2025.11.5, OS: 16.3, Frontend: 20251105.1

Thank you for any ideas to fix this.

Yep there has been an issue with TTS with some media players for a while.

Devs don’t appear to care. Their first reaction to the issue below was to recommend depreciating the media player type :angry:

See: SlimProto unusual behaviour when sending TTS Ā· Issue #139887 Ā· home-assistant/core Ā· GitHub

Is this becoming more widespread?

My Fire Tab 10" just started this annoying habit yesterday :frowning:
I think there was a (typically secretive?!) update to the system during the day.

I’m glad I just read this because I was starting to think I’d messed up some automations or something!

Which media players are you using?

Might be time to open a more generic issue.

google home speakers… although I probably should check that it’s not an automation issue in my case because I only noticed it recently on one automation which I have recently moved from YAML to a GUI created one.

Seems i have a similiar issue here. I use my Android tablet with HA companion app, which is also the media player for TTS messages in this case. I configured some TTS notifications, which are played twice.

When i reboot the tablet or the HA server (both fix it temporary), the issue won’t occur for some time.

But sooner or later, without changing anything, it starts to play every message two times.

When that happens, the companions notification log shows also two entries for every message, while the HA log shows just one sent message. I can’t figure out, how to stop that annoying behavior.

I’ve opened an issue:

Feel free to thumb up :+1: the issue rather than adding ā€œme tooā€, unless you have more information to add (e.g. more media player types the issue is present on).

3 Likes

I also have it here twice on all SqueezeLite players

action: media_player.play_media
data:
  announce: true
  extra:
    announce_volume: 0.4
    announce_timeout: 20
  media:
    media_content_id: media-source://tts/cloud?message="Test 1"
    media_content_type: music
    metadata: {}
target:
  entity_id: media_player.picoretts

One can entertain themselves - ā€˜Duran’, ā€˜Everything’, ā€˜Django’, ā€˜The’, ā€˜Talk’, ā€˜Mister’ - all good options.

action: notify.mobile_app_fire_tablet
data:
  message: TTS
  data:
    ttl: 0
    media_stream: alarm_stream
    tts_text: Duran
1 Like

I added a comment to the issue. I am not sure that anything is being done on it. Unsure why this just became a problem late last year and why it is hard to implement a fix. It is making TTS far less useful.

Almost all of the time my TTS messages are doubled, but occasionally I get a pleasant surprise and it is not doubled.

:eight_pointed_black_star: Finally found a fix for my TTS and media command that were repeated, by trial and error.
Two android mobile device had that strange behavior, one of them only started after a Samsung update, making it even harder to pinpoint the origin as the other is a lenovo tablette.
Hopefully not a coincidence as there is no mention in the release notes: Updating Browser-mod to latest 2.7.0 made TTS back to normal and command_media play-pause acting as expected. (was skipping to next song instead, had to go in Deezer - or swipe from top - for instance, in order to stop/pause)

Let’s see if it fixes it for anybody else as well :wink:

Unfortunately I don’t use Browser Mod.

Could be another HACS mod that interacts/listens to media… just guessing here

I’ll try a tts test after starting in safe mode when I get time, but I don’t have anything like that I can think of.

Well, false fix as it only worked a few times on both Android devices :unamused:

The TTS messages on my Amazon Fire Tab 10" just started coming through only ONCE again - not sure, if the issue is resolved completely in my case or if the next update or reboot will revert back to the double messaging again.