@dil-photos, not yet, but I'll look into building a 32bit deb file. Stay tuned.

EDIT 12/17/18:
@dil-photos, sorry but I found that they stopped making a 32bit NodeJS version. NodeJS is a dependency for the TRIGGERcmd agent. https://nodejs.org/en/download/

This method has no GUI, but one thing you could try is this. It worked for me.

sudo apt install nodejs-legacy git clone https://github.com/rvmey/TRIGGERcmd-Agent.git cd TRIGGERcmd-Agent node ./src/agent.js --console

@knipknap, nice! That's progress.

I'm not sure why the icon isn't showing. Can you think of anything that's not standard about your xwindows install? It show up for me and I took defaults when I installed Ubuntu Desktop v18

For now you can use some other editor to edit commands.json.

If you want this to load at system boot - be sure to enable the triggercmdagent,service

sudo systemctl enable triggercmdagent,service

@jasoncollege24, I updated the .deb installer. Now it installs libgconf-2-4 or libgconf2-4 depending on which one is appropriate for your specific Linux OS. Please download and try it again.

https://s3.amazonaws.com/triggercmdagents/triggercmdagent_1.0.1_amd64.deb

Also, thanks again for reporting the problem. I need to start watching for and testing the latest Linux releases so I can discover these issues before users do.

@Tiago-Mártires Pretty much the same thing but I added this line to crontab:

@reboot node /usr/share/triggercmdagent/resources/app/src/agent.js &

@Sid-Boswell, no parameters are needed to run the agent in foreground mode. It will find what it needs in your ~/.TRIGGERcmdData directory.

You can install the agent to startup in background mode during boot by running the installdaemon.sh script with sudo.

Please look at this page for more details.

@William-Mendes, you prefix your command with sudo to run it as root. Like this:

sudo /usr/local/bin/yourscript.sh

You'll need to add a line like this to your /etc/sudoers file so the TRIGGERcmd foreground agent can run the commands with sudo without a password prompt:

wmendes ALL = NOPASSWD: /bin/systemctl restart httpd.service, /bin/kill, /usr/local/bin/yourscript.sh

This article does a good job of explaining the sudoers file.

@Kelvin-Ferraz, awesome. I'm glad it's working.

Thanks @pirates. I just fixed it.

@PedroMartins, good. Sorry about the incompatibility.

@russ

I'm using chrome and it worked with the following:

google-chrome /home/dmcnaugh/Downloads/Alarm_Arm.html

Thank you, Russ!

@Smart-Communities, I haven't tried Zorin OS yet. I'm downloading it now. I'll give it a try soon.

I think you installed and ran the TRIGGERcmd agent, but I think you didn't leave it running. So when you tried to run your commands on the computer they didn't run because the agent wasn't running.

Also, that's true - you can't create commands from the website. You have to either edit the text in the commands.json file manually, or use the GUI editor.

These are the Ubuntu instructions. I read that Zorin is based on Ubuntu.

EDIT: I tried it. Unfortunately it didn't work to just run triggercmdagent but you can run it like this in a Terminal window:

Run this first to install nodejs:

sudo apt install nodejs -y

Then you can run the agent in foreground mode like this:

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

You can install the background agent to start as root when Zorin OS boots like this:

sudo su - node /usr/lib/triggercmdagent/resources/app/src/agent.js --console (CTRL-C after pasting in the token) sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.sh

Because that agent is running in background mode, It will only run commands with ground = background in your /root/.TRIGGERcmdData/commands.json file.