@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").

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

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

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

Will you please test it and let me know?

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

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

@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.

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

Great thanks! I have resubscribed!

@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.

@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.

@insaneoctane, I'm sure it was #3.

It has to show up on the webpage before you can trigger the command with the API, and background commands don't show up until you install the background service. That background service feature is often misunderstood. I almost wish I didn't include it. It's meant to allow you to trigger commands in the context of a Windows service or a Linux daemon so you don't have to be logged in for the commands to run.

@sverd, can you send me exactly what you have in your Command field?

It sounds to me like you're prefixing your command with the word start. If so, please try it without start.

Also if your command needs the present working directory to be C:\Program Files (x86)\SonicWALL\SSL-VPN\NetExtender, then please try making your command run a batch file with these contents:

cd /d "C:\Program Files (x86)\SonicWALL\SSL-VPN\NetExtender" NEGui

So your command would be something like c:\folder\batchfilename.bat

@web-desk, what OS are you running on the two servers? I just tested on one of my Win2012 R2 servers with recent updates and had a problem - it just didn't install the service. Can you please try this?

Close the TRIGGERcmd tray icon Right-click the TRIGGERcmd Agent icon and click "Run as administrator". Right-click TRIGGERcmd tray icon, click Background Service - Install Background Service Run Services.msc and see if you have a TRIGGERcmdAgent service

Yes and yes.
"Without a subscription, you can only have 1 computer and send 1 trigger per minute. "

If it's simple enough, you can just separate commands with a "&"

e.g. cls & dir c:\*. & timeout 5

@pico, that's interesting. I'll experiment with that. I hope it works. Thanks for the suggestion.

EDIT: I worked on it for a while and didn't get it working. I couldn't get it to add the Login item while it's quarantined. I think that's a mac security feature for apps downloaded outside of the app store.

@klimesvl, I see you signed up and cancelled today. I'll refund your money. I hope you'll re-subscribe.