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

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

@Russ oh man, what bad news are these...! ok, let's do it from scratch again then... and I now will save a copy of my .json file in my dropbox...

thanks for the prompt answer!

@Firas-Frikha , do you have a question?

@Mariana-Castro, if you didn't save your c:\Users\(your user)\.TRIGGERcmdData\commands.json from your previous Windows load, you've lost your commands.. You should delete your computer from your TRIGGERcmd account so you can recreate it from your new Windows load.

For security reasons, TRIGGERcmd does not store the actual commands in the cloud - they only exist on your computer in your commands.json file.

@Mauro, there's no built-in way to open the GUI Editor using a command, but if you want I could build it into the next version of the agent.

I remember you did it this way, so I assume you're looking for a simpler/cleaner method.
https://www.triggercmd.com/forum/topic/2716/macro-to-open-triggercmd-gui?_=1718324644863

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

44363ede-f14b-41a3-891c-131f4deefc66-image.png

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.

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

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

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

@StealthNet, yes, good idea. To avoid that problem when you update next time you could exclude those two folders.

@Russ Yea i use the Smart Home Skill, like it much more
Ill stick with the Routine way, it aint that bad
Thanks again!

@Furkan-Cevik, nice, I'm glad you got it working. Also, thank you for subscribing!

@Russ thnk you, deleting and submitting again worked! Best,

@Strahan, that should work.

Do you see an Alexa device called "bedtime" in the Alexa app?
667c86ef-d339-433a-acd2-c9d521cb6e3c-image.png

FYI, you could also remove the on and off portion of the command, and clear the "Off command" field like this because the agent will add " on" or " off" to your command depending on whether you're flipping the virtual switch on or off.

Trigger: bedtime Command: c:\misc\loghealth.bat bedtime

At first I was concerned that bedtime might be a reserved word, but I tried "bedtime" and "bed time" in the Voice field and both worked for me.

82dfaf50-a9a4-4549-9f78-e8001a91b436-image.png

@h6477801471, ok, if you put MultiMonitorTool.exe in d:\tools, then make your command this:

d:\tools\MultiMonitorTool.exe /TurnOff 1

Or you could do this so you can say, Alexa, turn monitor off, and Alexa, turn monitor on.
978faec6-3792-4b24-83b9-f78eb6bed2a6-image.png

If you specify the path (d:\tools) to the .exe file in your command you don't have to put d:\tools in your PATH variable.

If you want, you could turn the projector on and off with a smart plug instead. You'd create 2 commands, and associate each one with an Alexa routine that flips the smart switch off and on. The problem is I don't think you're supposed to abruptly turn projectors off because the fan needs to run to cool the bulb down. I'm not sure though if that's still a concern these days.

I made a video about how to run Alexa routines when you trigger your commands here:
https://www.youtube.com/watch?v=nrqj-OwDpGE

Also I forgot to ask, does it work if you run the command manually from a cmd window?