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 ?
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 and I hope I didn’t miss the concept of 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 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 compatible for SDK3 using the same very trivial principle ?
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.
…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.
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.
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(please note it will get installed as new app and you will have to redo your flows).
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.