VoxCommando is built upon the Windows Speech Recognition engine and is dependent on your hardware and how you have set it up.
We have integrated every conceivable tool to try to help make it possible for you to configure VoxCommando in a way that will work for you in your environment and with the hardware you have but it is not magic.
Most likely there are things you can do to prevent this issue, but maybe you just need to adjust your expectations of what is possible with a microphone that is always listening when we don't have special hardware with built in keyword detection and an array microphone.
Providing us with a log file is always a good place to start, especially when you are not willing to elaborate on your problem beyond a single sentence. This makes it easier for us to guess what is actually happening. The log file would make it easier for us to determine if you are actually in standby mode, and what your prefix is and what commands are being triggered.
Here are some of the more likely reasons for your issue. It could be one thing or a combination of these things.
1 You are not in standby mode. Prefix mode requires that you be in standby mode to work.
2 The commands being triggered are set as "always on" (these commands work even in standby without a prefix)
3 Your prefix is too short. Make sure it is 3 syllables or more (e.g. "Alexa", "OKAY Google")
4 The command being triggered is too short (e.g. "up")
5 Your input volume is set too high
6 Your microphone has automatic gain control turned on (this turns the input level up extremely high when the room is silent)
7 Your mic has acoustic echo cancellation turned on (this can sometimes create odd audio artifacts)
8 Your required confidence is set too low
9 Your required prefix confidence is set too low
10 Your silent room is not really silent. (Fans, motors, dogs barking, cars driving by an open windows, furniture the microphone is on gets bumped, etc.)
11 Your list of commands is
too short. If you only have a few voice commands then it is much more likely to trigger false positives.
Some possible solutions other than addressing the issues above:
1 - Create a new blank speech profile in Windows advanced speech settings.
2 - Turn VoxCommando OFF completely when not using it, instead of putting it in standby. VC can be turned back on using various methods such as presence detection (e.g. a motion sensor) or with a remote control, keyboard or mouse event etc.
There is an action in VoxCommando called VcAdvanced.SaveRecoWav
see:
http://voxcommando.com/mediawiki/index.php?title=Actions#SaveRecoWavYou can put this action into commands that are being triggered when the room is "silent" and then listen to the wav file to know what VC is actually hearing when it triggers this command.