Hi Russ,

The problem, as you suspected, was that I did not run sudo su -. I followed the steps you laid out in your previous post and did indeed profit :).

Thanks for your help.

Hi,

What i tried and failed to explain was I did edit the commands.json, but that was failing, so to rule out my changes I reverted to the default commands.json.

I added the log lines you suggested and got the following output (at the end of the journalctl command):

I went back to the computer management portal and my computer was still listed. I wanted to delete and re-register the computer, so to do that I:

• deleted the computer from the portal
• refreshed the page to verify it had gone
• stopped the agent via sudo systemctrl stop triggercmdagent
• re-ran triggercmdagent
• re-entered the token
• made sure the computer was now listed in the Computer Management, which it was
• restarted the service via sudo systemctl start triggercmdagent
• checked the output via systemctl status triggercmdagent

and got the same error:

I am not sure why the service believes the computer has been deleted when it was registered in this same session only a minute or so before.

Hi Russ, Thanks for the quick reply.

It is the commands.json in /root/ that i am editing. When I edited it to contain the two background commands I want, I got 2 errors. When I did a fresh uninstall and install, so the commands.json in /root/ had 3 background commands, I got 3 errors. This is my as output as my PI is currently:

Thanks again for taking the time to help with this.

Hi,

Hopefully you can help me. I am trying to use triggercmd to trigger a couple of commands on my Raspberry Pi 3 via Alexa. I actually got one of the commands working at one point but was having some trouble with the syntax of the other. Anyway, after a few attempts I worked out the syntax but whenever i try to upload the commands i get the "Failed while trying add a trigger" error.
Looking at the machines in Computer Management the machine is listed, but there are no triggers.
I have tried deleting my machine from the triggercmd computer management view and re running triggercmd from the prompt. When i enter the token the machine re-appears in the computer management view so machine registration seems to work.
I double checked the commands.json file and there were no spurious commas, the last line had no comma. I got two "Failed to add..." errors - which matched the number of triggers i had (both background). To try to rule out my json, I copied the default file, with the 4 triggers in (3 background and 1 foreground) and re ran the installdaemon.sh. Again everything seemed ok but checking the status (via systemctl status triggercmdagent) I can see 3 "failed while trying to add a trigger" errors, probably corresponding to the 3 background triggers it is trying to use. As a final attempt i tried uninstalling the software (via the removedaemon.sh script, removing the machine from the computer management page, then reinstalling, again I get the 3 errors.
To me this points to an error on the server rather then the client, but aside from deleting a machine, it is somewhat of a blackbox to me.

Can you think of anything else i can try?

Thanks