Great! I tried to run again and it works Thanks Russ for the prompt attention!

Se você baixou o google drive sync para sincronizar use este comando, o aceita através do exe Eu consegui assim. "C:\Program Files\Google\Drive\googledrivesync.exe"

@echornd, thank you for reporting this! I found the problem and fixed it. I'm sorry. I broke this recently when I was fixing something else. I didn't test thoroughly enough. Sorry about that. You can send parameters via Zapier again now.

@Ivan-Kuler, @Daniel-Millan, you might be interested in this: https://www.triggercmd.com/forum/topic/1531/pass-parameters-with-alexa-routines

@Irfan-Khan, nice. Thanks for testing, and thanks for the original question. I figured it makes sense to block those characters in parameters by default, especially when you give someone a bookmark URL to run your command that allows parameters.

@James-McCarte, the Instructions button on that example links to this page that explains what you need to do to make that command (and others) work. [image: 1628165590807-c0ba6f30-7b98-416d-89d7-db1f23307d6f-image.png]

@Russ Yes, running Windows 10. It's updating immediately now. Maybe some temporary delay. Thanks for your help Russ.

@Beto-Gontijo, EDIT 5/10/2026: As of agent version 1.0.59 you can connect it directly to a HomeKit hub. Original reply: You can use the homebridge-http-switch plugin with a configuration like this. Click the red Bookmark button for the command you want to run, then copy the bookmark URL for the onUrl setting. I recommend a "Short Bookmark" for this use-case because unlike the original Bookmark URL's, they persist, even when you make changes to your commands. You can also change short bookmarks to a different computer/command combo in the triggercmd.com site UI, so you don't have to update the bookmark URL in the homebridge-http-switch config. [image: 1625784860468-34a74b9b-a1ce-4b77-bba7-e63724b4e4b3-image.png] { "accessory": "HTTP-SWITCH", "name": "TRIGGERcmd - Calculator", "switchType": "stateless", "timeout": 500, "onUrl": "https://triggercmd.com/sb?b=blahblah" } [image: 1625784709070-a461eacc-6e74-4c12-9e20-245ddc790878-image.png]

@Matt-Packwood, can you paste a screenshot here? Not sure yet.

@Xander, that's interesting a routine can corrupt on its own. Not good. I'm glad you got it figured out though.

@Russ said in How i can put a delay in a open command?: "C:\Users\KRATUUZ\AppData\Local\Discord\Update.exe" --processStart Discord.exe Okay!!! I will try! Thanks so much!

Hello @Russ, I found out what happened. First when I changed my machine name and then the name in the site's control panel, I don't know why, but the commands that were associated with Alexa's app routines lost their link. I think this is what you mentioned that could break TRIGGERcmd. Alexa interpreted the applied command, but did not open the files and applications. But there was an even bigger problem, because Alexa discovered other new commands associated with the other name I gave my machine, i.e the commands in Alexa were duplicated! I had to delete everything one by one it created. After that, I replaced a backup I had of the TRIGGERcmd commands (commands.json file) and let Alexa rediscover all the commands again. But it still couldn't figure out all the commands at once. I had to re-enable Alexa's TRIGGERcmd skill and ask it to find out the rest of the commands. So to finish, I had to reassociate all the commands again for each routine I had. Finally, with this I don't think to change my machine name anytime soon. It was a lot of work, it took me almost 2 hours to redo the process. In case it happens to someone, that can be of support so that no one gets lost at first like I was. Regards,

@Fast-shop-santa-ursula, currently there's no limit if you're subscribed.

@Ruan-Barros, it looks like it added the Gnome Editor command the first time, and the second time it found that Gnome Editor is the only foreground command in you commands.json file so it didn't need to add anything new - Gnome Editor was already added to your computer in your account. You're running the agent in foreground mode so it will ignore any commands with ground = background. If you click the green Trigger button for Gnome Editor it will probably try to run it. You should see that in your agent output.

@markosjal, on a Raspberry Pi you generally install the agent to run as root and in background mode. So you edit /root/.TRIGGERcmdData/commands.json to add or remove commands. You'll want to set the ground field to background too because the background agent will ignore any with ground = foreground. Please let me know what's working, if anything, like can you run commands using the Trigger button on the website? Have you enabled the TRIGGERcmd Smart Home Skill? Please do try that after you confirm the commands run then you click the Trigger buttons for them on the website.

@dacarle, that's definitely possible. Have you tried using a "bookmark" url? You click the Bookmark button next to the command to generate it.

@Pablo-Rodriguez, I just want to confirm you've checked for the TRIGGERcmd icon in the tray in the lower right after you click the up arrow? [image: 1624568571407-2e9abf3e-e64a-4e2f-8b57-8476d05c9593-image.png] If you see a screen that says it's incompatible, please send me a screenshot. Thanks for the info about Windows 10 x64 - that's important.

@asis-Pal, can you send me a screenshot from Chrome on your phone? That should work. It works for me.