@daveola, I think I'm due for an update to that Youtube video. I'll make sure it's more prominent in the new recording.

The desktop icon the agent installs on the desktop just runs that tray icon, so that doesn't help much.

@atmosphere, wow, I'm glad that was it because I had no idea what I could do about that.

@bobrdavies, I'm glad you found it - yea the forum is a separate system so you have to use a separate account.

@veepueco, if you run it from a cmd prompt does it work? Also, can you send a screenshot of the file name and path, and paste the contents of your script below?

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

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

Thanks @xander !

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

@russ Thanks a lot, this worked. I shouldn't've assumed it would always run in the home directory. This saved me a lot of headaches.

I got it working. It turns out that when you add a TRIGGERcmd command to the Webcore device list on your SmartPhone (Webcore > Settings > Available Devices), you have to scroll way down the screen to the Switches section. Normally most devices will show up at the top in the Actuators section.

@hellomiakoda, when I uploaded the .deb file last time I updated it, apparently I forgot to make it public.

@hellomiakoda, thanks for telling me. Please try again. It should work now.

@russ Thanks! I will try it

Just tried it out and it works! Thanks!!

@jebus-jones, please try again. It should work now. I'm sorry it took so long to fix. I put some details about the problem here:

https://www.triggercmd.com/forum/topic/399/is-the-goolge-home-triggercmd-app-working

Please disregard. I figured out that I had to remove the current listed PC in the web console, and then it allowed me to add token.

@thecussen, awesome. Thanks for sharing your use case.

This makes a lot of sense (because most of the "on" commands are the ones experiencing issues. I'm at work now, but will modify the commands when I return home and post the results. Thanks again for your assistance.

UPDATE: The issue is resolved. Removing the "on" from the end of the voice field fixed the problem. Thanks again!