[ Respeaker Core V2.0 ] Snips unresponsive once an intent has not been recognized #60
Comments
I've confirmed this as well on Respeaker Core v2. Was able to reproduce under 60.8, Once an unknown intent, responses are no longer recognized. In my case, I have to restart all services to have recognition back. respeaker@Livingroom:~$ sam status Connected to device livingroom OS version ................... Debian GNU/Linux 9 (stretch) Service status: snips-analytics .............. 0.60.8 (not running) respeaker@Livingroom:~$ respeaker@Livingroom:~$ sam watch |
Hey guys, I cannot reproduce your issue on version 0.61.1 using the weather demo assistant. If it occurs again on your side, please re-ping us on the forum. |
I am facing a problem with Snips. The Chain works well until an intent is not recognized or the ASR captures an empty string.
The hotword is not triggered anymore and not even a
sudo systemctl restart snips-hotword.service
solved the problem. I have to restart the 'snips-audio-server.service' to get back on track.I am using a Respeaker Core v2.0
Here are the logs when an empty string is detected and the audio service is restarted
The text was updated successfully, but these errors were encountered: