@dan5150, wonder if you might have multiple TRIGGERcmd accounts, and your Alexa account is tied to the other TRIGGERcmd account?
Just brainstorming here.
If so, you could try unlinking and re-linking to your account.
EDIT: We figured it out - Dan had "shut down /s /t 30" as his command but he needed "shutdown /s /t 30". Notice the shutdown command shouldn't have a space it in. There's a shut down command in the Example commands BTW.
@bruceybizzit, I think you should try either checking your debug.log file for clues, or deleting your computer in the web gui, and deleting your c:\users(username).TRIGGERcmdData folder. After deleting those, when you run TRIGGERcmd again it should prompt for the token.
@wadeal, the point of the voice property of your computer is to specify something you can say to Alexa that makes it easy for her to recognize. So I recommend something simple in your computer's voice field like, "movies"
Alexa/Google Assistant/Cortana don't use the computer's name field, they use the voice field to find your computer.
Click the blue Edit button for your computer on the website to get to that voice trigger field.
For some reason I ran into the same problem when I said, "Alexa, tell Trigger CMD to open movies". Alexa identified "movies" as the name of a computer for some reason.
This phrase worked better: "Alexa, ask Trigger CMD to run movies"
I'll see if I can "train" Alexa to understand the previous phrase better.
EDIT: I see I never implemented "to open" with Alexa. I'll look into adding that, but you can only use these for now:
EDIT 2: There's something strange about how Alexa handles the word movies, so I'd avoid using it as a voice trigger for your command. I've been trying to tell Alexa to recognize movies as a command and she just won't.