Posts made by Russ

@batteryxsnare, I see the problem, and I'll work on it. Right now the SmartThings SmartApp uses the computer and command ID's, but if I switch to using the computer name and command name to match the SmartThings switches to the triggercmd commands, it would allow you to move your commands to a new computer, name it the same in TRIGGERcmd, and you wouldn't have to re-create your SmartThings switches.

I'll have to make a new version of the SmartThings app code, and unfortunately you will have to delete your switches and re-add them to move to the new code.

I'll let you know when it's ready. Thank you for reporting this problem!

@strahan, the connection is made from the agent on your computer to the TRIGGERcmd servers via that IP. That doesn't mean traffic only has to flow in that one direction.

In that IFTTT scenario, IFTTT sends a web request to the webhook on one of the TRIGGERcmd servers, and the TRIGGERcmd server your agent is connected to tells the agent to trigger the command.

@strahan, currently the only IP is 75.75.214.51. The connections are only outbound from your house to that IP over https/443.

Good question @strahan.

All of your triggers are in the commands.json file in the .TRIGGERcmdData subfolder of your user home folder.

In my case it's C:\Users\russe\.TRIGGERcmdData\commands.json

Just take a copy of that, and on your new computer, after installing the agent, copy/paste this file to the same place.

If you want Google Assistant or Alexa to tell you when you last rebooted, put this in your Voice Reply field:

Rebooted on {{result}}

Create a file with a name like RebootDate.ps1 and create a TRIGGERcmd command that runs it, like this:

powershell c:\LastReboot\RebootDate.ps1

Put these contents in the c:\LastReboot\RebootDate.ps1 file.

$month=(Get-WmiObject -class Win32_OperatingSystem | Select-Object  __SERVER,@{label='LastBootUpTime';expression={$_.ConvertToDateTime($_.LastBootUpTime)}}).LastBootupTime.Month.tostring()

$day=(Get-WmiObject -class Win32_OperatingSystem | Select-Object  __SERVER,@{label='LastBootUpTime';expression={$_.ConvertToDateTime($_.LastBootUpTime)}}).LastBootupTime.Day.tostring()

~/.TRIGGERcmdData/sendresult.bat $month/$day

Here's a video showing how to do this: https://youtu.be/VugF9t-UK7Q

If your command has {{result}} in the Voice Reply field, then the voice assistant will wait a few seconds for a "result" of the command to be logged in the Runs list for that command, and will include that result in what it says back to you.

So for example, you could have Alexa run a command on your Raspberry Pi that would take the temperature, and Alexa could tell you that temperature.

As a test, I put this in my Voice Reply field of my "Results Test" command:

Running {{trigger}} on {{computer}} with result {{result}}

I put this in the Command field:

%USERPROFILE%\.TRIGGERcmdData\sendresult.bat "My command result"

NOTE: Use ~/.TRIGGERcmdData/sendresult.sh instead for Linux/Mac/Raspberry Pi.

I said this:

Hey Google, ask trigger CMD to run results test

Google Assistant said this:

Running results test on DS with result My command result

You only have about 4-5 seconds to send a result via that SendResult script. If you take too long, it will say "no result" in the {{result}} placeholder.

@colegl and @phil-tanguay, I implemented this today for Google Assistant. I'm working on Alexa now.

I put this in my Voice Reply field of my Notepad command (I should have just created a new command):

Running {{trigger}} on {{computer}} with params {{params}} with result {{result}}

I put this in the Command field:

%USERPROFILE%\.TRIGGERcmdData\sendresult "My command result"

I said this:

Ask trigger command to run notepad with parameter russ

Google Assistant said this:

Running notepad on DS with params russ with result My command result

I'm pretty happy with how it turned out.

I only gave about 4-5 seconds to send a result via that SendResult.bat script. If you take too long, it will say "no result" in the {{result}} placeholder.

EDIT: Now you can do this with Alexa too.

@alvaro-gutierrez-romero, you should have a new tray icon in the lower-right after you paste in your token. Do you have that?

@koen-van-lent, it should work with a free account too, but only 1 per minute of course.

Do you have token=(your token from Instructions page) in the body?

@mark-kreger, you could create a c:\tools folder, and in it, create a ClearHistory.bat file in it with these contents:

REM Clear IE history:
rundll32.exe InetCpl.cpl,ClearMyTracksByProcess 255

REM Clear Chrome history:
cd /d C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data
del /s History*

Then create a TRIGGERcmd command that runs c:\tools\ClearHistory.bat

Thanks @xander !

I generally don't like to ask for reviews, but Google is telling me they're not willing to publish my "TRIGGERcmd Smart Home" action because I don't have enough positive reviews.

So, if you love TRIGGERcmd, I'd appreciate your reviews.

• TRIGGERcmd Smart Home Alexa skill: https://www.amazon.com/product-reviews/B07P1MMFRP <- This works like the TRIGGERcmd Smart Home Google action I'd like to publish.
• TRIGGERcmd Alexa skill: https://www.amazon.com/product-reviews/B06XFN2TZN
• TRIGGER command Alexa skill: https://www.amazon.com/product-reviews/B074TV61DK
• TRIGGERcmd Google Assistant action: https://assistant.google.com/services/a/id/5aba4539c049e69e
• TRIGGER command Google Assistant action: https://assistant.google.com/services/a/uid/000000c97192e061

I was just googling and found this review by Paul E King:
https://www.pocketables.com/2018/12/how-to-use-google-assistant-and-others-to-control-your-pc-mac-pi-etc.html

Thanks Paul!

@js, can you post the commands you're using to turn your monitor on and off?

You can use a script like this to handle the on and off parameters:

#!/bin/bash

if [ "$1" = "on" ] ; then
  echo Turning it on
fi

if [ "$1" = "off" ] ; then
  echo Turning it off
fi

You'll find it in the directory as Ejecuta Comando.

@Fernando-Mateos, @Fernando-Mateos-Lopez and @David-Jiménez-Lamas,

Amazon approved the spanish version today. You'll find it as Ejecuta Comando.

I actually discovered this when I accidentally said, "Alexa, run calculator."

Apparently if you've already said, "Alexa, ask TRIGGERcmd to run X", then next time you only have to say, "Alexa, run X."

That's awesome. I hope Google Assistant does the same.

@tim-s and @meyerdenney, yea I wish they didn't do that. Alexa's doing it now too, so I suspect there's some legal reason for it. I'm guessing it's to let users know this is a third party, not a Google service you're about to hear from.

I was research this and came across this pretty thorough blog post.
https://www.androidpolice.com/2018/02/10/ultimate-guide-google-home-tips-tricks-understanding-making-assistant-speaker/

I learned a few things from it, including that other people are annoyed by the multiple voices issue too:

"Assistant apps talk back to you in a different voice than the one you're used to hearing from your Google Home. It's jarring at first, but Home will respond with, "Alright, getting X," and another voice will come up and tell you what this particular app/service can do and will continue answering you until you're done with it and want to go back to the regular Home voice and commands..."

I also found this reddit post from a year ago that says Google Assistant will stop saying, "Alright, getting X" after you've been using X for a while. Unfortunately that hasn't been my experience.
https://www.reddit.com/r/googlehome/comments/80efhh/google_home_stopping_talkative_introduction_to/

I also noticed Alexa doesn't always say "Ok here's TRIGGERcmd, ..." For instance if I say, "Alexa, run calculator" she doesn't, so maybe if the command is short enough she doesn't say it.

Some of you might have noticed, when you'd say something like:

Alexa, ask TRIGGER cmd to run notepad on downstairs

You'd get an answer like this:

"Could not find a command with voice word cmd notepad on downstairs, ..."

I fixed that today.

For some reason Alexa started sending the "cmd" part of "TRIGGER cmd" as a prefix in the command name. I actually had to add code to strip that out.

@jackson-pollard, I was able to reproduce the problem and I figured out why it worked in the GUI but not from the website.

This is how you can fix it. Just change your command to this:

echo "python giveTour.py fullTour" > ~/Desktop/Cram0002/reqs.txt

The reason it didn't work is the present working directory is /usr/lib/triggercmdagent/resources/app/src when the command runs remotely, but when you run it locally via the GUI, your present working directory is your home directory.

So if you just specify your home folder using the ~ character, it finds the correct folder to write the file to.