@Russ Sorry for being unclear.
Yes the smart home skill.
Ah. So the device name appears to be the Trigger field and as I used the same for both fields all is good I hadn;t grokked that Voice was being ignored.
In fact I eventually found I can use two words for device name (trigger field). You have to be careful as uncommon words can be confused and second words like "play" or "run" can get misinterpreted to do other things as Alexa already handles them.
I do not see "on" or "off" passed as parameters, but the Command or Off Command get invoked as expected. Speaking a number, percent or colour do get passed to either command as a parameter as expected.
The voiceReply seems to be ignored by smart home devices and it always says "OK" unless you use the Alexa App setting to make a noise instead. Is there anyway to get the voice reply to work? I expect as you ignore the voice fields the answer is no
btw I found a useful debugging tool is to add a start to my processing cmd file open a window. eg
start "" echo "[%1][%2][%3]"
That helped me fix an obscure reason some variables were not being expanded when the cmd was invoked from TRIGGERcmd but worked fine from the cmd shell.
Maybe the Runs could show the command return value and outputs to stdout and stderr to help debugging? But that would require more server storage I guess.