I was playing with the custom spoken message options yesterday and I noticed that there was a significant delay when I executed the trigger and when I heard the text-to-speech coming out of the speakers. When I say significant, it was several minutes. Is it usually like this?
Now, for those of you with good memories, I realize the irony of the above statement given my post last fall…
Hmm…maybe it is an issue with the @obycode version of it. I’ll follow-up with them to see, although I thought theirs was based on the Sonos version. I recall there being an issue in the Sonos code somewhere that was preventing the their app from working properly, so they had to rework the Sonos code.
The way oby code does it is weird. Not sure if I have ever fully understood how it works. It essentially downloads a file to your PC every time it
Parses text-to-speech commands. The speed of this might be dependent on the health of the Obycode servers.
Agreed. Maybe in the next version (which I’ve been working on for a while off and on) should just scrap the Sonos SmartApps and just supply its own. capability.speechSynthesis has the speak method that just passes a string. I’ll support that instead of the custom methods the Sonos uses.