Alexa Not Recognizing New Trigger Commands? (Updated)
-
Alexa seems to be having trouble recognizing new commands. I put in a simple new command on my computer that's already running 25+ commands. The TriggerCMD skill is enabled and all of my other commands work fine and show up in the Alexa app. Did a "discover devices" and for the life of me, I cannot get Alexa to recognize any additional commands. The one new command comes up as jibberish and is listed as an "Alexa Smart Device." Is there anything going on with the backend server or otherwise that is interfering with Alexa's ability to find new commands?
-
I think I discovered the problem. In the past, you didn't have to put in the optional Alexa voice command when creating a new trigger command. Now apparently you do? If I created a command without the optional voice command, it either would not show up at all in the Alexa device list, or it would show up as garbled text. But if I created a new command and included the Alexa voice trigger as well, it shows up normally when I discover devices on Alexa. Perhaps Amazon changed something on the back end?
-
Now after browsing the forum I see that if you have only one computer running TriggerCMD, you don't have to put in the optional voice command. But if you have more than one, then you have to put that in for Alexa to recognize it.
SO BOTTOM LINE:
-
If you are running TriggerCMD on only one computer, you don't have to put in the optional Alexa voice command when creating a new trigger.
-
But if you are running more than one computer with TriggerCMD, then you have to put in the optional Alexa voice command with every new trigger command. Otherwise, Alexa will not recognize it.
-
-
@dougcolt, sorry for the trouble, but you seem to have figured it out.
Both computers and commands have a "voice" field. Both voice fields need to be populated, except for your default computer's voice field (although it doesn't hurt to populate it). By default, if you have one computer, that computer is your default computer.
