@xander, thanks for testing. I'm glad you asked for that. I needed a Go project, and a CLI tool that calls an API is a perfect use case for Go.

@dan5150, wonder if you might have multiple TRIGGERcmd accounts, and your Alexa account is tied to the other TRIGGERcmd account?

Just brainstorming here.

If so, you could try unlinking and re-linking to your account.

EDIT: We figured it out - Dan had "shut down /s /t 30" as his command but he needed "shutdown /s /t 30". Notice the shutdown command shouldn't have a space it in. There's a shut down command in the Example commands BTW.

Great thanks! I have resubscribed!

Awesome @jay-dee! Thanks for the subscription too.

@mitchell-razga, I added the parameters to the run status.

@bruceybizzit, I think you should try either checking your debug.log file for clues, or deleting your computer in the web gui, and deleting your c:\users(username).TRIGGERcmdData folder. After deleting those, when you run TRIGGERcmd again it should prompt for the token.

@tim-s, that would be evil. My wife unplugged my Google Home in the family room because the TV triggers it.

@tim-s, your theory seems reasonable. I was sad to find out Google blocks most skills on their watches too. It's frustrating.

@pixelatedscreen, can you send me the c:\users(username).TRIGGERcmdData\debug.log file? That might have a clue.

Also, you could try uninstalling and re-installing the background service.

@miakoda-combies, I updated the .deb to support Ubuntu 18.10.

Will you please test it and let me know?

Thanks @strahan, that is super cool. I love to hear about use cases like that.

@russ So I had to put in the IP address directly...the codes wouldnt accept the localhost command. Any idea why? Thanks

@meyerdenney, I use an Alexa "Routine" to open my garage with "Alexa, open sesame", but it depends on my SmartThings system. That works because routines work with Smart Home systems.

Otherwise, I don't know of a way to do that with Alexa. I wish Alexa had something like Google Assistant's "routines" (they used to be called "shortcuts").

Just to clarify:

Bat file:

nircmd setdefaultsounddevice "VG248" 1
nircmd.exe setsysvolume 35000
PlayAlarmVBS.vbs

vbs file:

Set WshShell = WScript.CreateObject("WScript.Shell")

Comandline = "C:\Users\Username\AppData\Roaming\Spotify\Spotify.exe"
WScript.sleep 500
CreateObject("WScript.Shell").Run("linktoplaylist")
WScript.sleep 3000
WshShell.SendKeys "{ENTER}"
WScript.sleep 100
WshShell.SendKeys "^{RIGHT}"

@wadeal, the point of the voice property of your computer is to specify something you can say to Alexa that makes it easy for her to recognize. So I recommend something simple in your computer's voice field like, "movies"

Alexa/Google Assistant/Cortana don't use the computer's name field, they use the voice field to find your computer.

Click the blue Edit button for your computer on the website to get to that voice trigger field.

The only way I know how to do it is via SmartThings.

Alexa routine -> SmartThings -> TRIGGERcmd -> computer

@nathan7, if you delete your commands.json file, it will replace it with the original.

@pnick,

For some reason I ran into the same problem when I said, "Alexa, tell Trigger CMD to open movies". Alexa identified "movies" as the name of a computer for some reason.

This phrase worked better: "Alexa, ask Trigger CMD to run movies"

I'll see if I can "train" Alexa to understand the previous phrase better.

EDIT: I see I never implemented "to open" with Alexa. I'll look into adding that, but you can only use these for now:

to run to trigger run trigger

EDIT 2: There's something strange about how Alexa handles the word movies, so I'd avoid using it as a voice trigger for your command. I've been trying to tell Alexa to recognize movies as a command and she just won't.