action:
- service: notify.mobile_app_pixel_xl
data:
title: "Nobody is home right now, turn off the alarm"
message: TTS
data:
channel: alarm_stream
priority: high
ttl: 0
I’m using those settings to ensure it’s played even if the phone is in do-not-disturb. Other settings are available in the docs dschido linked.
I even found the HACS/Browser-mod way too and had that working also.
@Tinkerer - could I use your suggested way to send the message to a group rather than one target?
Sure… there’s no magic here, just building blocks.
I just tried via a group and nothing happened, it appears ‘platform: group’ method only works for actual mobile app notifications and not TTS.
I presume I just have to add multiple service entries under action rather than just send the TTS to a group.
did the notification arrive on the device? check notification history in app configuration. As long as the notification received with message: TTS
it will process it as TTS
Strange, literally as I got to the end of reading your post, my phone played back 4 notifications in a row.
I just checked the notification-history in the app-config, and I see the notifications each arriving at different times, however they didn’t play until later and in sequence.
did you have ttl
and priority
added to the notifications when you sent them? normally delays are related to doze mode so we have to bypass it
That happens to me too.
@dshokouhi on the same topic but slightly different, when is the breaking change due on command notifications?
I read about it in GitHub.
For that one were probably going to talk about it first in a blog post to give a heads up and then do the switch in the next release after that.
Group TTS functionality works
Sorry to unbury an old threat but what is the current implementation of this feature?
Thank you
Install the official app and it does it.
Thanks.
The tts part only seems to be valid for android. Maybe I should have asked more specificly any way to play tts over the mobile app on ios? Besides uploading a specific wav file.
For me it’s not working. TTS on phone says “please set a title so that text can be processed into speech”.
The format changed, check the companion app docs for the updated format.
That’s it! Thank you! It works now.
Are we out of luck on ios for TTS notifications? I only see instructions for Android
It’d be magic if it worked on iOS.
I was having the exact same problem. Notifications was being sent, but I only heard the voice message when I grab the phone from the table. Even without unlocking it. As soon as the screen shows something, the phone start talking… with the missed previous notifications.
Oooops… I RE-EDIT MY MESSAGE… I wrote here what I thought was the solution, but after most tests, I think dshokouhi is right. What have made the notifications work is adding, specially the ‘ttl’ line to the service. On december 2023 the sintax that work for me is:
- service: notify.mobile_app_<here-your-mobile>
data:
message: "TTS"
data:
ttl: 0
priority: high
media_stream: alarm_stream
tts_text: "Test text"
As said here in the docs:
" For Android, notifications will appear immediately in most cases. However, in some cases (such as phone being stationary or when screen has been turned off for prolonged period of time), default notifications will not ring the phone until screen is turned on. To override that behavior, set priority: high
and ttl: 0
."