But for sure all your chance is the official RulesAPI and Routine builder.
You can try to build a SmartApp as well, outside of the IDEâs platform, but for that you need to host it by yourself and need to have access to Amazonâs Poly as the source of the text-to-speech.
What the Routines offer with TTS and what the API can actually do are very different. Unfortunately the public API doesnât document/offer the required actions.
Thanks for the reply. It is really too bad. Iâm going to miss hearing âthe mail has arrivedâ and a myriad of other cool things I have working with this.
I wish I didnât have so many devices, rules, and automations. I couldnât imagine the time it would take to migrate to another platform.
If you have echo devices, itâs quite easy to set up announcements for them using echo routines (not ST routines). I have one friend who mostly uses Google home, but does have two echo dots used just for voice announcements.
We switched over to Google about a year ago, Amazon got ridiculous with its âby the wayâ stuff after every interaction⌠and then something on their end broke after working for eons it couldnât complete simple commands like âturn off x lightâ half the time.
We kept one Amazon device but I removed its access to ST⌠I did try using their voice for automations but I have to say Big Talker by far has the best , most pleasant voices to choose from. Echo is cold.
In Home Assistant if you use it with the Nabu Casa subscription, the Google text-to-voice languages are included and it can do that to any speaker what it supports. I know it works with Google Home devices and Sonos speakers as well.
I donât use it too much, but I believe you can add other text-to-voice services as well.
All these services what SmartThings cuts will be a huge pile of money not spent. Plus the servers what they spare running the Groovy stuffâŚ
You could also call the /services/tts endpoint which returns a URL that points to an MP3 file if your device commands supports passing an MP3 file directly to it. Or for that matter, you could generate a TTS or whatever sound file you wanted and store it somewhere then pass the stored file directly to your command.
Big Talker 2 functionality eventually died for me (November). I noticed that the Smartthings app now has a âPlay message on speakerâ option in Routines.
Go to Automation tab and hit the â+â button to
âCreate Routineâ.
In the If condition, create whatever trigger you want, like a motion sensor movement detected.
In the Then section, add a new action and select âNotify Someoneâ.
The third option is âSpeak message to speakerâ.
Enter the message you want to speak.
Select the Audio Device to play it on: I have been using a Sonos One (2nd gen) with Big Talker and it works here. My Google speakers donât show up,so theyâre supported yet.
Select appropriate Language and Male/Female voice.
Save and give the routine a name.
I donât know of a way to use dynamic parameters in the message field like Big Talker uses %devicename% so you can just use one routine for multiple devices. So for now I had to create a routine for each sensor, and for my door contact sensors I had to create two routines for each door (open and close) - ugh. But at least I still have my voice announcements.