@Anderson-Lajes, I installed the TRIGGERcmd agent on Mint Linux and it worked well for me.

7d6443d8-bbc9-4e14-8ac8-003a7335fb63-image.png

If you run it on Hyper-V, you'll want to use a Generation 2 virtual machine, and disable secure boot.

Also, to use the Background Service you'll need nodejs installed:

sudo apt install nodejs

@Jogador-Extremo-live said in Turn Computer Monitors Off:

I have two monitor, is there a way to turn off just my second monitor?

So this is basically what I need, did you manage to do this?

I want to play games on my TV which is one of 3 monitors I have. And i want to turn off both monitors to have only the TV i'm using to game

@j0semm, I see those are all background commands, which will only be added if you're running the agent in background mode, which happens when you install the background service with a command like this:

sudo sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.sh

That will install it as a linux service you can view with a command like this:

systemctl status triggercmdagent

The Gnome Editor command probably got added when you ran the agent the first time. You run it in foreground mode the first time to install the token. That Gnome Editor command is a foreground command in the default commands.json file.

@tal-sabadia, there is a way to get a simple "failed" or "succeeded" voice response for a long script run or a script that you trigger manually.

1: It requires creating two TRIGGER.cmd dummy scripts (dummy1 & dummy2) that simply echo "OK" when ran from command line. 2: At the end of the backup script have them triggered (using the tcmd tool found here https://www.triggercmd.com/forum/topic/196/tcmd-go-command-line-tool-is-available-now) based 1 on a fail and other on a succeed result. 3: In Alexa routines create two, one for dummy1 that Alexa says something like, "Trigger C M D reports script succeeded"
The other for dummy2 that Alexa says something like, "Trigger C M D reports script failed"

This way you can use the same routines and dummy scripts for several different long running scripts and even for scripts that aren't started by TRIGGERcmd

@affa, I'd like to narrow down the problem.

Does it work if you use the Parameters button on the website?
4701b125-7b34-47c8-b4c8-6ab82b380741-image.png

4095952f-1b6d-432b-870b-21e30394ef63-image.png

We should make sure this works before moving on to Integromat.

@John-Gomes , I think one of two possibilities are likely:

You haven't enabled the TRIGGERcmd Smart Home Alexa skill You haven't given your command a voice word.

@Nn-Nn i found my own answer it was a little research for it but it works
i had shamed for this but the answer it was change the parameters of commands to work in this so like : i want open firefox then i go terminal an type firefox and "tada" this work in the parametres thaks.
and i insist sorry for my bad english.

@farol Nevermind. Found it.

@hermes-deus-grego, you can use the shutdown command to turn the Ubuntu PC off - that's the easy part.

The harder part is using another computer on your network to turn the Ubuntu PC on via Wake-On-Lan. I use a Raspberry Pi because it doesn't require much power and it's always on. You could test it using your phone before investing in a Raspberry Pi using this app.

I made this post about using Wake-On-Lan a while ago:
https://www.triggercmd.com/forum/topic/49/turn-on-a-computer

Hi! The "code" command works perfectly on the mac terminal, but may not work on TriggerCMD. In not work, you can also try:

Command: open -a "Visual Studio Code"

@favancini, with the original TRIGGERcmd or TRIGGER command google assistant action, the format of the voice commands are like this: "Hey Google, ask TRIGGERcmd (or TRIGGER command) to run X with parameter Y"

So you could say something like this:

"Hey Google, ask TRIGGERcmd to run album with parameter X." Where X is the name of your playlist.

Your command could run a script that runs your Mp3 player with X as your playlist parameter.

@hlywine, that's awesome! Thank you!

@Ricardo-Horibe, you the background agent adds, removes, and runs background commands. The foreground agent adds, removes, and runs foreground commands.

On Windows you can install the background agent (aka service) like this:

fb0e3a69-72df-490e-a326-bf795c509db3-image.png

Use one of these commands to install the background agent (aka daemon) on Linux:

sudo sh /usr/share/triggercmdagent/resources/app/src/installdaemon.sh
sudo sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.sh (newer Ubuntu OS's)

@kaligora said in Using on Debian Buster:

/root/.TRIGGERcmdData

I see you're not running X-Windows, or you're ssh'ed into your Linux box, so you can't run triggercmdagent because that would try to run the X-Windows GUI agent app.

I see you installed it to run as a background agent though. That's good. You can edit your commands in /root/.TRIGGERcmdData/commands.json. Make sure they have "ground": "background" because the agent running in systemd runs in background mode.

You can run one of these commands to edit that file:

sudo vi /root/.TRIGGERcmdData/commands.json
sudo pico /root/.TRIGGERcmdData/commands.json
sudo nano /root/.TRIGGERcmdData/commands.json