@Russ STAR. Yes it was a comma…

Now I ran into another problem I am afraid.
Triggercmd sees the new commands on the webpage and I can trigger them. However no changes are detected by the Alexa skill. I can run all commands I already had via Alexa, but the new ones (which are on triggercmd.com and work) don’t appear as switches. I have removed and reinstalled the skill (the smart home one), but it still detects only the only triggers. Sorry to pester you! Any clue?

Final message, I hope. Now I am back to the starting point: triggercmd works fine on my Pi, but I cannot edit the commands.json file. Every time I edit it, it allows me to save it but then an 'external program' changes it back to a previous version.

Now 'interestingly': if I edit the commands.json.backup and add the new trigger, then when I edit the commands.json it does 'revert' to a previous file... but it is the commands.json.backup file.

Still, the trigger does not show up in triggercmd.com .
All triggers that I have created previously work well

Ok, now reverted back to sd card installation.

systemctl status returns that triggercmd is running.

HOWEVER:

Under my computers it shows as GREEN only if I manually start triggercmdagent from terminal (and I don't CTRL-C out of it). This is with the service running.

With triggercmdagent running there are no triggers listed on the website even though my root triggercmd commands.json has the previous triggers in.

I have tried re inputting the token and re-running installdaemon.sh. Both work without errors, but I still can't make it work as a service.

Can you help please? not sure what's going on - sorry for the many messages.

I cannot actually reinstall it - it was the residual service after dpkg -P.

I tried reinstalling it and it returns this error

If I run npm audit fix --force I continue to have the same issue

Not sure what's happening, could you help please?

Now I have uninstalled it with sudo dpkg -P and reinstalled it and it no longer runs.
When reinstalling when I tried to run 'triggercmdagent' to paste the token, it gives me this error: /usr/bin/triggercmdagent: line 5: /usr/share/triggercmdagent/app/null: no such file or directory

so I skipped to installdamon.sh, which seemed to work fine.
However this is the output of systemctl status triggercmdagent:

Any help please?

I have triggercmd working finr on my Raspberry Pi. I have edited before the /root/.TRIGGERcmdData/commands.json (with sudo nano).

I have changed the internal drive of the Pi from SD to nvme with its own SD cloner. So far I had no problem at all and Trigger CMD continues to work.

However, every time I "sudo nano /root/.TRIGGERcmdData/commands.json" I can add new commands, I can save, but as soon as I exit the json reverts back to the previous one (which is not the default one, it's the one I edited before changing the drive).

I tried to text edit with a gui (sudo mousepad ...) and as soon as I edit the file and successful save it, it says 'external program changed the file, do you want to reload?'

If I stop the service and edit the json the modifications stick until I restart triggercmd service, at that point it reverts back to previous.

Could you please help? I am sure I am just missing something. Perhaps I should just ininstall triggercmd and reinstall it on the pi?

@Russ Ah yes absolutely! Sorry, that's the one. It's because I was unable to access the root folder, so I just assumed it was the other folder. I sudo nanoed it and now it appears instantly many thank you so much

All right, so I followed all the commands in the tutorial and triggercmd and background service installed fine.
Computer is added to my computers on triggercmd.com and all 4 sample triggers show up. However when I edit the commands.json file, the changes don't get uploaded. I added commands and also tried to delete the Gnome editor command, but on the website it just shows the original 4 commands.
I ran sudo systemctl stop triggercmdagent and then start, but they still remain the same.

This is the output of status:

triggercmdagent.service - TRIGGERcmd Agent
     Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; pres>
     Active: active (running) since Tue 2024-12-03 20:48:17 GMT; 6s ago
   Main PID: 10763 (node)
      Tasks: 11 (limit: 9559)
        CPU: 625ms
     CGroup: /system.slice/triggercmdagent.service
             └─10763 node /usr/share/triggercmdagent/app/src/daemon.js --run /r>

Dec 03 20:48:18 raspberrypi env[10763]: (Use `node --trace-warnings ...` to sho>
Dec 03 20:48:18 raspberrypi env[10763]: Write backup completed.
Dec 03 20:48:18 raspberrypi env[10763]:   |>    Now connected to https://www.tr>
Dec 03 20:48:18 raspberrypi env[10763]: \___/   For help, see: http://bit.ly/2q>
Dec 03 20:48:18 raspberrypi env[10763]:         (using sails.io.js node SDK @v1>
Dec 03 20:48:18 raspberrypi env[10763]:          Connected at: Tue Dec 03 2024 >
Dec 03 20:48:18 raspberrypi env[10763]: Initiated command adds
Dec 03 20:48:18 raspberrypi env[10763]: Initiated command removals
Dec 03 20:48:18 raspberrypi env[10763]: { message: 'Subscribed to 674f68f42b0c5>
Dec 03 20:48:18 raspberrypi env[10763]: { message: 'Subscribed to 674f68f42b0c5>

This is the content of my commands.json file

[
  {"trigger":"Reboot","command":"shutdown -r","ground":"background","voice":"reboot","allowParams": "false"},
  {"trigger":"yum update","command":"yum -y update","ground":"background","voice":"yum update","allowParams": "false"},
  {"trigger":"apt update","command":"apt-get -y update","ground":"background","voice":"update","allowParams": "false"},
  {"trigger":"unmount","command":"umount /media/xexets/*","ground":"background","voice":"unmount","allowParams": "false"}
]

Am I missing something?

Thank you!