# \[APP\]\[Pro\] Google Services - App for Translate and new Text-to-Speech for any device with url input **URL:** \ **Category:** Apps\ **Tags:** app, tools\ **Created:** [February 25, 2021, 10:50am UTC](https://community.homey.app/t/app-pro-google-services-app-for-translate-and-new-text-to-speech-for-any-device-with-url-input/43257 "2021-02-25T10:50:00Z")\ **Posts on this page:** 1\ **Showing post:** 143
**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:** [March 17, 2021, 7:39pm UTC](https://community.homey.app/t/app-pro-google-services-app-for-translate-and-new-text-to-speech-for-any-device-with-url-input/43257/143 "2021-03-17T19:39:11Z")
> [@Martijn\_Hoogenbosch](#): > > question; do I understand it correctly every text string needs a own device? No, you don’t need another device: You get an unique URL for each Unique speech (including text, pitch, speed, pauses, etc). And those URLs are SHARED between TTS devices if there the exact same speech with the exact same settings. So creating a device for each text would be pointless. You create a device for each output-device you have, each speaker you want to speak alone oon, and/or create a device for which the trigger will send the url to all speakers. Because for each TTS device you link it to a speaker/device through a trigger and a action card sending the url. Ofc you could use it differently when using [H.O.O.P. (Hope) - Homey Object Oriented Programming](https://community.homey.app/t/h-o-o-p-hope-homey-object-oriented-programming/43709) --- _[View the full topic](https://community.homey.app/t/app-pro-google-services-app-for-translate-and-new-text-to-speech-for-any-device-with-url-input/43257)._