@brad-schmidt, I did some more research and I think I have way that's not terribly difficult.

Install nodejs if it's not already installed. Create a folder like: c:\eaglecam Download and unzip the version of the chrome webdriver for your version of Chrome into that folder.
http://chromedriver.chromium.org/downloads Copy/paste the code below into a file called play.js in your folder. Open a cmd prompt and type: cd \eaglecam Run: npm install selenium-webdriver Run: node play.js If that works, open the TRIGGERcmd GUI and create a this command: 😄 & cd \eaglecam & node play.js const {Builder, By, Key, until} = require('selenium-webdriver'); var driver = new Builder() .forBrowser('chrome') .build(); driver.manage().window().maximize(); driver.get('https://portal.hdontap.com/s/embed/?stream=aef-nefl-CUST-multicam&ratio=16:9&fluid=true') .then(_ => driver.sleep(2000)) .then(_ => driver.findElement(By.className('vjs-big-play-button')).click())

@zipster1967, you can only edit them using the TRIGGERcmd agent installed on your computer. You can't edit them on the website.

If you run Windows, you should have a "tray" icon in the lower-right near your clock. You can right-click that, then click "GUI Command Editor". Then click the pencil next to the commands you want to edit. Please confirm you've gotten that far.

The background commands are added/removed by the background service. The foreground commands are added by the foreground agent. That tray icon is part of the foreground agent.

@batteryxsnare, unfortunately I see no smoking gun in that output.

@lima, you might be able to shrink it down a little, but probably not much because the agent needs a few node module dependencies which require other dependencies. Most of that bloat if from electron for the GUI - it's basically a small version of the Chromium browser which is at core of Chrome.

@meyerdenney, the only way I know how to that is to setup your TRIGGERcmd command as a SmartThings switch because your SmartThings devices show up under Smart Home in Alexa routines.

EDIT: @meyerdenney, I'm looking into creating a TRIGGERcmd Alexa Smart Home skill. That should solve this. I'm planning to make each command act like an on/off switch, just like the SmartThings integration.

EDIT 2: I finished the TRIGGERcmd Smart Home Alexa skill and it's awesome. Alexa can recognize your words much better with this TRIGGERcmd Smart Home skill because she knows the limited set of trigger names.

@honvl, the Runs list for each command logs "Trigger sent" and "Command ran". "Trigger sent" is logged when the TRIGGERcmd server tells the agent to run a command. "Command ran" is logged when the agent actually runs the command and reports back to the server.

@dennism, thank you for reporting it. I confirmed this was a bug with version 20 of the Windows client. I pulled it off the site so the the link goes to version 19 again.

I thought at first that this was just an Avast issue because I get this issue even with version 19 if I've got Avast installed. The workaround for Avast users is to temporarily disable it during the TRIGGERcmd agent install.

EDIT: I created a new version (v21) that fixed the bug and includes v20's new feature for sending a command's result to the Runs list.

Sorry for the bug, and thanks again for reporting it.

@stevef9432203, if you can install nodejs on it, then it should work.

If you can verify that, let me know and I'll help get it installed.

Be sure to to autostart the service boot -
sudo systemctl enable triggercmdagent.service

@gnetdevelopment, so far I've only implemented the ability to send feedback to the Runs history for each command.

Now that that's done, I'm planning to add the ability to have Alexa or Google Assistant wait a few seconds for a result to be sent back, then say the result.

Let's say you wanted to know how many packages can be upgraded on your Raspberry Pi. You could add a command that would run this script:

#!/bin/bash export UPGRADABLE_COUNT=$(apt list --upgradable | grep upgradable | wc | cut -f 6 -d " ") sh ~/.TRIGGERcmdData/sendresult.sh "${UPGRADABLE_COUNT} packages could be upgraded."

It would look like this in the website, and when I get the Alexa and Google Assistant work done, you could have the result spoken when you run it by voice.
Upgrade Check Result

I guess I figured out how to edit the triggers but I still not able to create working command I want to start a program on my computer but am unclear on where to put the program name to get it to run. Is there anywhere to find a tutorial on how to build new triggers?

@jorgee, have you tried deleting your c:\users\(your user)\.TRIGGERcmdData folder? If you do that, then close and re-open TRIGGERcmd, it might fix it.

Another possibility is your Antivirus software is blocking it. You could try turning that off temporarily while TRIGGERcmd runs for the first time.

@russ /usr/local/bin/wakeonlan was the ticket.
Thanks so much for the info, able to make my PCs from my Mac from a full power off now!

@atmosphere, I'm sorry but right now the TRIGGERcmd installer only supports one TRIGGERcmd account per Raspberry Pi.

But, theoretically you could maybe run two instances of the TRIGGERcmd agent on the Pi, as two separate Linux users, and give those two users sudo access if they need to run things as root.

If you run triggercmdagent --console it will run in foreground mode like so, and store two separate commands.json files in the .TRIGGERcmdData subfolder of their respective home folders:

pi@raspberrypi:~ $ triggercmdagent --console Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot Daemon install: false No token exists. Login to request one. prompt: token:

The trick would be in getting the two agents to run after a reboot.

Thanks @jdeuel.

@karl-g, please uninstall and download again. I removed version 1.0.20 and put 1.0.19 back until I can figure out why people are getting that error.

@kaiontour, unfortunately I only have so much control over what Alexa will recognize, which is why I gave the user the flexibility in that voice field to pick something that Alexa will recognize. You could try "restart kodi" instead of "kodi restart" if that works better.

Thank you,