I’m facing this problem:
- user say with normal voice “Turn off the ceiling light”
- ASR detects “Turn off”
- All lights in that room goes off
Sometimes - but not so often - ASR do understand “Turn off the ceiling light”.
When I’m saying “normal voice”, I mean a voice that is strong enough for all other commands. A vast majority of the commands and queries works as expected and are understood correctly.
If I raise the voice and make an effort to minimize the delay between “Turn off” and “the ceiling light” it is more likely to understand.
I have tried to modify the endpointing rules Is it possible to modify the default timeout on no response from the user
I’m on 0.61.1, so I had 5 rules: I increased 1 and played with rule 2-3-4 , longer time and higher cost. I noticed that it took significantly longer to get the response from ASR so I guess the values were accepted.
However this didn’t seem to change the behaviour, ASR is till truncating the command to “Turn off”.
In the assistant I have no training example with just “Turn off”. There are quite a few (10%) starting with “Turn off”.
“Switch off/on” and “Turn on” suffers from a similar problem.
How can I address this problem?
It is a commercial product and users are very likely to start playing with “Turn on/off” commands so I really would like to fix it.