@vitormbn , if you run the same command from a CMD window does it work? Error code 1 means it's running the command but it's failing. Ideally it will fail in the same way so you can see the error. One possible reason for the failure might be you don't have admin access on your machine.

@Russ Done. Will keep you in the loop.
Thank you!

@Tony-Seaback

I replied to you here, but basically I broke the background service in version 1.0.45. I just need to upgrade the node version and update the agent. I'll do that today. Stay tuned.

https://www.triggercmd.com/forum/topic/3227/background-agent-commands-not-syncing-or-service-not-starting-please-assist-please-thank-you

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@Tony-Seaback, I replied to you here, but basically I broke the background service. I just need to upgrade the node version and update the agent. I'll do that today. Stay tuned.

https://www.triggercmd.com/forum/topic/3227/background-agent-commands-not-syncing-or-service-not-starting-please-assist-please-thank-you

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@Tony-Seaback, I see the problem. I broke the background service in this latest version 1.0.45. I'll produce a new version today and get back to you.

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@Tony-Seaback, I see from your other posts you're using the background service. I assume the foreground service is sync'ing foreground commands just fine?

I just found out the background service is broken on Windows version 1.0.45. I'm working on the fix now.

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@theotherclub, your second computer needs to have a "Voice Name" before Alexa will create devices for each of that computer's triggers.

89b6ddc2-f582-41fb-b8cb-330509f9e9ba-image.png

Your first computer doesn't need a Voice Name because it's your default computer by default.

This page in the documentation explains further:
https://docs.triggercmd.com/#/./SmartHomeSwitches

@Mark-Hollis, your commands are not stored in the cloud. They're only stored on your computer, so if you don't have a backup of your commands.json file, you'll need to recreate them. One Windows you can find your commands.json file in this folder:

c:\Users\(your user)\.TRIGGERcmdData

If you're not subscribed, you'll need to delete your current computer before you can create another one.

@atroguer
Yes if you setup a autohotkey and use the spy to get the x and y mouse coordinates u can

In TriggerCMD gui
“C:(path to autohotkey)” -play “C:(path to autohotkey script)”

Use ChatGPT, to help you make the autohotkey script

On desktop make a txt document
Copy and paste AHK script from CHATGPT to document
Save as
MyScript.ahk
File Type. ALL

@Russ I got it.
The issue was due to that I havent gotten really logged in, for some reason after clicking the validation link it showed like I was logged in. I logged off and input my credentials again and I could find averithing in place.

Thanks

Awesome @Santiago. Thanks for letting me know. Sorry about the trouble.

@Russ Thanks for getting me started.
Also meant to post commands must be URL encoded even though it isn't a URL.
Verbal command would be something like "Alexa, turn Loft Lights 40 [percent]

@Abel-Boby, do you see a list of voice commands on this page?

You should have one voice command for each of your triggercmd commands that has a voice word, but only if the computer is your default computer or it has a voice word assigned to it. You can set your default computer on your profile page.

In other words, these are the requirements for creating virtual devices in Google Home for your commands:

Each command must have a voice word. Each computer must have a voice word, or it must be your default computer.

@jcksnftsn, awesome.

@ess__gabriel, I remember now. Tray icons no longer work by default, so you have to install this Gnome shell extension: https://extensions.gnome.org/extension/615/appindicator-support/

@steef-van-der-Poel If you want to run a .jar executable, you need to run it using java. This is best done with a batch script like the following file:

Batch Script (launch.bat) cd C:\Users\steef\Desktop\minecraftServer java -Xmx1024M -Xms1024M -jar minecraft_server.1.21.4.jar > log.txt 2>&1

Your TriggerCMD command would have to be executing the .bat file

Something like this would work, the command comes from Minecraft's site:
https://www.minecraft.net/en-us/download/server

a66cf93e-d25e-4307-8d9a-ba761eec8e5c-image.png

@Floor_kicker Thank you very much for helping.

@eromano, I tried to install OpenWRT on a VMWare VM for a while. I got version 15 installed using an OVA but I couldn't get openssl working, so I couldn't install nodejs etc on it.

Anyway, I noticed your error output shows it's trying to access a URI that starts with /engine.io . That's not valid URI.

I wonder if you've upgraded socket.io-client beyond the version specified in ubuntupackage.json because this article says the latest version 'socket.io-client@4.X.X uses /engine.io instead of the valid /socket.io URI.

@Hugoboss, sorry, I missed your original post so I'm glad you followed up.

For the 2 examples that won't run in the triggercmd agent, you said they won't run now, but they ran fine yesterday. Did you upgrade the agent between when they ran and when they didn't?

Do they run fine if you run them manually from a cmd prompt?

Please try putting this one in a .bat script like this, and run the .bat script as your command instead:

cd /d "C:\Users\username\AppData\Local\Programs\UiPath\Studio" UiRobot.exe execute --process "Discord.Join.Server"

Please test the .bat script manually too.

Also could you share the contents of this script, and the output when you run it manually?

"C:\Applications\UiPath\Robot\Starta Spel\Starta Spel\Start Game.bat"

@Matheus-de-Souza, it's showing "Command ran with error code 1" because your command is failing. Commands return error code 0 when they succeed.

To troubleshoot, it would help to get the output of your command. You should be able to see the error if you run it manually from a cmd prompt.

To open a cmd prompt, you can hold the Windows key and press R, then type cmd and press enter.
9a53f208-d7ed-45ee-b14b-dec1f499230d-image.png

If the command runs fine in the cmd prompt but it fails when you run it with the TRIGGERcmd agent, you should copy/paste your command into a .bat file and redirect the command's output to a log file, and change your triggercmd command to run the .bat file. That way you can look in the log file to see the error.

For example, you could create a script.bat file with these contents:

yourcommand > c:\logs\script.log 2>&1

This part is to make stderr output go into your log, not just stdout: 2>&1

Notice I put the log file in a c:\logs directory. You'll need to create that directory first. Windows won't let you write to a file in c:\ by default.