HS3 as Service (via scheduler) and Batch file problem...

[shodge]

I searched for this and did not find a entry. I'm running HS3 via the startup scheduler method on Server 2016. All have been well for a couple of years until I am playing with running Alexa as a TTS output. For this I need to execute a batch file to call plink and run the remote batch file on a pi. t simply hangs when triggering the event. I've tracked it down to HS3 not opening a console window when running the batch. So is this a known bug? Is there any work around?

Help.
-Stan

[shodge]

I'll answer this myself - no solutions. Bottom line - don't do anything to open a console window when running as a schedule started app.

My solution was using MQTT to send a message to node-red to run the remote batch file. It works well and I learned a bunch.

-Stan