@Russ Hi Russ! I have created new commands for testing purposes but only the ones that are marked as "foreground" were showing up on the website... So I used the option "remove background services" and then "install background services" and right after that the background commands appeared on website.... Not sure what happened, maybe something was stuck and cleared by itself after the reinstall...anyway, it's working properly now!! Thank you for all quick support, really appreciate that!
Best regards

@Igor-Marinho, Alexa talks to the TRIGGERcmd servers, and the TRIGGERcmd servers talk to the agents. Next time, please test the agent first by running your commands from the triggercmd.com website. If that works, there's no need to troubleshoot the agent and you can move on to troubleshooting the Alexa integration. Also if you do have an agent problem, instead of uninstalling/re-installing it, you should try restarting it.

We can troubleshoot Alexa after you re-install the TRIGGERcmd agent and test it from the triggercmd.com website.

Please try deleting your C:\Users\(your user)\AppData\Local\triggercmdagent directory, then re-install the TRIGGERcmd agent. Hopefully that will work around the installation error.

@Smart-Communities, you could install the background service and make your commands background commands. Then they'll run in the context of the TRIGGERcmdAgent Windows service.

f683db7c-3ad3-4144-9c6b-5db1c47c9024-image.png

4dd69c6c-2590-455c-bf91-848d720392f2-image.png

9329ed07-e07b-410f-b78d-dcc50bb58fb8-image.png

@marti-ruiz, the parameters you send with your trigger always get tacked on to the end of your command, so you should put that same command in a .bat file if you want the parameter where the %1 is.

Your TRIGGERcmd command would run your .bat script like this:

b4ae43ca-f277-436a-b9b3-143288f9c973-image.png

Your label.bat script contents:

type "C:\BC\%1" > \\mycomputer.local\ZEBRA

@Russ so the short URLs act as a redirect. Thanks Russ.

@El-Kortungas, what does it show in your Runs list for the command? I just ran Calculator using the TRIGGERcmd Smart Home skill and it ran only once as you can see here:

63868947-3086-4a59-a7fc-5087967a20a4-image.png

Also, which Alexa skill are you using? The runs list will show that too. I recommend the TRIGGERcmd Smart Home skill.

You could try unlinking and re-linking the skill.

@matheus-venancio What is the actual command that you're using? And does it work from a cmd prompt?

@Mike-Vecchiarelli , can you send me a copy of your debug.log file?

I wonder if you see multiple instances of something like this:

|> Now connected to https://www.triggercmd.com. \___/ For help, see: http://bit.ly/2q0QDpf (using sails.io.js node SDK @v1.2.1) Connected at: Fri Mar 15 2024 18:24:00 GMT-0400 (Eastern Daylight Time)

Also, can you tell me the versions of the agent on your 4 computers? If they're different, that could be a clue.

Also, I have better logging now, so I can probably track down the server logs related to your issue if you give me the time and your computer ID or account email address if/when it happens again.

@Russ I signed out/closed the app and then opened it up again. See the below screenshots of the developer mode enabled and add device page.

Developer mode enabled:
ST1.jpg

Cannot see "My Testing Devices":
ST2.jpg

I appreciate your assistance. Thank you.

@Bruno-Rafael Look through recent posts for NirCmd instructions. It can simulate key presses but I don't know that a virtual press will suffice.

If it does, simply create an Alexa routine with both actions (and you'd probably want to throw a Wait command in between)

@Russ
It worked. The error was in credential.json, TRIGGERcmd couldn't find the file, so I entered the data directly into the python file.

Good job. Thanks for the help my friend.

@Xander, there's no official x86 TRIGGERcmd agent version. If you updated agent.js, you've got the latest functionality.

can anyone help with this?

@eromano resolved by a new install from zero.
Maybe the problem was that at the first execute was already present another machine