# Google text to speech (tts)

**URL:** <https://community.homey.app/t/google-text-to-speech-tts/29770>\
**Category:** Apps\
**Created:** [May 13, 2020, 7:33am UTC](https://community.homey.app/t/google-text-to-speech-tts/29770 "2020-05-13T07:33:28Z")\
**Posts on this page:** 20\
**Page:** 7

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 7, 2022, 4:19pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/122 "2022-11-07T16:19:19Z")

</div>

Yep Peter, I know but I have multiple devices and different playing scenarios (sometimes one devices, sometimes all devices etc.) …I know this might work, but it would require to create… 10 flows in Advanced flows for 5 devices ? and…recreate 100 flows with different conditions while passing Text token ?

Simply this is much more easier :

![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/2/e2e70e0ef2710a56ddd72c25f10935a4ce43b15a.png)  
_(just for illustration)_

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [November 7, 2022, 5:24pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/123 "2022-11-07T17:24:31Z")

</div>

Thats the cloud version peter, not the non-cloud, right?

The non-cloud seems to have an issue with the extention i guess.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [November 7, 2022, 5:27pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/124 "2022-11-07T17:27:36Z")

</div>

It is the non-cloud Arie. I didn’t fill in anything, these flowcards worked right after app install

 ![Screenshot 2022-11-07 at 18-26-39 1.HomeyPro Peter](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/0/40961e55e223c456560954e547ee686a45b25615.png)

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [November 7, 2022, 5:57pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/125 "2022-11-07T17:57:09Z")

</div>

> [@Sharkys](#):
>
> recreate 100 flows with different conditions while passing Text token ?

What?  
I don’t get what you are saying, could you explain?

You only need one flow per device to trigger the url on chromecast.

After that, you need just one speed card per speech.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 7, 2022, 6:37pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/126 "2022-11-07T18:37:23Z")

</div>

Maybe I’m missing here something Just to prevent confusion, we are speaking about OLD Google TTS app - [Cast a text to Google App for Homey | Homey](https://homey.app/en-us/app/com.google.tts/Google-TTS/) and I hope I didn’t miss the concept of [Google Services](https://homey.app/en-gb/app/nl.qluster-it.GoogleServices/Google-Services/) (Arie’s app) . Google TTS app (old one) works in the way, that app itself provide all the Chromecast devices list, and offers on action level to Start saying whatever you want on whatever Chromecast device you can connected to your Homey with variety of languages (22 in total “TTS”), speed and Volume, including option ALL devices (Chromecast Group).

I don’t know how to achieve the same on [Google Services](https://homey.app/en-gb/app/nl.qluster-it.GoogleServices/Google-Services/) the same, simple, way - again speaking multiple devices or just one, different content etc. Eg. how to decide which device actually plays, I must create additional X devices to match Chromecast devices, create adv. flows like Peter posted above but how I send this URL/sound/speech to specific device, via Adv. triggers apps/actions ?

So if I will maybe reformulate my question above - is there a way to get [Google TTS app](https://homey.app/en-us/app/com.google.tts/Google-TTS/) compatible for SDK3 using the same very trivial principle ?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [November 7, 2022, 10:28pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/127 "2022-11-07T22:28:18Z")

</div>

My bad when I misunderstood your questions.  
I (we) are afraid that this topic’s app, **Google TTS** , is probably not going to be updated to SDK3.  
I don’t understand why you want to find a way it can be upgraded, because there’s a perfectly fine alternative.

That’s why I mentioned Arie’s app, **Google Services** , with a flow example of how you can achieve something similar with the free ‘classic’ TTS device _of Arie’s app_.

As a workaround 😜

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 7, 2022, 10:48pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/128 "2022-11-07T22:48:01Z")

</div>

> [@Peter\_Kawa](#):
>
> I don’t understand why you want to find a way it can be upgraded, because there’s a perfectly fine alternative.

…because it still has it’s users, it not dependent on cloud subscription, it is simpler to use and provide much more language options (speaking about TTS). 😉 But thank you for your attempt to help, I appreciate it.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [November 7, 2022, 11:00pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/129 "2022-11-07T23:00:44Z")

</div>

No problem, Sharkys. We don’t agree about a solution then 🙃

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [November 8, 2022, 11:01am UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/130 "2022-11-08T11:01:49Z")

</div>

> [@Sharkys](#):
>
> because it still has it’s users, it not dependent on cloud subscription, it is simpler to use and provide much more language options (speaking about TTS).

Hey @Sharkys , i am fine with rooting it to SDK3, if the developer can be contacted and transfers the App and Sourcecode over to me.  
But as of now i have still not have contact with the developer.

Hey @denniedegroot, could i or another developer take over your app?  
A lott of people depend on it.

---

<div class="post-metadata">

**Author:** ![denniedegroot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/denniedegroot/32/797_2.png) [@denniedegroot](https://community.homey.app/u/denniedegroot)\
**Post date:** [November 8, 2022, 4:22pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/131 "2022-11-08T16:22:54Z")

</div>

I will convert this app to SDKv3 in due time.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 8, 2022, 4:33pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/132 "2022-11-08T16:33:32Z")

</div>

Welcome back after 2 years and thank you 🙂

---

<div class="post-metadata">

**Author:** ![Marcel\_Visser](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_visser/32/66024_2.png) [@Marcel\_Visser](https://community.homey.app/u/Marcel_Visser)\
**Post date:** [November 8, 2022, 9:24pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/133 "2022-11-08T21:24:40Z")

</div>

That’s GREAT!

---

<div class="post-metadata">

**Author:** ![Glenn\_Dijkstra](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/glenn_dijkstra/32/17251_2.png) [@Glenn\_Dijkstra](https://community.homey.app/u/Glenn_Dijkstra)\
**Post date:** [January 27, 2023, 8:07pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/134 "2023-01-27T20:07:18Z")

</div>

Thanks @denniedegroot, love the app!

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [February 8, 2023, 7:17am UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/135 "2023-02-08T07:17:45Z")

</div>

FYI, thanks to the great work of @Martin_Verbeek , Google TTS has been rewritten to the SDK3. If you prefer to use version from Martin, you can go already to the HCS and install it - [Homey Community Store](https://store.homey.community/app/com.verbem.castTTS) _(please note it will get installed as new app and you will have to redo your flows)._

 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/3/a387c5bdc92a0a4a294947fadccb2ef668adacf4.jpeg)

[Original version](https://homey.app/en-us/app/com.google.tts/Google-TTS/) might get updated by Dennie somewhere in the future - [GitHub · Where software is built](https://github.com/denniedegroot/com.google.tts/issues/37and) [SDK3 compliant, fixed some issues, compose setup, new images by dudz40 · Pull Request #38 · denniedegroot/com.google.tts · GitHub](https://github.com/denniedegroot/com.google.tts/pull/38)

Btw by rewrite, Martin also added functionality to avoid sound on muted speakers 😉

As always, consider to Donate to relevant developer, you will find links on relevant page, eg. for Martin - check out [HCS](https://store.homey.community/app/com.verbem.castTTS).

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [February 8, 2023, 7:35am UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/136 "2023-02-08T07:35:57Z")

</div>

Also casting to a nest stereo pair should work now. If you have a stereo pair active, casting to an individual speaker in that pair will not work.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [February 10, 2023, 3:41pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/137 "2023-02-10T15:41:28Z")

</div>

Just got Sonos casting included, is that interresting?

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [February 10, 2023, 4:02pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/138 "2023-02-10T16:02:29Z")

</div>

check it out on HCS version 3.1.0. It is fresh please let me know if any troubles

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [February 10, 2023, 6:50pm UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/139 "2023-02-10T18:50:31Z")

</div>

I will probably migrate to your version on Sunday…I see no other choice anymore 🙂

---

<div class="post-metadata">

**Author:** ![Joka](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Joka](https://community.homey.app/u/Joka)\
**Post date:** [February 11, 2023, 8:36am UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/140 "2023-02-11T08:36:12Z")

</div>

> [@Martin\_Verbeek](#):
>
> Just got Sonos casting included, is that interresting?

Thx, much appreciate! Unfortunately no speech on my Sonos S1 devices?

I can see that the volume is adjusted in the Sonos controller via the app but I get this error:

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/5/e575ac8fddc7228f7e4d436730ff30218bc9fff3.png)

Translation: Playback of googletts.mp3 not possible. Connection [tmpfiles.org](http://tmpfiles.org) was disconnected.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [February 11, 2023, 9:13am UTC](https://community.homey.app/t/google-text-to-speech-tts/29770/141 "2023-02-11T09:13:14Z")

</div>

The app stores the output of tts temporary on a file that should be reachable by the Sonos device. No issue here on S1 devices. Looks like the file cannot be accessed by the Sonos device.

Can you access [/tmp/files - About](https://tmpfiles.org/about) from another device in your network?

[Previous page](https://community.homey.app/t/google-text-to-speech-tts/29770.md?page=6)

[Next page](https://community.homey.app/t/google-text-to-speech-tts/29770.md?page=8)
