Notice the "ground":"background" or "ground":"foreground" part of each command in the commands.json data file.
Gnome Editor is a built-in example foreground command, but I don't think Gnome Editor is available on a Raspberry Pi, so that would explain why if you trigger it it doesn't do anything.
I figured most people who use TRIGGERcmd on a Raspberry Pi will likely only be interested in background commands that run in the daemon (aka background service). For example "apt-get -y update".
That said, you can run the agent in foreground mode just by running "triggercmdagent", but you'll want to run different commands than "gedit" (Gnome Editor). If you're running triggercmdagent in an SSH session, you could have it run something like "tail /var/log/messages", and if you're running it in X-Windows, you could have it run a GUI app like "xeyes".
I have an Alexa routine associated with a SmartThings virtual switch, associated with my TRIGGERcmd trigger that runs a command on my Raspberry Pi that tells a relay to complete the garage door button circuit for half a second to signal my garage door opener to open the door. Boom!
Paul Hibbert does a good job of explaining the new Alexa routines here.
I explain the Raspberry Pi / relay hardware setup here, but there are probably better tutorials on setting up a Pi to flip a relay.
This shows how to use TRIGGERcmd with SmartThings.
I've been saying "open sesame" to Google Assistant for a while now. I like Google Assistant because I can use her on my phone, and because it's easier to setup because it skips SmartThings step because Google Assistant shortcuts can be used with any voice command, not just smart-home commands.
If I missed anything in this article, please let me know.
Looks like your connection to TRIGGERcmd Forum was lost, please wait while we try to reconnect.