@al-mastro, awesome. You're welcome. I'm glad that worked.

@MarkW, awesome. I'm glad that worked.

@jaysimhb, I'm sorry, for security reasons, I built TRIGGERcmd to never store the actual commands in the cloud, so you would need access to your old laptop.
For the future, you'll want to keep a backup of this file:

%USERPROFILE%\.TRIGGERcmdData\commands.json

For example:
c:\Users\russ\.TRIGGERcmdData\commands.json

@hellomiakoda, how can you tell it's timing out? Is that what it says in your %userprofile%\.TRIGGERcmdData\debug.log file?

Can you confirm you're running Windows 10 and the latest version of the TRIGGERcmd agent?

TRIGGERcmd is working fine for me, and a lot of other people. I've updated my Windows 10 PC to the latest updates. I'm also using the latest version of the TRIGGERcmd Windows agent.

These are a couple things you could try:

You could try removing and re-installing the agent. Some antivirus software breaks the TRIGGERcmd agent. You could try disabling it temporarily to see if that makes it work. You could reset your data with these steps:
a. Rename your %userprofile%\.TRIGGERcmdData folder
b. Go to this page https://www.triggercmd.com/user/computer/list and delete your computer.
c. Right-click your TRIGGERcmd agent tray icon and click Quit
d. Re-run the TRIGGERcmd Agent and log it in.
e. Copy your commands.json file from your backed up .TRIGGERcmdData folder to your new .TRIGGERcmdData folder to restore your commands.

@russ Jeeze 20 days ago, sorry for my late reply.

Thanks for getting back to me.

Unfortunate, it's driving me nuts haha.

Keep up the great work 🙂

@jpe81 and @batteryxsnare, thanks to @Royski, now Hubitat is supported.

https://www.triggercmd.com/forum/topic/494/hubitat-integration

@Atmosphere, I just found out this problem was on my end. There was a bug in my logic that triggered in cases when Google sent the computer word along with the trigger voice word. I'm sorry! Anyway I fixed it, so you might need to switch back to using pool instead of poo or pooll.

Also, thank you for reporting it. I feel bad that I blamed this on Google when it was my fault.

@alon Figured it out.

I had "<< >>" around each parameter ... that somehow broke it ... removing the escaping fixed it.

@shubi, I could create another Alexa skill using a different 2 words. If I do that, what words do you think I should use?

I did this for English a long time ago because people didn't like having to say Trigger C M D and thought it would be better to say Trigger Command.

@abdi-abdi, can you give me details? What did you say, and what did Google say back?

@ben-noble, you might be missing the fact that when you install the TRIGGERcmd agent, you'll get a new icon in your "tray" in the lower right corner of your screen. You can right-click that to find the GUI Command Editor where you can add and remove commands. I'm assuming you're using Windows?

0_1563722507658_b942b3df-7c50-430a-b6de-c46cef9b850f-image.png

When you add commands, they should show up in your account under your computer at www.triggercmd.com.

Please let me know if you got that far.

Boom! Awesome @bluefunoodle311 !

Thank you 🙂

@sulisenator, can you try these things?

Un-select all of our commands from your TRIGGERcmd SmartApp - hopefully it will let you save the page after that. Manually remove any TRIGGERcmd switches the SmartApp may have left because they're associated with other SmartApps, or used in a Routine or something. You'll find the Remove button under the gear under the switch. Go back into the TRIGGERcmd SmartApp and re-add the switches you want.

@monty, have you tried xdotool?

https://unix.stackexchange.com/questions/267704/command-to-simulate-keyboard-input

will do thanks

@glauco-keniti-inoue, currently it's not possible, but now that you've asked, it's on my todo list.

@shaun-pillai, if I understand correctly, you probably need to:

Install curl from here.

Add a TRIGGERcmd command called GarageLightsOn that runs this command:

curl http://192.168.0.101:3480/port_3480/data_request?id=lu_action&output_format=json&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=57

Setup your IFTTT Webhook with these settings:
Method: POST
Content Type: application/x-www-form-urlencoded
Body: token=(your token from the instructions page)
URL: https://www.triggercmd.com/api/IFTTT?trigger=GarageLightsOn&computer=ComputerName