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:

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

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

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?

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?

@Russ Oh boy this is what I was looking for, as I'm getting a new Windows machine tomorrow. Although I'm not sure how many of my switches are v1 and v2 so I guess I'll find out. Thank you for this great upgrade to the code!

Thank you so much for the reply and for the awesome software in general. I'm getting a new PC tomorrow so I had to revisit this topic and confirm this is still the case. I think I have my evening planned now setting up the new virtual switches!

I just installed TriggerCMD on an upgraded computer that controls all of my home audio. I have about 50 different commands already added to SmartThings that used to execute on the old computer. Is there any way to copy all of these commands over to my new computer and not have to re-add everything to SmartThings? I copied the json file no problem so that I have all of the commands on the new computer, but all of the commands show up as new devices on SmartThings. I have the new computer and the old computer named the same.

Any ideas on how this might be done? Thanks in advance!!!!

I've had no problem creating a script to open spotify and start a particular playlist. What I can't seem to figure out is how to control spotify ONCE A SONG IS ALREADY PLAYING. For example, the script below will increase the volume no problem when a song is not playing in spotify. But if something is playing, it's completely unresponsive. Essentially, any SendKeys commands are just ignored when Spotify is playing a song. Anyone solve this issue? Thanks in advance!

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.AppActivate "spotify"
WshShell.SendKeys "^{UP}"