@mega_big, on a Raspberry Pi, assuming you installed the agent using these instructions, your commands are in this file:

/root/.TRIGGERcmdData/commands.json

You'll see the default commands in there.

You can run these commands to edit it:

sudo su - cd /root/.TRIGGERcmdData nano commands.json

While the agent is running, it will detect changes in that commands.json file and create/remove triggers for those commands in your TRIGGERcmd account. If you mess up the json at all (an extra comma even), the agent will restore the last backup it took. You'll see that in your debug.log.

If you don't want to deal with editing text, you could create a command on your Windows PC using the "GUI Command Editor" then copy/paste the json text of that command from the "Text Command Editor" into your commands.json file.

@jcksnftsn, awesome.

@Al-S, do the new commands have a voice word? That's required for the skill to create devices.

@Al-S, great. Glad that was it.

@sparker, TRIGGERcmd Smart Home is an Alexa skill, not something you install on your phone, so now I'm not sure if you're talking about the TRIGGERcmd iOS or Android phone app.

I wonder if you logged into your account using the "Login with Google" button? If so, you'd need to set a password in your profile page before logging into the phone app with a email/password. The phone apps allow you to use a pair code to login, so you could also try that instead.

If you're talking about the Alexa skill, you could try enabling it on you computer instead. If you use the same browser where you're logged into triggercmd, it won't even prompt for login when you enable the skill.

@Russ ty!!

Russ, is there any other information that you need or anything else that I can do or provide to help determine what to do to get my commands.json commands into TRIGGER.cmd on my RasPi Zero W?

@hogkite, you're welcome.

I just updated the Mac agent too.

@riccardo-cereser, please try adding this to your script:

SCRIPTDIR=$(dirname "$0") cd $SCRIPTDIR

That way you can specify the full path to your script in the commands.json file, and when your script runs, it will cd to the directory where your script is.

It all worked out! Thank you very much Russ, you helped me a lot.@russ

@dean-mcnaughton, nice. Good job getting it working.

@zed-master, if you can install nodejs on it, you should be able to run the agent.js with a command like this:

node agent.js --console

You can find the agent code at https://github.com/rvmey/TRIGGERcmdAgent

@steve-porter yep that will mess things up. I remember reading another post about that so that isn't something that you alone have experienced. I found a couple times the file didn't update for me for different errors in command lines.
I've gotten into the habit of double checking if it saves.

@Andy-Kutruff, try this one. I just pushed it:

docker pull rvmey/triggercmdagent:arm

You'll need to create an actual computer record in your account and get the ID for it from your browser's address bar after you click view triggers.

Very cool. Thanks @Sébastien-Pineau. I'll let you know if I get this working.

I just updated the scripts that TRIGGERcmd runs to have full paths, and now it works, thanks!