No problem at all @Smart-Communities. I'm glad you asked.

@abaratz, you're welcome. I'm glad that worked as a work-around. Thank you for reporting the problem too.

If anyone else experiences this problem, please tell me.

@Russ Hi Russ I had some issues with my raspberry Pi SD card corrupting and then trying to remember how I'd set it all up in the first place so wasn't using the app for a while.
However, I checked now and it's all working fine with no issues with the on/off status.
Thanks for your excellent work !

@rexabbot, no, but if you want to run foreground commands that launch GUI application like a browser, you can open a terminal window within X-Windows, and run triggercmdagent. That will run the agent in foreground mode.

Unfortunately you won't be able to use the GUI editor though, so you'll have to edit the commands.json file manually with vi or pico.

@superpan, you can see here I'm using wayland:

TRIGGERcmd Ubuntu

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

@russ

Sorry for the late reply, I didn't get any issues in the past few days, It seems to be completely working fine right now. Thanks for the help!

@russ, I've confirmed that the Alexa skill is working! Thanks for the rapid response!

@Bruno-Tomarchio, ok good. Thanks for letting me know.

@tuicemen,

This is actually wrong ^. "deviceType":"light" is not a thing.

If adding that made it work, it's because when you change a command, TRIGGERcmd deletes and re-creates the Alexa smart home device. That needed to happen for the Alexa device associated with your command to have the new brightness feature.

Sorry I didn't tell you that sooner. Any newly created commands will have the new brightness and color features. Old commands just need to be changed so they get re-created. Or you can delete and re-discover them at https://alexa.amazon.com.

Also btw, only Alexa supports brightness and color so far. I'll look into Google Assistant soon.

EDIT 3/21/22: The "TRIGGERcmd Smart Home" action on Google Assistant supports color and brightness now too.

@Steve-Lee, thank you for doing that!

You're welcome @davboc. Thanks again for finding that Paypal bug.

@buddahs808 ,

The trick is to use a simple word for google to hear in the 'voice' field for the command.

Does 'calculator' work?

@mike-cornelison, I finally figured it out. Please try "floor lamp" with Cortana again. I think it will work now.

@Abel-Boby, do you see a list of voice commands on this page?

You should have one voice command for each of your triggercmd commands that has a voice word, but only if the computer is your default computer or it has a voice word assigned to it. You can set your default computer on your profile page.

In other words, these are the requirements for creating virtual devices in Google Home for your commands:

Each command must have a voice word. Each computer must have a voice word, or it must be your default computer.

i changed the interface from GTK 3 to cinnamon and solve the problem

Thank you 🙂

@Byron-Trantham, sorry about the extra work but I'm glad you have a solution now.

@Russ
It appears the service doesn't want to startup properly now. I have to manually start it up myself. Currently it's set as Automatic.
and abort sleep isn't being discovered by my alexa.

@Forbidden-Duck, that's good. I hope it stays working.