I'm using chrome and it worked with the following:
Thank you, Russ!
Thanks. Really loving this app.
In case you're interested, the final application was to automate arming/disarming a home security system for when people arrive or leave the home.
My particular vendor (A-tech security) does not allow integration with home automation systems, like Home Assistant (HA) or SmartThings, but they do allow users to log into their account online to arm/disarm their system.
So, this was the workaround:
Still not working. I tried it with and without a parenthesis around the trigger word - calculator (see below). Neither work.
It looks like the triggercmdagent never gets the order to run; when I review the run count for the trigger, it never changes after I call the service in Home Assistant.
I've confirmed I'm using the same token that's on file at the DAM-UBUVM computer. Do you have any other thoughts?
Tried with parenthesis, as follows:
rest_command: triggercmd_calculator: url: 'https://www.triggercmd.com/api/run/triggerSave' method: "post" content_type: "application/x-www-form-urlencoded" payload: "computer=(DAM-UBUVM)&trigger=(calculator)&token=(MYTOKEN)"
Tried without parenthesis, as follows:
rest_command: triggercmd_calculator: url: 'https://www.triggercmd.com/api/run/triggerSave' method: "post" content_type: "application/x-www-form-urlencoded" payload: "computer=(DAM-UBUVM)&trigger=calculator&token=(MYTOKEN)"
I've inserted this line into my Home Assistant config.yaml file (below), and it does not appear to be running the command at all. The triggercmd agent, running in terminal, doesn't indicate any command is received / executed. I suspect the problem is in the payload line. Of course my actual token is inserted where it should be, indicated by MYTOKEN in the script below.
The title of my trigger, in TRIGGERcmd is "calculator", and it does work, when executed via TRIGGERcmd.
Any suggestions what I've done wrong here:
rest_command: triggercmd_calculator: url: 'https://www.triggercmd.com/api/run/triggerSave' method: "post" content_type: "application/x-www-form-urlencoded" payload: "trigger=calculator&token=(MYTOKEN)"
I'm trying to run a file titled, "Alarm_Arm.html" inside my "Downloads" folder. Nothing is happening. I can confirm the triggercmd agent is open and running, and able to run other triggers/commands. So, I really do believe the problem must be in the structure of this line of code. Any suggestions what may be wrong?
I think the batch file wrote info to the card, but can't remember for sure. I'm hesitant to repeat the experiment right now because the SSD card is configured and running Raspberry Pi OS.
As far as I'm concerned, this is not an active issue for me anymore because I installed it a different way; I should have followed up to let you know. Thank you for looking into it and responding though!
I've got this working now.
Instead of installing using the instructions at "Raspberry Pi Setup", I went to the "Instructions" page and downloaded the deb file and token there. The deb installed the agent to /usr/share/triggercmdagent and the .TRIGGERcmdData folder was placed in /home/pi. Now I can add/edit the commands.json file inside the .TRIGGERcmdData folder and everything works as it should.
After a brief foray with Ubuntu, I'm back to Raspberry Pi OS.
Attempted a Raspberry Pi OS installation loaded with triggercmd, using the method described here: Windows script to prep SD card for Raspberry Pi with TRIGGERcmd agent. But it didn't get past the boot screen.
So, reinstalled triggercmdagent from scratch using original instructions here: Raspberry Pi setup.
Followed those instructions verbatim and triggers still aren't working. In fact, the calculator trigger doesn't work anymore.
Not sure if this is expected to work anymore. My setup gets stuck at the boot screen.