No. You just need to place that command in an always enabled command group, such as the core VoxCommands command group.
And the TCP plugin's simple web server needs to be enabled for this command to work.
Here's what is happening:
When you use the Amazon Echo as a microphone, you are using a workaround rather than the standard method of issuing voice commands in VC.
Typically, in VoxCommando we use Microsoft's speech recognition engine to interpret audio directly from a microphone input.
When you use the Echo, you are instead using Amazon's speech recognition, and then you're sending your voice command as a text string to VoxCommando via an http get request.
Two Echo to VC solutions have been shared on the forum. If you're still using the first one, then the http request you're sending to Vox is generating an event called "EchoToVC", which includes two payload values. The first payload is the command, as text.
The command XML in question is triggered by that EchoToVC event.
When this command is triggered, it uses a built-in VC action that
emulates the act of giving a voice command.
That action is
VC.TellVox.
If you double-click on that command in the command tree you can see that line.
In other words, every time you tell Alexa to send a command to VoxCommando, Amazon is sending a text string, and then VoxCommando tries to match that string against a voice command in your command tree.
The problem with this method is that if Amazon's interpreted text is spelled differently than what VoxCommando is expecting, the command will not execute in VC.
This is not an issue when we use a normal microphone input with VC.
