32 Bit GUI TriggerCMD Editor

Russ

@a-mcf, that is so awesome!! Nice job.

This is what it looks like.
myTRIGGERcmd

André Ricardo da Costa

@A-McF I have a mini PC Minix Neo Z64 32 bit with windows 10 installed. I tried to download this file on my mini pc and the following error appeared: Run-time error "76" Path not Found. Could you help me? I really want to make Trigger CMD work on my mini PC. I'm waiting. Thank you.

André Ricardo da Costa

@Russ
323/5000
I have a mini PC Minix Neo Z64 32 bit with windows 10 installed. I tried to download this file on my mini pc and the following error appeared: Run-time error "76" Path not Found. Could you help? I really want to make Trigger CMD work on my mini PC. I'm waiting. Thank you.

Russ

@André-Ricardo-da-Costa,

The normal Windows installer doesn't work on 32bit Windows. If you still want to try to make it work, this is the process:
https://www.triggercmd.com/forum/topic/99/no-gui-triggercmd-agent-that-works-on-32bit-windows

That 32bit agent doesn't come with a GUI, so you can use @A-McF's 32bit GUI TriggerCMD Editor to edit your %USERPROFILE%\.TRIGGERcmdData\commands.json file, or you can just edit it with Notepad.

André Ricardo da Costa

@Russ First, thank you very much for your feedback. I have good news! I followed exactly the instructions from the link you gave and after some work I was able to install the CMD Trigger program on Windows 10 32 Bit. The calculator, Notepad, Explorer, Mspaint, Wmplayer successfully worked with Alexa! I was able to find the file with the basic commands inside my user's folder and make some edits and on the Trigger CMD website and Alexa recognizes the commands. But, in the tests I did, only the calculator, Notepad, Explorer, Mspaint, Wmplayer actually work. I tested the programs that can be opened by CMD using the Start command followed by the name of the program. What do I have to do to make other programs work with Trigger CMD?
I still haven't managed to get the on the computer to run the Zoom Mettings app and Chrome. Do you have any suggestions to help me? I'm excited about it. Thank you very much for your help and for your excellent program. I will help you to promote it more in Brazil.

[
{"trigger":"Reboot in 10 seconds","command":"shutdown /r /t 10","ground":"background","voice":"reboot"},

{"trigger":"Calculator","command":"calc","ground":"foreground","voice":"calculator"},
{"trigger":"Notepad","command":"notepad","ground":"foreground","voice":"notepad"},
{"trigger":"Zoom","command":"zoom","ground":"foreground","voice":"zoom"},
{"trigger":"Google Chrome","command":"chrome","ground":"foreground","voice":"chrome"},
{"trigger":"Explorer","command":"explorer","ground":"foreground","voice":"explorer"},
{"trigger":"Wmplayer","command":"wmplayer","ground":"foreground","voice":"wmplayer"},
{"trigger":"Mspaint","command":"mspaint","ground":"foreground","voice":"mspaint"}
]

Russ

@André-Ricardo-da-Costa, I replied to your post here.

Also, thank you for promoting it in Brazil. I've actually noticed a lot of new users in Brazil recently.

Emanuel

Hello guys! I am not able to use the 32 Bit GUI TriggerCMD Editor.

When I try to open the application this window appears:
Captura de Tela (23).png

Can someone help me?

Russ

@Emanuel-Ferreira, this probably means there's something wrong with your commands.json file. You could try starting out with a simple one like this:

[
 {
  "trigger": "Notepad",
  "command": "notepad",
  "ground": "foreground",
  "voice": "notepad",
  "allowParams": "true"
 }
]

Emanuel

@Russ I still can't use the 32 Bit GUI TriggerCMD Editor interface, but I can add the commands through the "commands.json" file and everything works just fine. The only problem is that every time I turn on the computer, I have to run the triggercmdagent.bat file or the commands will not work. Do you know how I can solve this? I also can't open Chrome, I don't know why. I checked the controls and everything is fine but it doesn't work.

Thanks in advance!

Russ

@Emanuel-Ferreira, if you copy your triggercmdagent.bat file to this folder, it should run when you login:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

Can you copy/paste your commands.json entry for chrome? I'd like to see your command.

Emanuel

I copied the file triggercmdagent.bat and now it works, thanks!

I managed to solve the problem that Alexa did not open Chrome, the script looked like this:

{"trigger": "Google Chrome", "command": "start chrome", "ground": "foreground", "voice": "chrome", "allowParams": "false"}

Thanks for your help! : )

Emanuel

Hello @Russ!

I'm having some problems with Skill ... A few days ago the command stopped reaching the computer. The "smart home devices" that I put on still appear on the Alexa app. I did not tamper with any settings on my computer. The command is simply not enough.

So I deleted it and registered my pc again on the site but it didn't work. I can only solve this when I uninstall the Trigger skill and install it again. There it works for a while until it appears in the file "triggercmdagent.bat":

Captura de Tela (181).png

Then it even says that the connection came back (since it did not fall) but the commands do not work at all.
This message keeps repeating itself.
I've tried several things here but I can't solve it.
Can you tell if this is a bug in the skill? Or is there a way to solve this permanently?

Russ

@Emanuel-Ferreira, if you don't use the skill and just use the Trigger buttons on triggercmd.com website does it run the commands?

You should confirm that works before working on the Alexa skill. We need to determine if the problem is between Alexa and the server or between the server and your agent.

Your screenshot only shows a 2.296 second disconnect between the agent and the server, so it seems that might not be related.

If you see that the commands run fine from the website, then please try changing your voice word on one of your commands. That should delete and re-create the Smart Home device in the Alexa app.

Emanuel

@Russ The commands were working on the site, I did what you said and it worked.

Thanks!