Thank you @mallea ! Merry Christmas!

@dlaugh14, your example is way cooler than mine.

@rexabbot, no, but if you want to run foreground commands that launch GUI application like a browser, you can open a terminal window within X-Windows, and run triggercmdagent. That will run the agent in foreground mode.

Unfortunately you won't be able to use the GUI editor though, so you'll have to edit the commands.json file manually with vi or pico.

@Joost-Breggeman said in Command script not working - Raspberry?:

{"trigger":"Hello World","command":"sudo /home/pi/tmp/test.sh","ground":"foreground","voice":"update","allowParams": "false"}

nevermind... found it. there should be an absolute path to the text file in the script

@bzowk ,

That should have worked. Background commands are elevated commands by default because they run in the context of the Windows service that runs as Local System.

I have a background command called "Restart Print Spooler" that runs:

sc stop spooler & sc start spooler

I just tested it on my Win10 box and it worked. I have UAC turned on though, so maybe that's the difference.

EDIT 7/4/21:
Check out this solution too: https://www.triggercmd.com/forum/topic/1453/questions/2

Now there's a better way to run the agent on a 32bit version of Windows:

https://www.triggercmd.com/forum/topic/99/no-gui-triggercmd-agent-that-works-on-32bit-windows

Now there's a better way to run the agent on 32bit Windows.

https://www.triggercmd.com/forum/topic/99/no-gui-triggercmd-agent-that-works-on-32bit-windows

@kingdavid52, thank you for telling me I had this issue.

I found that the Ubuntu installation instructions didn't work unless you were in X-Windows.

I updated the instructions here.

I don't want Ubuntu users to have to install the X-Windows GUI, so again, thank your for pointing this out!

Awesome @Brandon, nice job.

@Neflhiem, I'm glad you got it working. I like how it turned out too. Thanks again for your questions - I wouldn't have thought to implement this if you hadn't asked.

@Russ thanks

Also, the server I'm using this on hid the task bar icons, so it was a little while before I realized there was a place to right-click and pull up a GUI editor =P. The directions on your website are not incorrect.

Both German Alexa skills are live now!

https://www.amazon.de/VanderMey-Consulting-LLC-TRIGGER-command/dp/B074TV61DK/
https://www.amazon.de/VanderMey-Consulting-LLC-TRIGGERcmd/dp/B06XFN2TZN/

If you confirm they're working fine, please tell your friends. 🙂

Thanks again for all your help @MarcusV!

@zayaan, I'm glad we could figure it out.

FYI, for everyone else - he was able to fix it by deleting the contents of his c:\users\(username)\.TRIGGERcmdData folder. Then when he ran the TRIGGERcmd Agent, it re-prompted for a token and re-created his computer in his account.

In hind-sight he should have backed up his commands.json first (oops).

Ask and you shall receive. Now you can search the forum.

@Nate-Hales, did a quick google search and found one of the topics that have been around a while, so apparently they're indexing it.

@Jim-Potash, in your Alexa app it shows you what Alexa is hearing you say, so you can use that to match your voice words for your computer and your command.

The word "reboot" for the command should be no problem, but you might have better luck using a different voice word for the computer.