Posts made by Russ

@bluefunoodle311,

Here are some things you can try and check.

First, the fact that your Raspberry Pi shows up in your TRIGGERcmd account on the website means you successfully logged it in with your token, but I'm not sure whether you were logged in as the pi user or the root user. This command is necessary to switch you do the root user:

sudo su -

Also, Gnome Editor is a foreground command ( it has "ground": "foreground" in commands.json ). The fact that you only see that command means you only ran the agent in foreground mode so far.

What you want to do is get the agent running as root in background mode so it starts up as a daemon when your Raspberry Pi boots up.

If triggercmdagent running is running as root in background mode, the commands in /root/.TRIGGERcmdData/commands.json with "ground":"background" will show up on the website.

Please try these commands:

sudo su -
/usr/share/triggercmdagent/app/src/removedaemon.sh
/usr/share/triggercmdagent/app/src/installdaemon.sh

You want to run removedaemon.sh before re-installing it just in case you've installed it wrong somehow.

Also, please run these commands. You should see output like below if it's working.

root@garagepi:~# ps -ef | grep triggercmd
root      7610     1  0 Feb24 ?        00:41:49 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData

root@garagepi:~# systemctl status triggercmdagent
● triggercmdagent.service - TRIGGERcmd Agent
   Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-07-16 23:08:43 UTC; 1min 27s ago
 Main PID: 20448 (node)
   CGroup: /system.slice/triggercmdagent.service
           └─20448 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData

Jul 16 23:08:46 garagepi env[20448]: Logging in with saved token to run background tasks.
Jul 16 23:08:47 garagepi env[20448]: Write backup completed.

@bugtrapper, you should be able to pass multiple parameters by putting a space between them, or a %20 between them, like this:

https://www.triggercmd.com/trigger/bookmark?token=bookmarktoken&params=foo bar

or

https://www.triggercmd.com/trigger/bookmark?token=bookmarktoken&params=foo&20bar

@sulisenator, can you try these things?

• Un-select all of our commands from your TRIGGERcmd SmartApp - hopefully it will let you save the page after that.
• Manually remove any TRIGGERcmd switches the SmartApp may have left because they're associated with other SmartApps, or used in a Routine or something. You'll find the Remove button under the gear under the switch.
• Go back into the TRIGGERcmd SmartApp and re-add the switches you want.

Create a free trial account at twilio.com.

Click the three dots inside a circle icon on the left.

Select Programmable SMS

Select TwiML Apps under Tools

Set your request URL like this:
https://www.triggercmd.com/api/twilio?trigger=LogSMS&computer=DellPC&token=(your token from Instructions page)

Create a batch file (d:\tools\twilio.bat for example) that accepts your parameters. As a test, you could just log the parameters with a batch file like this:

echo %1 %2 %3 %4 %5 %6 %7 %8 %9 >> d:\tools\twilio.log

Create a TRIGGERcmd command that runs your batch file with Allow Parameters set to true.

Docker provides a quick and easy way to package and run Linux software. This also works on Windows if you run Docker on Windows.

Here's how to build and run a Docker container that runs the TRIGGERcmd agent:

Create a text file called Dockerfile with these contents:

FROM ubuntu

RUN apt-get -y update && apt-get -y upgrade
RUN apt install -y nodejs npm wget
RUN wget https://s3.amazonaws.com/triggercmdagents/triggercmdagent_1.0.1_amd64.deb
RUN apt install -y ./triggercmdagent_1.0.1_amd64.deb

CMD node /usr/lib/triggercmdagent/resources/app/src/agent.js --console

To build the container image, cd to the directory where you put the Dockerfile file, then run this command:

docker build . --tag=triggercmdagent

To see your new Docker image in your local Docker cache, run this command:

docker images

To run your new image on Linux and use /tmp as your TRIGGERcmd data folder, run:

docker run -it -v /tmp:/root/.TRIGGERcmdData triggercmdagent

To run your new image on Windows and use c:\mydir as your TRIGGERcmd data folder, run:

docker run -it -v c:\mydir:/root/.TRIGGERcmdData triggercmdagent

When you run it, you'll see it prompt for your token (from the Instructions page):

Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot
Daemon install: false
No token exists.  Login to request one.
prompt: token:

@monty, have you tried xdotool?

https://unix.stackexchange.com/questions/267704/command-to-simulate-keyboard-input

@glauco-keniti-inoue, currently it's not possible, but now that you've asked, it's on my todo list.

@shaun-pillai, if I understand correctly, you probably need to:

1. Install curl from here.

2. Add a TRIGGERcmd command called GarageLightsOn that runs this command:

   curl http://192.168.0.101:3480/port_3480/data_request?id=lu_action&output_format=json&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=57

3. Setup your IFTTT Webhook with these settings:
   Method: POST
   Content Type: application/x-www-form-urlencoded
   Body: token=(your token from the instructions page)
   URL: https://www.triggercmd.com/api/IFTTT?trigger=GarageLightsOn&computer=ComputerName

@mike-cornelison, I suggest you try unlinking and re-linking your TRIGGERcmd account.

Thanks @gauner. I've got the code updated. Would you mind translating this too for the listing in the directory?

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")

@xtropy, will you please trying this as your command?

touch /test/foo

When I ran your command manually, it created a foo file in my current directory, and a /test file in my / directory. I don't think that's the result you're looking for.

When I created a /test fodler, then ran touch /test/foo via TRIGGERcmd it worked - it created a foo file in /test.

Also I think you're aware of this already, but just in case - remember the daemon adds and runs background commands, and when you triggercmdagent interactively, it will run foreground commands.

@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.

@daveola, you should see a new icon in your "tray" the lower right corner of your screen, near the clock. You might have to click the up arrow to see all of your tray icons.

When you right-click that icon you'll see a menu pop up like this:

I saw failure entries in the log like this:

Gassistant: Could not find a trigger called X on Y on Y, sorry.

Google started sending the " on Y" part of the sentence in the trigger field. I added code to parse that out.

Sorry about the issue for anyone who experienced it.

If you ever see problems with TRIGGERcmd, or just have suggestions for improvement, please tell me.

@sulisenator, I'm ready to do the Italian language versions of the Alexa skill and Google Assistant action.

Would you mind translating the text to the right of the = sign to Italian for me?

      cardtitle = "TRIGGERcmd";
      greeting = "Say something like, run Calculator on Office PC.";
      cardgreeting = greeting;
      helpspeech = "When you install a trigger c m d agent on a computer, it will show up in your account at trigger c m d dot com.  Click that computer's edit button to add a voice trigger.  Then you can have alexa run any commands that have voice triggers on that computer by saying, run X on Y, where X is the command's voice trigger, and Y is the computer's voice trigger.  Go to trigger c m d dot com for more instructions.  What do you want to do now?  Say stop if you're done.";
      helptext = "When you install a TRIGGERcmd agent on a computer, it will show up in your account at triggercmd.com.  Click that computer's Edit button to add a voice trigger.  Then you can have Alexa run any commands that have voice triggers on that computer by saying, run X on Y, where X is the command's voice trigger, and Y is the computer's voice trigger.  What do you want to do now?";
      goodbye = "Good-bye";
      pleaselink = "Please go to your Alexa app and link your account.";
      redohelp = "Say something like, run Notepad on Family PC.  You can also say Help.  Say Stop if you're done.";
      nocomputercalledprefix = "Could not find a computer with voice word ";
      tryagain = ", try again, or say Stop if you're done.";
      notriggercalledprefix = "Could not find a command with voice word ";
      onword = " on ";
      triggering = "Triggering ";
      cardtriggering = triggering;
      doesnotallowparams = " does not allow parameters.";
      withparameter = " with parameter ";
      waitaminute = "Wait a minute, or subscribe so you don't have to.";
      launched = "Launched";
      nodefaultspeech = "You haven't set a default computer in your trigger C M D profile yet.";

@erin-leiker, please give this a try:

1. Run this as your pi user to allow root to send stuff to your pi user's Xwindows:

xhost si:localuser:root

2. Install the background service as root with:

/usr/share/triggercmdagent/app/src/installdaemon.sh

3. 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.