pete_c
Guru
@Morgan,
You can if you want add a micro Intel based computer like the Pipo for Microsoft SAPI and aux HS3 windows plugins (remotely). Here use a virtual box to do this.
My custom tabletop touchscreens here in Wintel run HSTouch and MS SAPI and/or OmniTouch Pro touch or in Linux run Squeezeplayer such that automation sounds run through zoned audio, tabletop touch screens (SAPI and GV), GV or Alexa.
Just related to MS SAPI and HS3 speaker dot exe you can run that on any microsoft product and your HS3 instances will talk to the speaker dot exe.
It does introduce another box to your network just related to Microsoft SAPI. (I use Oracle VB or touchscreens here for that).

Using Microsoft SAPI here then have no dependencies on the cloud for TTS. That and do not put dependencies for automation on Amazon Alexa (just sound TT / VR candy). IE: if I unplug cloud based anything my home automation continues to work just fine.
Relating to the new use of WiFi switches / cloud stuff here rewriting the firmware on these devices allows me to keep using the internal network. (MQTT). Absolutely will never program any of these devices with phones or tablets on the internet. It's an easy button solution for those folks tethered to their smart phones and many yut today.
Noticed the topic has moved to wireless thermostats with cloud connections. Here very legacy and do not touch my Omnistat thermostat which is still serially connected to the OmniPro 2 panel. That and I do not gaze at my thermostat all day...in fact I rarely look at it or any of the consoles that connect to it.
You can if you want add a micro Intel based computer like the Pipo for Microsoft SAPI and aux HS3 windows plugins (remotely). Here use a virtual box to do this.
My custom tabletop touchscreens here in Wintel run HSTouch and MS SAPI and/or OmniTouch Pro touch or in Linux run Squeezeplayer such that automation sounds run through zoned audio, tabletop touch screens (SAPI and GV), GV or Alexa.
Just related to MS SAPI and HS3 speaker dot exe you can run that on any microsoft product and your HS3 instances will talk to the speaker dot exe.
It does introduce another box to your network just related to Microsoft SAPI. (I use Oracle VB or touchscreens here for that).

Using Microsoft SAPI here then have no dependencies on the cloud for TTS. That and do not put dependencies for automation on Amazon Alexa (just sound TT / VR candy). IE: if I unplug cloud based anything my home automation continues to work just fine.
Relating to the new use of WiFi switches / cloud stuff here rewriting the firmware on these devices allows me to keep using the internal network. (MQTT). Absolutely will never program any of these devices with phones or tablets on the internet. It's an easy button solution for those folks tethered to their smart phones and many yut today.
Noticed the topic has moved to wireless thermostats with cloud connections. Here very legacy and do not touch my Omnistat thermostat which is still serially connected to the OmniPro 2 panel. That and I do not gaze at my thermostat all day...in fact I rarely look at it or any of the consoles that connect to it.