Thanks Russ. That worked. I was trying various commands like trying to run "nano" and it didn't pop-up so figured there were bigger issues at play. Since I am not running in an X environment, I'm assuming the commands run in a random virtual console? I was running foreground to get visibility and troubleshooting from the logs. I just modified the commands.json line for this to background and started the daemon and this also worked. Not a lot of documentation for using triggercmd via command line (ssh) and most is focused on the GUI so fumbling may way around . Thanks again for the reply. Now that I know commands are running correctly, I'll play around with the scripts I want to run. Great program BTW

@russ said in Alexa Skill in Italy: TRIGGERcmd is a cloud service that allows you to securely and remotely run commands on your computers. Your commands could install updates, reboot, run a script, or anything else you decide. Login at www.triggercmd.com. Download and install an agent on your computer. It will prompt for the token during the install. Go to the Instructions page in your triggercmd.com account, and copy the token. Paste the token from the Instructions page into your agent to log it in. Your computer will now show up in your www.triggercmd.com account. Click Edit and add a voice trigger to your computer. Add the TRIGGERcmd skill in your Alexa app. Link your Alexa account to your TRIGGERcmd.com account. Say: Alexa, open TRIGGERcmd. Say: run Calculator on Office (use your own computer's voice trigger instead of "Office") TRIGGERcmd è un servizio che ti permette di impartire comandi in remoto ai tuoi computer in piena sicurezza. Puoi installare aggiornamenti, riavviare il PC, avviare uno script o qualsiasi cosa di cui tu abbia bisogno. Effettua il login su www.triggercmd.com. Scarica ed installa il client sul tuo computer. Ti verrà richiesto un token durante l'installazione. Vai sulla pagina Instructions del tuo account triggercmd.com e copia il token. Incolla il token quando richiesto dal client per collegare il tuo account. Il computer appena associato verrà mostrato nel tuo account www.triggercmd.com. Clicca su Edit e aggiungi un trigger vocale al tuo computer. Aggiungi la skill TRIGGERcmd alla tua app Alexa. Connetti il tuo account Alexa al tuo account TRIGGERcmd.com. Dici: Alexa, apri TRIGGERcmd. Dici: apri Calcolatrice su nome_computer (dove nome_computer corrisponde al trigger vocale impostato nei passaggi precedenti)

@hansen-w, good, I'm glad you figured it out. Some day I might write a proper Android app, but for now the app just loads the login page from the website, which causes a problem with Google authentication.

@daveola, no, that's the name of the Google Assistant action or Alexa skill. You could use the alternative called "Trigger Command" instead.

@daveola, I think I'm due for an update to that Youtube video. I'll make sure it's more prominent in the new recording. The desktop icon the agent installs on the desktop just runs that tray icon, so that doesn't help much.

@erin-leiker, please give this a try: Run this as your pi user to allow root to send stuff to your pi user's Xwindows: xhost si:localuser:root Install the background service as root with: /usr/share/triggercmdagent/app/src/installdaemon.sh Make sure this variable is set when your command runs as root in the context of your triggercmdagent: export DISPLAY=:0.0 Your agent will be running in background mode, so the commands need "ground": "background" to run that way. I suggest testing with galculator. It's an xwindows calculator app.

@atmosphere, wow, I'm glad that was it because I had no idea what I could do about that.

@bobrdavies, I'm glad you found it - yea the forum is a separate system so you have to use a separate account.

@kuldiin, I got an email that Amazon approved it for UK (and CA, IN, AU). If you like it, please rate it . I think the Alexa TRIGGERcmd Smart Home skill is one of the best ways to use TRIGGERcmd because it recognizes your words so well, and all you have to say is, "turn on calculator."

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

@muvvala-g, I use Jenkins too, so I can put together an example if you want, but here's some quick research I did so far: https://jenkins.io/doc/book/managing/cli/#common-commands It looks like Jenkins gives you a command-line tool that can run jobs. EDIT: I tried it out and it works pretty well. My command looks like this: java -jar jenkins-cli.jar -s http://localhost:8080 -http -auth admin:PASSWORD build MyJob -v -s Also, I downloaded the jenkins-cli.jar from my own Jenkins server with this command: wget http://localhost:8080/jnlpJars/jenkins-cli.jar Does that accomplish what you're trying to do?

@veepueco, if you run it from a cmd prompt does it work? Also, can you send a screenshot of the file name and path, and paste the contents of your script below?

@veepueco, I don't think that's possible. You can still run commands while the screen is locked, but you won't be able to see the result until you manually unlock the screen.

@batteryxsnare, please wait to delete and re-create your switches. You'll want to install the new smartthings smartapp code first. I'm almost done with it. I'm working on it now. Thanks for offering to do a review. Also I checked, and you're not subscribed yet. For future reference, if you're subscribed, you'll see this in red on the instructions page: You're already subscribed. Thank you for your support! And for clarity, I just added this text to the instructions page if you're not subscribed: You're not subscribed yet. EDIT: It's done. Now the SmartThings switches are tied to the commands via the computer name / command name combo, so you can move your commands to a new computer, name the computer the same as the old computer (in the web gui), and you won't have to re-create your SmartThings switches. Thanks for the suggestion. I should have done that a long time ago. To use the new SmartApp code, you'll need to remove your switches, login to the SmartThings IDE, and update the SmartApp code to use the new V2 code, then re-add your switches. BTW, if you're an Alexa user, you can get similar voice experience without SmartThings with this skill.

@strahan, the connection is made from the agent on your computer to the TRIGGERcmd servers via that IP. That doesn't mean traffic only has to flow in that one direction. In that IFTTT scenario, IFTTT sends a web request to the webhook on one of the TRIGGERcmd servers, and the TRIGGERcmd server your agent is connected to tells the agent to trigger the command.