@davboc asked me for a way to produce a list of his commands. I gave him an API call to use, and he came up with this python script that takes the output and makes it nice and readable. I thought it was pretty cool so I'm sharing it here:

import subprocess

string=subprocess.check_output(["curl -k -X POST https://www.triggercmd.com/api/command/commandlist -H 'Authorization: Bearer (your token from Instructions page)'"],stderr=subprocess.STDOUT,shell=True).strip()

array=string.decode().split('"name":')
array.pop(0);
for a in array:
    print a.split('"')[1].strip()

The output looks like this:

Downstairs > Calculator
Downstairs > Delete browse history
Downstairs > Launch a website
Downstairs > Notepad
Downstairs > Rebooting in 10 seconds
Downstairs > Volume Down
Downstairs > Volume Up
Garage > Betsy Garage Door
Garage > Reboot
Garage > Russ Garage Door
Garage > apt update
Garage > boot russfam
Laptop > Calculator
Laptop > Delete browse history in Internet Explorer
Laptop > Down Arrow
Laptop > Email my document list
Laptop > Launch a website
Laptop > Lock my PC
Laptop > Play mp3's in your Music folder
Laptop > Reboot
Laptop > Update Windows
MintNAS > Gnome Editor
MintNAS > Reboot
MintNAS > apt update
MintNAS > yum update
RussFam > Backup Documents
RussFam > Calculator
RussFam > Dropbox
RussFam > Email my document list
RussFam > Michael Jackson Thriller Album
RussFam > Mute

I can say:

• Alexa, ask TRIGGERcmd to run Type This with parameter I am the coolest

And my computer will type "I am the coolest" wherever my cursor happens to be.

Create c:\tools\typeit.vbs with these contents:

Dim Wsh
Set Wsh = Wscript.CreateObject("Wscript.Shell")

Set args = Wscript.Arguments

For Each arg In args
  Wsh.SendKeys arg
  Wsh.SendKeys " "
Next

Then create a command in TRIGGERcmd like this with parameters turned on:

wscript c:\tools\typeit.vbs

TRIGGERcmd runs your commands super fast, so if you're testing this on the computer where the agent is running and using the Parameters button on the website, you can add a 5 second pause at the beginning of the script with this command. That should give you enough time to click another window before it types your parameters in that window.

WScript.sleep 5000

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

@nuzibito, if it works from the website and it's on the printable voice command list, it should work fine with Alexa. If you're using the Smart Home skill, just remember to Discover devices at https://alexa.amazon.com.

If you don't see it on the voice command lists, you probably need to fill in the voice field for the command and/or the computer.

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!

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 made this video to demo this.

You can use this strip, or any similar 5V addressable LED strip.

To prepare the Raspberry Pi with the OS, the TRIGGERcmd agent, and connection to your wifi, I recommend the setup.bat script that makes that process a snap.

I used a $10 Raspberry Pi Zero W, but any Pi should work.

Run these commands to install pre-reqs:

sudo su -
apt install python3-pip
pip3 install rpi_ws281x

Contents of green.py:

import sys
from rpi_ws281x import *

if len(sys.argv) > 1:
    if sys.argv[1] == "white":
        color = Color(255,255,255)
        print("white")
    elif sys.argv[1] == "green":
        print("green")
        color = Color(0,255,0)
    elif sys.argv[1] == "red":
        color = Color(255,0,0)
        print("red")
    elif sys.argv[1] == "blue":
        color = Color(0,0,255)
        print("blue")
    elif sys.argv[1] == "off":
        color = Color(0,0,0)
        print("off")
    else:
        color = Color(255,255,255) # white
        print("white")
else:
    color = Color(255,255,255) # white

# LED strip configuration:
LED_COUNT      = 300      # Number of LED pixels.
LED_PIN        = 18      # GPIO pin connected to the pixels (18 uses PWM!).
#LED_PIN        = 10      # GPIO pin connected to the pixels (10 uses SPI /dev/spidev0.0).
LED_FREQ_HZ    = 800000  # LED signal frequency in hertz (usually 800khz)
LED_DMA        = 10      # DMA channel to use for generating signal (try 10)
LED_BRIGHTNESS = 255     # Set to 0 for darkest and 255 for brightest
LED_INVERT     = False   # True to invert the signal (when using NPN transistor level shift)
LED_CHANNEL    = 0       # set to '1' for GPIOs 13, 19, 41, 45 or 53

strip = Adafruit_NeoPixel(LED_COUNT, LED_PIN, LED_FREQ_HZ,LED_DMA,LED_INVERT,LED_BRIGHTNESS,LED_CHANNEL)
strip.begin()

for x in range(0,LED_COUNT):
    strip.setPixelColor(x,color)

strip.show()

0,255,0 is green, 255,0,0 is red, and 0,0,255 is blue.

commands.json entries:

    {"trigger":"Lights","command":"python3 \/root\/leds.py","ground":"background","voice":"lights","allowParams": "true"},
    {"trigger":"White","command":"python3 \/root\/leds.py white","ground":"background","voice":"white","allowParams": "false"},
    {"trigger":"Green","command":"python3 \/root\/leds.py green","ground":"background","voice":"green","allowParams": "false"},
    {"trigger":"Blue","command":"python3 \/root\/leds.py blue","ground":"background","voice":"blue","allowParams": "false"},
    {"trigger":"Red","command":"python3 \/root\/leds.py red","ground":"background","voice":"red","allowParams": "false"},
    {"trigger":"Off","command":"python3 \/root\/leds.py off","ground":"background","voice":"off","allowParams": "false"}

This picture shows how to wire it. Red is 5V, Grey is ground, and White is signal (middle wire on the LED strip).

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.

rundll32.exe InetCpl.cpl,ClearMyTracksByProcess 255

@tuicemen, I just tried it. It worked nicely.

Here's my Alexa Routine config:

I'm using the TRIGGERcmd skill which works the same as the Trigger Command skill.

I used a "Custom" action with this text: ask TRIGGER C M D to run result

My command config looks like this:

My super basic python script looks like this:

import os
result = 'Nineteen'
sts = os.system(os.environ['USERPROFILE'] + "\\.TRIGGERcmdData\\SendResult.bat "+str(result))

@marcott, please try this as a .bat file script:

nircmd sendkey shift down
nircmd sendkey ctrl down
nircmd sendkey alt down
nircmd sendkey b press
nircmd sendkey shift up
nircmd sendkey ctrl up
nircmd sendkey alt up

If you don't have nircmd yet, this video shows how to install it.

This is the relevant nircmd documentation page: https://nircmd.nirsoft.net/sendkey.html

@matt-packwood, do you have any antivirus software on your Mac? You could try disabling that temporarily to see if that's killing the agent somehow. That might explain why it's happening on your mac but no one else has seen it.

@skrttz , whenever there are spaces in the command path, you have to quote it.

@skrttz, I tried that method but it didn't work for me. I did find a method though.

I created a shortcut (.lnk) file, and I'm able to run it via that shortcut like this:

These were my steps to create the xbox.lnk file on my desktop:

Open the Applications folder:

Right-click Xbox and click Create shortcut:

Now I have an Xbox.lnk file on my desktop:

@skrttz,

I used this process and found the protocol name in this section of the AppxManifest.xml file:

  <Extensions>
    <uap:Extension Category="windows.protocol">
      <uap:Protocol Name="xbox-tcui" />

But when I ran start xbox-tcui I got this useless window:

So for some reason the normal process doesn't work for the Xbox app.

I'll do some more research, but it's not looking good.

@mevlüt-bora, you wrote, "Even try to turn it off manually with the GUI, it still didn't turn it off." That information helps narrow it down.

Are you using this command to shutdown?

shutdown /s /t 60

If so, can you try that in a cmd window like this?

I wonder if that will give an error - like maybe it doesn't have access to shutdown.

@skrttz, when I used this command to close Brave, it saved my browser tabs:

taskkill /im brave.exe

When I re-opened Brave, my tabs were re-opened.

@david-albino, the agent should start automatically when you login.

For some use-cases you might want to run the background agent which starts up even before you login because it runs as a Windows service. It only runs background commands and they run in the background so you don't see them running. That's why use-cases are limited.

To install background agent, you right-click the TRIGGERcmd agent icon in your tray, then click Background Service, then Install Background Service.

If you want the normal foreground agent to start during boot without having to login, you could also configure your Windows to automatically login.

@legtod2, if you can control it with a keyboard, you might be able to use this "keyboard" python module to make commands that simulate keyboard strokes.

https://github.com/boppreh/keyboard

@skrttz, what's wrong with ending the Brave browser task? Do you not want the tabs to be saved? I'm trying to figure out what you want to happen differently.