Speaker Client that Calls an API

[Mitch G]

I tried searching for an answer to no avail so I apologize if this has been asked and answered before, but I have an API in my home network that can be used to do TTS over speakers in my house.
I would like to use this API as a speaker client in HS3 (Zee S2).

Is this possible? If so, any pointers to documentation?

Thanks,


Mitch

[alexbk66]

Did you find a solution?

[mrhappy]

The only way I know how to do this is to create a plugin and register it as a speech proxy, in your plugin then you can do whatever you wish with the spoken text and send it elsewhere. It is how the Sonos/Chromecast plugin does it, in early HS3 days I created a plugin that would be a speaker client itself so there was no reliance on the HS speaker application - it worked but not a great deal of point to it.

[Pete]

Here running a W7 VB and Speaker dot exe (5 of them) and SAPI speech fonts on the same box as Homeseer 3 Pro is running on.



Zee2 HS3 lite also uses these sapi speaker fonts.

Well that and also running HSTouch on Intel based embedded Windows with SAPI and speaker running on these tabletops. Different english speech fonts (and multiple language speech fonts).

Also have squeeze players that will proxy the speech from HS (lite or pro) but do not do this. Personally prefer different SAPI fonts versus proxying one speech font from HS3. That is me though.

Also starting to proxy TTS to Alexa devices these days. Recently combined the audio from an Amazon dot with the HS3 SAPI audio to Russound. Works great.

Use it now for Amazon Weather and news and status TTS for alarm features BUT I do not have dependencies on the Amazon for automation (if that makes sense?)

[alexbk66]

The only way I know how to do this is to create a plugin and register it as a speech proxy. It is how the Sonos/Chromecast plugin does it

Not really, Chromcast plugin uses the same API as HS Speaker app - HomeSeerAPI.ISpeechAPI. It's not documented, but you can see it in VS. Using this API when plugin starts - your device automatically appears in speaker client list. And you can send different TTS to different devices using this list. Which you can't do using SpeakerProxy functions.

[alexbk66]

running a W7 VB and Speaker dot exe and SAPI speech fonts... (if that makes sense?)

Not really Pete, can you please elaborate a bit?

[Pete]

I am wanting to keep multiple sapi voice font use here so each of the instances runs a separate speaker dot exe application with different sapi voice fonts.

Homeseer's touch application copies the text to speech file to the client and the client plays it back. It is not SAPI. (except for the Android client?).

Different TTS is just that but it is the same voice font.