Slow dialogmanagement in 2.5.9

Help
1

I’ve a well running Rasspy installation with 2.5.0-pre on which the dialoghandling is very fast. in the MQTT explorer I can see following timing:

hotword --> hotword detected 10:32:00
asr --> startListening 10:32:00
asr --> textCaptured 10:32:04
intent --> SchalterIntent 10:32:04

Now I try to setup the same system with 2.5.9. The System ist running but very slow. The timing is now
hotword --> hotword detected 10:15:11
asr --> startListening 10:15:12
asr --> textCaptured 10:15:15
intent --> SchalterIntent 10:15:17

I use the same satellite for both systems.
Are there any ideas what is causing this bad timing ?

Thx!
Martin

2

Hi @Martin_Maier, welcome back.

Do you have feedback sounds enabled? Later versions of the dialogue manager paused to wait for the beeps to play in order to avoid the ASR/wake systems picking it up.

1 Like
3

Hi @synesthesiam

I only use nearly the same profile.json on both machines:
{
“dialogue”: {
“satellite_site_ids”: “192.168.178.33,192.168.178.34”,
“system”: “rhasspy”
},
“intent”: {
“satellite_site_ids”: “192.168.178.33,192.168.178.34”,
“system”: “fsticuffs”
},
“microphone”: {
“system”: “pyaudio”
},
“mqtt”: {
“enabled”: “true”,
“host”: “192.168.178.49”
},
“sounds”: {
“system”: “aplay”
},
“speech_to_text”: {
“satellite_site_ids”: “192.168.178.33,192.168.178.34”,
“system”: “kaldi”
},
“text_to_speech”: {
“satellite_site_ids”: “192.168.178.33,192.168.178.34”,
“system”: “espeak”
},
“rhasspy”: {
“listen_on_start”: false
}
}

this profile will be used by a standard docker installation of rhasspy.
So I didn’t any other configurations.

THx!

4

Hi @synesthesiam

I’ve just removed the sounds entry from profile and restarted docker but it’s the same behaviour as before. As satellite I use a respeaker 4 setup with snips as wakeword and hermesledcontrol. On the 2.5.0-pre the recordindication lights immediately after the wakeword was detected on 2.5.9 this happens after feeled 2 seconds.

5

Hi @synesthesiam
so finally I’ve found the solution. It’s not enough to disable the “Intent Handling”, you also have to empty all wav-file entries. After save and restart the satellite works as expected and the profile entry is changed to:
“sounds”: {
“error”: “”,
“recorded”: “”,
“wake”: “”
},

Thx! Martin

1 Like
6

Thanks for the follow-up :+1:

I’ve marked your last post as a solution for others to find in the future.