@Tesla-Fahrer, sorry, at this point the agent cannot connect to the TRIGGERcmd server through a proxy.

@Russ

Thank you so much, Russ.
I just subscribed your software.

It is awesome on windows 10 and works.

@prik-m, what determines the number of computers is how many you have in your computer list.

So if you could run the agent on computer A, and use computer B to edit computer A's commands.json file somehow, then you'd only be using one computer (A) according to TRIGGERcmd.

@Russ That works, thank you!

@Ananda, the error is saying you must subscribe before adding an additional computer. You must have a computer in your account already. If you delete it, or subscribe, you won't get this error.

The subscription allows you to have more than one computer, and run more than one command per minute.

@Russ thanks for the quick reply. I tried it out and it worked perfectly. Thanks again

@Russ The tray icon was there but it was unclickable. When I deleted those folders and the PC from my computer list on triggercmd admin, I was then able to reinstall and everything then worked as it should.

@gingerslayer113 (or whom it may concern)
I've used automagic4android(.com) bc of its scripting ability, so this looked quite interesting to me:
Google Home WOL Configuration -
https://www.youtube.com/watch?v=iD6lCh7Uhq8

Similar to a4a looks MacroDroid, and, bc also mentioned within the above video: Tasker

Good luck 👍

@caio-augusto, I read this at the bottom of this page:

wuauclt is no longer available with Windows 10.
You can use usoclient.exe instead.
Parameters are /StartScan, /StartDownload, /StartInstall

I tried it and it doesn't give any output, but I assume it works. I'll have to try it when my PC needs updates. I tried it on a couple of mine but both are up-to-date so it didn't do anything.

@russ thank you for your fast reply. I really appreciate it. The firewall was blocking the commands indeed. If I try use them before login, everything works properly. But after login, when the firewall comes up, every command stop working.

@emristv, good. Yea you either need that or your computer needs to have a voice word set, but it's better to use the default computer so you don't have to say the computer's voice to Alexa.

In other words, if you use the default computer, you can say, "Alexa, turn on calculator"

If you just set the computer's voice word to "laptop" or something, then you'd say, "Alexa, turn on calculator on laptop"

@matheus-zarpellon , you have to delete your computer from your account at TRIGGERcmd.com first.

@chabetico, your commands were stored in the commands.json file in C:\Users\(your user)\.TRIGGERcmdData\commands.json. If that file is gone, you'll need to recreate your commands from scratch. For added security, the actual commands are not stored in your account in the cloud. They're stored on your computer.

@Irfan-Khan, I hope you'll share your end product when you get it all figured out.

@Kevin-Diehl, if you deleted the .TRIGGERcmdData folder it should prompt for a token again.

Maybe a reboot would help.

@Gerardo-Lasso, I think you might have two accounts, and your computer is associated with the other account.

You could delete the C:\Users\(your user)\.TRIGGERcmdData\token.tkn file, then close and re-run the TRIGGERcmd Agent. That will prompt for a token again and you can give it a token from this account. That will create the computer record in this account.

@Arturo-Gracia-Maqueda, I sent you a message here.

Your actual commands are never uploaded to the TRIGGERcmd servers. I consider it a security feature, but I can see how it might be helpful if there was a backup of that commands.json file. I might consider offering an opt-in way to send backups of the commands.json file to the servers.

Oh, sweet @kellanist. I just answered you on the other thread. I'll link that one here.

@Elmer-Dogy, you can delete your token.tkn file from your .TRIGGERcmdData folder in your home folder. Your home folder is c:\Users\(your user) on Windows.

After you delete that, the next time you run the agent it will prompt you for your token again.