@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