Turn on a computer

Wesley Correa

@Russ First thanks for feedback. see how this triggers however in the cloud appears only GNOME

Wesley Correa

@Russ I changed the IDRAC trigger the ground parameter to foreground and it appeared in the cloud ... but why the IDRAC trigger does not appear when this background

Russ

@Wesley-Correa, the foreground agent adds/removes/runs foreground commands, and the background agent adds/removes/runs background commands. So I think the background agent isn't running.

To install the background agent on the Pi, you'll need to do this:

sudo su -
/usr/share/triggercmdagent/app/src/installdaemon.sh

Then you can check its status like this:

systemctl status triggercmdagent

Wesley Correa

@Russ Okay, but how to identify the output from the command if this is first or second?

Russ

@Wesley-Correa, to capture the output of a command, you can make the command direct "standard out" and "standard error" to a text file like this:

yourcommand &>> /tmp/commandlog.txt

Use a single > if you want to over-write the txt file every time instead of appending to it.

Please explain what you mean by "first or second".

Wesley Correa

@Russ I say that in the trigger parameter it is like {"trigger": "idrac", "command": "/ usr / bin / idrac.sh", "ground": "foreground", "voice": "power on", " allowParams ":" false "},

foreground appears in the cloud, but when you put the background

Russ

@Wesley-Correa, when you switch your command from foreground to background, you can't tell which agent added it just by looking at the website. I suggest adding something to your trigger name to specify background, like this:

{"trigger": "idrac background", "command": "/usr/bin/idrac.sh", "ground": "background", "voice": "power on", "allowParams":"false"},

Then use systemctl status triggercmdagent to see that the background agent added it.

BTW, I got rid of some extra spaces you had in your json entry that might have caused a problem.

Wesley Correa

@Russ Thank you all right now.

Russ

@Wesley-Correa, awesome. I'm glad that worked out.

Wesley Correa

Hello, I intend to create one more command, and share access. in that case I have to create another commands.json?

because the entries created in commands.json I cannot share

Russ

@Wesley-Correa, if you share your computer with another TRIGGERcmd user, all of the commands on that computer are shared.

Are you seeing the commands you created in commands.json on the website?