@warrisr, I don't know yet. I'll have to try this myself.

Their site seems to be down. I'll have to try some other time.

@hellomiakoda, when I uploaded the .deb file last time I updated it, apparently I forgot to make it public.

@hellomiakoda, thanks for telling me. Please try again. It should work now.

@yen-gálvez, here are some ideas:

If your Trigger buttons on the web work, you probably don't need to do this, but to start over, you don't need to uninstall the TriggerCMD agent. Instead, just delete the computer from the website, and delete the .TRIGGERcmdData folder from your user's home folder. That's c:\users\(youruser)\.TRIGGERcmdData on Windows. Then close the TRIGGERcmd agent (right-click the tray icon, Quit), and re-open it. At that point it will recreate your .TRIGGERcmdData folder and re-prompt for a token.

It doesn't matter that the token from the Instructions page changes. Any token from that page is as good as another.

Also, the token you want to use with IFTTT is from the instructions page, not the bookmark token.

@decio-accietto, when I tap the compass in the lower right, it brings up an "Explore" page with a search field. When I type Triggercmd in that field, I see two options: TRIGGERcmd and TRIGGER command. You can pick the one you like better. Some people prefer to say Trigger Command instead of Trigger C M D.

Do you not see those when you search?

Sorry @fernando-mateos-lopez. I will get to it soon.

EDIT 4/20/19: I just submitted the Spanish version of the Alexa skill. It's called "Ejecuta Comando". Now we have to wait a few days for them to give me feedback. I usually don't get everything right the first time, so it will probably be about a week to get feedback and fix whatever is wrong.

@phil-tanguay, I do plan on implementing that ability soon, now that I've added the SendResult script to the .TRIGGERcmdData folder to send a result of a command back to the server.

Currently the result just gets logged in the Runs log for the command.

It's on my todo list.

Bubba did a great job explaining the process in his videos, but here's a summary of the process for X10 users:

1. Plug one of these into your PC’s USB port.
2. Install and run this software (do not change the port from 6003 to 8086).
3. Setup an X10 switch as A3.
4. Create a TRIGGERcmd account
5. Install the TRIGGERcmd agent (bottom of the page)
6. Install curl for Windows
7. Create a batch file with these contents:

if "%1"=="on" curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~%%22A3%%20on%%22
if "%1"=="off" curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~%%22A3%%20off%%22

7. Use the TRIGGERcmd agent software to create a TRIGGERcmd command that runs the batch file,
   a. Enable parameters (for on and off parameter).
   b. Fill in the Voice field with “kitchen lights” or something similar depending on what the A3 switch is for.
8. Link the Alexa TRIGGERcmd Smart Home skill to your TRIGGERcmd account.
9. Use the Alexa Web app to Discover devices.
10. Say, “Alexa, turn on kitchen lights.”
11. Say, “Alexa, turn off kitchen lights.”

Also, here's a video on the new Alexa TRIGGERcmd Smart Home skill.

@jebus-jones, please try again. It should work now. I'm sorry it took so long to fix. I put some details about the problem here:

https://www.triggercmd.com/forum/topic/399/is-the-goolge-home-triggercmd-app-working

@atmosphere, sorry I missed your post until just now. Can you confirm your phone is logged into the Home app as the same google user your Google Home uses? Also, can you try again today? If you were using the Trigger Command action (instead of the Trigger CMD action), that might explain it because there was a problem with the Trigger Command action until today.