@Alejandro-Lopez, you can use the same TRIGGERcmd account, but if you don't have the commands.json file from your c:\Users\(username)\.TRIGGERcmdData folder, you'll need to recreate your commands because that's where they were stored. For security reasons, they're not stored in the cloud.

You'll need to delete your old computer from your account because unless you're subscribed you can only have 1 computer.

@Russ looks like its been stable! thank you!

@HENRY-BADU, 32bit Windows isn't supported, but people have made it work with these instructions:

https://www.triggercmd.com/forum/topic/99/no-gui-triggercmd-agent-that-works-on-32bit-windows

@rkstormer, thanks for your patience. I'm glad we got it figured out.

FYI, this typo was the problem with the SmartApp code. This commit fixes it, so you can upgrade to the latest version of the code now and it should work fine.

https://github.com/rvmey/SmartThingsPublic/commit/354a7bd74ae911197433c476f0c59c1dba5de91a#diff-cf70bb620d755db3e5a6ede5fd18e43d1b639309fa4e7b63c3e2e9222b2b3992

@Steve-Gardinier, are you trying to pair the tcmd command line utility? That's the only use for the pair code so far.

You use the token on the Instructions page to login the agent on your computer, or the Android TRIGGERcmd Widgets app.

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.

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

34a74b9b-a1ce-4b77-bba7-e63724b4e4b3-image.png

{ "accessory": "HTTP-SWITCH", "name": "TRIGGERcmd - Calculator", "switchType": "stateless", "timeout": 500, "onUrl": "https://www.triggercmd.com/trigger/bookmark?token=eyJhbGciOi....." }

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.