Ok @js, you could change your commands.json to this:

[ {"trigger":"Monitor","command":"/root/monitor.sh","ground":"background","voice":"Monitor","allowParams": "true"} ]

And put this in your /root/monitor.sh script:

#!/bin/bash if [ "$1" = "on" ] ; then echo Turning it on vcgencmd display_power 1 fi if [ "$1" = "off" ] ; then echo Turning it off vcgencmd display_power 0 fi

And say this to Alexa or Google Assistant:

ask TRIGGERcmd to run monitor with parameter on

Or use the TRIGGERcmd Smart Home Alexa skill or the SmartThings integration with Google Assistant, and say this:

turn on monitor

Okay, the command lines you provided work, and I also changed my command word to just "shut" so Alexa can recognize it better. Overall, thanks a lot for helping me, TriggerCMD is definitely a great tool for the raspberry pi.

@Jack-Bailey, what will steam.py do? Anyway here are some steps you'll need to do. Let me know if you get stuck on any of them.

Create your steam.py file and test it. Install the TRIGGERcmd agent on your Raspberry Pi and test it using one of the built-in commands. Run this to install the background service so it starts when your Raspberry Pi boots:
/usr/share/triggercmdagent/app/src/installdaemon.sh Add your python3 steam.py command to your /root/.TRIGGERcmdData/commands.json file. Something like this:
{"trigger":"steam","command":"python3 \/root\/steam.py","ground":"background","voice":"steam","allowParams": "false"}, Test it using the green Trigger button on the TRIGGERcmd website. Go to ifttt.com and create your Button widget / TRIGGERcmd applet that runs your command. Long-press the IFTTT app icon and select Widgets, and place your button widget on your home screen.

@Alfredo-Guzman, you have to switch yourself to the root user before you can edit that file.

This command will switch to root:

sudo su -

@Russ Works now, thanks!

@Russ Thnx for the information i' will give it a go as soon as i will have alexa dot....still waiting due to the whole situation. But I understand what you are trying to say so i will test it and i have have an issue i will post it here. Thnxx again man.

I just updated the scripts that TRIGGERcmd runs to have full paths, and now it works, thanks!

Very cool. Thanks @Sébastien-Pineau. I'll let you know if I get this working.

@Andy-Kutruff, try this one. I just pushed it:

docker pull rvmey/triggercmdagent:arm

You'll need to create an actual computer record in your account and get the ID for it from your browser's address bar after you click view triggers.

@steve-porter yep that will mess things up. I remember reading another post about that so that isn't something that you alone have experienced. I found a couple times the file didn't update for me for different errors in command lines.
I've gotten into the habit of double checking if it saves.

@zed-master, if you can install nodejs on it, you should be able to run the agent.js with a command like this:

node agent.js --console

You can find the agent code at https://github.com/rvmey/TRIGGERcmdAgent

@dean-mcnaughton, nice. Good job getting it working.

It all worked out! Thank you very much Russ, you helped me a lot.@russ

@riccardo-cereser, please try adding this to your script:

SCRIPTDIR=$(dirname "$0") cd $SCRIPTDIR

That way you can specify the full path to your script in the commands.json file, and when your script runs, it will cd to the directory where your script is.