Better handling intent not recognized


Actually when an intent isn’t recognized we have such log:

[ERROR:42385147] FsticuffsRecognizer: in_loaded
Traceback (most recent call last):
File “/usr/share/rhasspy/rhasspy/”, line 179, in in_loaded
assert recognitions, “No intent recognized”
AssertionError: No intent recognized

This is a python error, meaning bad programming or bug.

For me, an intent not recognized isn’t a bug, but something normal if we ask something that the assistant was not trained for. So this shouldn’t return such traceback but just an info “not intent recognized”.