@Mateo-Fernandez, yes, unfortunately you'll need to make it faster. Alexa only gives a few seconds before a reply must be returned to Alexa, so TRIGGERcmd has to impose the same time limit.

@Emanuel-Esteves, in your user profile folder, there's a subfolder called .TRIGGERcmdData, for example:

C:\Users\russe\.TRIGGERcmdData

In that folder there's a commands.json and a computerid.cfg file. If you put the ID of the old computer in the computerid.cfg file, it will login as that computer. The commands.json file contains your commands, so if you still have a copy of that, you'll be able to restore your commands. Otherwise, you'll need to rebuild your commands. When your computer logs in, it synchronizes the commands in commands.json with the computer record in your TRIGGERcmd account.

To find the ID of your old computer, you can click View Triggers for that computer, then you'll see the computer ID in the browser URL:

I hope this helps. Sorry if this means you lost your commands and you need to rebuild them. At least you have a list of them in your account in the old computer record.

@Mateo-Fernandez, will you please try changing the action to this?

Alexa, pedirle Ejecuta Comando ejecuta saldo.

I think it might need to be in Spanish, unless you already know you're able to say to your Echo Dot, "Alexa, ask trigger C M D to run saldo" and it works.

@Thiago-Soares, which Alexa skill did you link? You need to link the TRIGGERcmd Smart Home skill for Alexa devices to appear for each of your commands. Your commands also need to have the voice field filled in. Your computer also needs the voice field filled in or it needs to be your default computer. You can set your default computer in your profile.

@Brunera-EL, one of the advantages of the background service is it runs before you login. It also runs background commands as root on Linux.

If you create a background command, does it show up on the website? If so, that means the background service is working. Please try changing the ground setting on your shutdown command to background, and try running it before you login. It should work.

@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.

"2021-08-26 19:54:08 Program: About to install to: C:\Users\User\AppData\Local\Discord"
"2821-08 1-26 19:54:21) Apply 21 ApplyReleasesImpl: Updating shortcut C:\Users\User\Desktop\Discord.Ink"

@Igor-Marinho Looks like you're installing Discord, not TriggerCMD.

@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.

@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:

Your label.bat script contents:

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

@Smart-Communities, if you give the new device the same computer name, the short bookmarks should still work. They specify a computer name and trigger name.

Normal bookmarks specify the trigger ID so those stop working if you even change certain fields in the trigger, like the name because that deletes and recreates the trigger with a new ID.