Turn on a computer

[Wesley Correa]

@Russ I'm trying to connect a DELL R420 through IDRAC using IPMI, I created .sh to run through TRRIGERCMD I added the content to json but it doesn't appear in the cloud. the existing triggers are working normally ... just mine that add doesn't show.
is running on raspberry py B + with Debian 10 buster.

I bought an eco dot + I am waiting to arrive and use Alexa but I need to solve this could you help me please?

is running on raspberry py B + with Debian 10 buster

[Russ]

@Wesley-Correa, I see some problems in your poweron trigger. The command path should start with a / (slash), ground should be background assuming you're running the background service, and the voice field should have a space because Alexa and Google probably won't match what you say to "poweron". It should be like this:

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

If you run triggercmdagent from the command line like that, it runs the agent in foreground mode. If you want to test it that way, change ground to foreground, but in general I use the background service with a Raspberry Pi.

[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?