Always debug/log raw text

Would it be possible to always see in the interface log, the raw text listened ?

Actually when an intent isn’t recognized we have this:

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

Would really help to see what the asr listened to help debug intent sentences.

Looks like a duplicate of Add raw_text event when intent is not recognized

Alternatively, the ASR output is logged with DEBUG level.

1 Like

Is it possible to play a sound when there is no intent recognized?
It is very helpful to understand whether you need to repeat command or not

I’ve got a start on this. Should be able to get it finished up tomorrow.

1 Like

I think this is done

1 Like