@William-Santiago-Ortiz-Trejos, for some reason your files with a .ahk extension aren't associated with AutoHotkey. That's supposed to happen when you install it, but maybe an antivirus program blocked it?

To fix it you could try running the batch file in this article from your C:\Program Files\AutoHotkey folder:
https://www.autohotkey.com/board/topic/13627-no-ahk-file-association/

@kalen-daniel, I didn't provide a method to auto-start the triggercmdagent in the foreground on a Pi. Your method is helpful because it provides a way to do that.

I figured most people would not run X-windows on their Pi's, like my-use case as a garages door opener. In cases like that, you'd run this script as root:

/usr/share/triggercmdagent/app/src/installdaemon.sh

... to install the triggercmdagent as a systemd daemon that would only run background commands.

After you run that script you can stop/start or get a status of the agent with these commands:

systemctl stop triggercmdagent
systemctl start triggercmdagent
systemctl status triggercmdagent

Christian, I looked at your voice words for your commands, and tried them. The 2nd one worked well for me, but I had to remove the "ing" from the 1st one before Alexa recognized it.

Your voice word for your computer worked well for me.

One thing I found too is that Alexa understands better if you pause for about 1 second between "run X" and "on Y". So think of it like a comma - run this, on that.

Also I just noticed a bug in the agent when I tested that. I found that if I only change the voice word for the command in commands.json, it doesn't update on the website. I had to change another field for it to update the command's voice word. Oops! I'll try to fix that and post a new version of the agent by tomorrow.

Thank you for testing!

Alexa Routines now works with the original "TRIGGERcmd" and "TRIGGER command" skills.

This is great because now instead of saying:

Alexa, ask TRIGGERcmd to run notepad on office with parameter russ

You can just say:

Alexa, russ

I just created this video to show how it works: https://youtu.be/rZXfncqXqmA

Also these screenshots show how to set it up in the Alexa app:

You'll need to install this on your Windows box to make it work: https://autohotkey.com

This is my media.ahk autohotkey script:

Gosub, %1%
return

next:
Send {Media_Next}
return

previous:
Send {Media_Prev}
return

pause:
Send {Media_Play_Pause}
return

play:
Send {Media_Play_Pause}
return

stop:
Send {Media_Stop}
return

volup:
Send {Volume_Up}
return

voldown:
Send {Volume_Down}
return

mute:
Send {Volume_Mute}
return

These are the corresponding commands.json entries:

{"trigger":"Mute","command":"start C:\\autohotkeyscripts\\media.ahk mute","ground":"foreground","voice":"mute"},
{"trigger":"Volume Up","command":"start C:\\autohotkeyscripts\\media.ahk volup","ground":"foreground","voice":"volume up"},
{"trigger":"Volume Down","command":"start C:\\autohotkeyscripts\\media.ahk voldown","ground":"foreground","voice":"volume down"},
{"trigger":"Media Next","command":"start C:\\autohotkeyscripts\\media.ahk next","ground":"foreground","voice":"next"},
{"trigger":"Media Stop","command":"start C:\\autohotkeyscripts\\media.ahk stop","ground":"foreground","voice":"stop"},
{"trigger":"Media Previous","command":"start C:\\autohotkeyscripts\\media.ahk previous","ground":"foreground","voice":"previous"},
{"trigger":"Media Play Pause","command":"start C:\\autohotkeyscripts\\media.ahk pause","ground":"foreground","voice":"pause"},

NOTE: You don't need a Play and a Pause because they do the same thing - they just toggle between play and pause.

This is optional, but I'm also using my Raspberry Pi based IR receiver to trigger the above commands with a VCR remote.

I have these entries in my /etc/lirc/lircrc file on the Pi:

  begin
       prog = irexec
       button = KEY_1
       config = export HOME=/root ; /root/triggertest.sh play downstairs
  end
  begin
       prog = irexec
       button = KEY_2
       config = export HOME=/root ; /root/triggertest.sh notepad downstairs
  end
  begin
       prog = irexec
       button = KEY_PLAY
       config = export HOME=/root ; /root/triggertest.sh "Media Play Pause" downstairs
  end
  begin
       prog = irexec
       button = KEY_PAUSE
       config = export HOME=/root ; /root/triggertest.sh "Media Play Pause" downstairs
  end
  begin
       prog = irexec
       button = KEY_RIGHT
       config = export HOME=/root ; /root/triggertest.sh "Media Next" downstairs
  end
  begin
       prog = irexec
       button = KEY_LEFT
       config = export HOME=/root ; /root/triggertest.sh "Media Previous" downstairs
  end
  begin
       prog = irexec
       button = KEY_STOP
       config = export HOME=/root ; /root/triggertest.sh "Media Stop" downstairs
  end
  begin
       prog = irexec
       button = KEY_UP
       config = export HOME=/root ; /root/triggertest.sh "Volume Up" downstairs
  end
  begin
       prog = irexec
       button = KEY_DOWN
       config = export HOME=/root ; /root/triggertest.sh "Volume Down" downstairs
  end
  begin
       prog = irexec
       button = KEY_MUTE
       config = export HOME=/root ; /root/triggertest.sh "Mute" downstairs
  end

I followed this tutorial to get my Pi Zero W on wifi without even connecting a keyboard and monitor to it.

I followed this tutorial to get it setup with lirc to run commands when I press corresponding buttons on an old VCR remote.

I setup the lircrc file to call the TRIGGERcmd API using curl commands when I press those buttons.

I found the curl commands to be much faster than these commands.

I also found that some remotes work better than others - like my Window Media Center remote works, but each button alternates between two different IR codes, so it works every other time you press a button. I settled on an old Toshiba VCR remote.

My /etc/lirc/lircrc file looks like this:

  begin
       button = KEY_PLAY
       prog = irexec
       config = export HOME=/root ; /root/triggertest.sh calculator downstairs
  end
  begin
       prog = irexec
       button = KEY_RIGHT
       config = export HOME=/root ; /root/triggertest.sh notepad downstairs
  end

My /root/triggertest.sh file looks like this:

#!/bin/sh

trigger=$1
computer=$2
token=`cat /root/.TRIGGERcmdData/token.tkn`

curl -X POST https://www.triggercmd.com/api/run/triggerSave \
-H "authorization: Bearer ${token}" \
-H 'content-type: application/json' \
-d "{\"computername\":\"${computer}\",\"triggername\":\"${trigger}\"}"

I'm sorry installing the background service it didn't work. I hope I can figure out why. I have Windows 10 too. I just tried uninstalling and re-installing the background service and it works for me.

Do you see the TRIGGERcmdAgent service listed in you Windows services? If so, maybe you just need to start it, or stop/start it.

When you installed the background service, did you see a "User Account Control" prompt to allow Node.js to make changes to your device? I assume you click Yes to that?

I'd appreciate any clues you can give me to help me reproduce the problem.

@Craig-OK, I've been thinking about this. None of the methods for shortening the Alexa phrase (ifttt or routines) allow for parameters, so I can't think of a good solution besides, just saying the whole thing:
Alexa, ask TRIGGERcmd to run download with parameter Ubuntu server

And that assumes the command with download in the voice field is on your default computer.

rundll32.exe InetCpl.cpl,ClearMyTracksByProcess 255

It all started when my house got robbed. I was frustrated by my cheap video cameras because I had video of the thief coming and going, but the quality was too low to provide many useful clues. The police probably could have identified the bad guy sooner if I'd had better video.

On my low res cameras I could see this guy leaving my house with my headphones, bike, hat, shoes, clothes, and a backpack full of valuables. He tracked mud all over my house and even took the time to take a shower. :rage:

Here he is in the backyard, hiding from my camera before he snuck around and disconnected it. You can see the resolution is not very good.

So I went on a tech shopping spree and upgraded my video surveillance system to HD and invested in a Samsung SmartThings based alarm system with presence sensors, motion sensor, door sensors, and a device that sounds the alarm if someone disconnects a camera. The thief disconnected a camera before he broke in, so I figured that device was worth installing.

One downside of an alarm system is the false alarms. Just last night I had one when I got back home from the bar after midnight. I don't drink, but I was hanging out with my kickball team after our game (we lost). To quickly turn off the alarm I setup a secret light switch that turns off my alarm when you flip it. At first I couldn't find a way to do that with a SmartThings SmartApp, so I used an IFTTT trigger.

I'd heard of IoT (internet of things) before all this, but I thought it was a marketing fluff (which it is), so I wasn't too interested, but using SmartThings and IFTTT for practical purposes piqued my interest and got my geek juices flowing. However, I realized one THING was missing from IoT - it was my PC.

About a year prior, I had published a few games, but I was looking for something else to build because I was spending too much time on these games and they weren't making me any money. A couple of them have been downloaded around 5000 times on the Amazon app store,

... but my ad revenue is still less than $200 even though my games have served over 1.1 million ads.

So I was looking for a non-game idea that's not too ambitious because I wanted to be able to finish it.

In my research I found Sails.JS which introduced me to websockets, which I thought was super cool because it lets the client interact with the server instantly. That's why modern real-time chat apps use it. While testing various websocket clients and servers I learned that Node.JS can run javascript code as a client and/or as a server. The Sails.JS server runs on Node.JS and has a javascript module for the client. This Sails.JS client module usually runs in the browser, but it can also run in other client apps, like the TRIGGERcmd agents.

When I learned about Electron, the TRIGGERcmd idea started to form. Electron adds a GUI to Node.JS to produce a cross-platform GUI application. It's based on Google's open-source Chromium project, which is the core of Chrome. The Raspberry Pi version is the only version of the TRIGGERcmd agent that doesn't use a GUI and therefore doesn't use Electron - it just uses Node.JS.

After the basic application and agents were ready, I wrote an integration with Alexa so you can use your voice to trigger commands. My best, most helpful user, @Christian-Robinson found TRIGGERcmd via the Alexa Skills store. He was actually looking for a way to run commands on his computer with Alexa.

I wrote another integration with Zapier so you can trigger commands based on various events like a new gmail emails, new files in dropbox, new posts on slack or facebook, etc... Zapier also has scheduler, so you could trigger a command once per day or something. Zapier works like IFTTT. It has some advantages over IFTTT but it's not as well known. IFTTT also wants $2,388 per year to integrate, which is way too much for me at this point. Edit 5/28/17: Now you can use IFTTT to trigger commands via their free Maker service. Zapier won't publish the integration until I get at least 10 users, so you could help me out by trying TRIGGERcmd with Zapier.

I also wrote an integration with SmartThings. Until Samsung approves it, you'll have to install it using their developer console. The TRIGGERcmd SmartApp lets you add virtual SmartThings switches for TRIGGERcmd commands you select. Then you can flip one of those virtual switches either manually in the SmartThings app, or automatically based on some event like motion sensed, a door opened, a temperature reached, switch flipped, etc... When you flip the virtual switch associated with your TRIGGERcmd trigger, it triggers the command, and immediately flips off.

I added the ability to run commands remotely by running a command, then when while I was setting up my Raspberry Pi Zero W to run remote commands when I press buttons on an old VCR remote, I realized it's actually faster to just run a curl command that hits the REST API directly.

Finally, I added Paypal integration so maybe someday TRIGGERcmd will make me some money, or maybe it will at least stop costing me money. You can use it without subscribing if don't want to run more than one command per minute. At this point the Alexa, Google Assistant, Zapier, and SmartThings integrations don't have that limitation. Nor does the command-line (or curl) method of triggering commands.

I hope you like TRIGGERcmd as much as I do, and I hope you post your questions, bug reports, use cases etc. on the forum.

@víctor-merino, please confirm you enabled the "TRIGGERcmd Smart Home" skill.

That's the only skill that will create an Alexa smart home device for each command that has text in the voice field.

You also need text in the computer's voice field unless it's your default computer. You set your default computer in your profile and you get to your profile by clicking your name in the upper right.

@eraldo_crj , it seems to me the agent isn't connected to the server for some reason.

Can you try closing it and re-running it? You can close it by right-clicking the tray icon and clicking Quit.

Also, can you paste the contents of your debug.log file here?
C:\Users\(your user)\.TRIGGERcmdData\debug.log

There could be a firewall in the way. The debug.log might give us a clue.

@matúš-maron, no problem. I'm glad you figured it out.

@dean-mcnaughton, that's awesome! I'm always interested in use-cases like this. Thanks for sharing.

@oscar-mro, this .bat file worked for me:

start https://google.com
timeout 3
nircmd sendkey tab press
nircmd sendkey spc press

It opens google, waits 3 seconds for it to finish opening, then presses tab, then space to select the microphone.

@dean-mcnaughton, awesome. Nice job.

@chaim-tscholkowsky, I see your command's name is "outside" but its voice field is blank. Please try again after you set that to "outside".

If it still doesn't work, you could try switching to the TRIGGERcmd Smart Home skill instead of the TRIGGERcmd skill.

The Smart Home skill works better, but you'll need to treat it like an on/off switch and say something like this instead:
Alexa, turn on outside. or Alexa, turn outside on.

@matúš-maron, can you show me your WOL1.sh script?

Also, please add a command to it like this, so you'll be able to confirm it's actually running:

echo "WOL1 ran" >> /tmp/wol1.log

If the /tmp/wol1.log shows the command is running, then maybe the WOL1.sh script is running with a different value for the PATH environment variable, so maybe it can't find the wakeonlan command. If that's the case, you could solve it by specifying the full path to wakeonlan when you run it.

@dean-mcnaughton, sorry I wasn't clear. Parenthesis are not necessary. I think either of these should work:

rest_command:
  triggercmd_calculator:
    url: 'https://www.triggercmd.com/api/run/triggerSave'
    method: "post"
    content_type: "application/x-www-form-urlencoded"
    payload: "computer=laptop&trigger=calculator&token=xyz....abc"

rest_command:
  triggercmd_calculator:
    url: 'https://www.triggercmd.com/api/run/triggerSave?computer=laptop&trigger=calculator&token=xyz....abc'
    method: "get"
    content_type: "application/x-www-form-urlencoded"

Also, the token can come from the token.tkn file on your computer or the Instructions page - either should work.

You could also test with curl like this:

curl "https://www.triggercmd.com/api/run/triggerSave?computer=laptop&trigger=calculator&token=asdf"

I made this Youtube video to show how to auto-open your tweets with specific hashtag using IFTTT.

https://youtu.be/3ZGFAegDBdc