Hi,
I know i am too late for the party but a workaround for someone that might be struggling with this, is to create a .vbs file.
Open notepad and paste:
Set WshShell = CreateObject("WScript.Shell")
WshShell.SendKeys("^{Esc}")
WScript.Sleep(1000)
WshShell.SendKeys("netflix")
WScript.Sleep(100)
WshShell.SendKeys "{ENTER}"
Feel free to replace any app downloaded from Microsoft store (and of course you can find it by just searching).
Then save as -> script_name.vbs
Save as type: All Files
And you are done. Watch your computer take over!!!! Terminator style
Instructions for each operating system, and various scenarios.
133
Topics
498
Posts
@Xavi-Ros, for extra security, I built TRIGGERcmd so the commands are not on the TRIGGERcmd server - they only exist on your computer, so if you don't have a backup of your C:\Users\(User Name)\.TRIGGERcmdData\commands.json file, then you have to re-create them manually. I'm sorry.
I have an Alexa routine associated with a SmartThings virtual switch, associated with my TRIGGERcmd trigger that runs a command on my Raspberry Pi that tells a relay to complete the garage door button circuit for half a second to signal my garage door opener to open the door. Boom!
Paul Hibbert does a good job of explaining the new Alexa routines here.
I explain the Raspberry Pi / relay hardware setup here, but there are probably better tutorials on setting up a Pi to flip a relay.
This shows how to use TRIGGERcmd with SmartThings.
Bubba also has some great videos explaining the process. Here's his latest video.
This is new for Alexa but I've been saying "open sesame" to Google Assistant for a while now. I like Google Assistant because I can use her on my phone, and it's easier to setup because it skips the SmartThings step because Google Assistant shortcuts can be used with any voice command. Alexa's routines only work with smart-home commands.
If I missed anything in this article, please let me know.