NluIntentNotRecognized notification gets stuck until a new event occurs

Help
1

Something strange started to happen in my setup a few days ago. When I say the wake word and not say anything after, I can only see the HotwordDetected event in the logs. And only when I say the wakeword again after some time, I can see the NluIntentNotRecognized of the previous listening appear in the logs.
Before, I used to get NluIntentNotRecognized notification right after the listening stops.
Here’s an example log:

[DEBUG:2023-02-06 15:54:30,008] rhasspyserver_hermes: Sent 115 char(s) to websocket
[DEBUG:2023-02-06 15:54:30,001] rhasspyserver_hermes: Sent 281 char(s) to websocket
[DEBUG:2023-02-06 15:54:29,998] rhasspyserver_hermes: <- HotwordDetected(model_id='/profiles/hi/raven/namaste/example-1.wav', model_version='', model_type='personal', current_sensitivity=0.55, site_id='default', session_id=None, send_audio_captured=None, lang=None, custom_entities=None)
[DEBUG:2023-02-06 15:54:22,165] rhasspyserver_hermes: <- NluIntentNotRecognized(input='', site_id='default', id=None, custom_data='namaste', session_id='default-namaste-92e6f1dd-5a01-4f8f-8953-4a62ea393c54')
[DEBUG:2023-02-06 15:54:15,237] rhasspyserver_hermes: Sent 115 char(s) to websocket
[DEBUG:2023-02-06 15:54:15,231] rhasspyserver_hermes: <- HotwordDetected(model_id='/profiles/hi/raven/namaste/example-1.wav', model_version='', model_type='personal', current_sensitivity=0.55, site_id='default', session_id=None, send_audio_captured=None, lang=None, custom_entities=None)

In the logs above, the first listening ends with the line [DEBUG:2023-02-06 15:54:15,237]. When it detects the second wake word that I say after some time, it logs the previous intent result at [DEBUG:2023-02-06 15:54:22,165] and then goes on with the new HotwordDetected event.

Other related things I noticed are:

  1. the problem doesn’t occur when I wake rhasspy with the wake button on the panel.
  2. Somehow browsing in the rhasspy panel (like opening sentences or configuration or restarting the system) invokes the awaiting intent recognition result.
  3. The problem doesn’t occur when an intent is correctly recognized

I need to solve the issue as I have another application listening through websocket that needs the intent recognition result to do some actions. In the case that no intent is recognized I am playing a special audio.

Thanks in advance