@Jim-Potash, in your Alexa app it shows you what Alexa is hearing you say, so you can use that to match your voice words for your computer and your command.
The word "reboot" for the command should be no problem, but you might have better luck using a different voice word for the computer.
FYI, for everyone else - he was able to fix it by deleting the contents of his c:\users\(username)\.TRIGGERcmdData folder. Then when he ran the TRIGGERcmd Agent, it re-prompted for a token and re-created his computer in his account.
In hind-sight he should have backed up his commands.json first (oops).
Also, the server I'm using this on hid the task bar icons, so it was a little while before I realized there was a place to right-click and pull up a GUI editor =P. The directions on your website are not incorrect.
@Neflhiem, I'm glad you got it working. I like how it turned out too. Thanks again for your questions - I wouldn't have thought to implement this if you hadn't asked.
That should have worked. Background commands are elevated commands by default because they run in the context of the Windows service that runs as Local System.
I have a background command called "Restart Print Spooler" that runs:
sc stop spooler & sc start spooler
I just tested it on my Win10 box and it worked. I have UAC turned on though, so maybe that's the difference.
