Echo problem on all sound after reboot

1

Hi,

Since a few days I have a strange problem I never had before. Only happens on my master.

When rebooting it, I have every sound repeated several time !
For example, I go to ip:12101 and enter a sentence beside speak button ‘Hello, hope you are fine’
The TTS say something like
Hello hello hel hope ho you are fine fine fine

Same when truggering wakeword, the wav sound is repeated several time.

I have check all I can, nothing fancy. In the log I have only one tts command with one playFinished.

Have check docker, only one image, once container running.

After a few hard reboot, it disappear and all goes fine.

Let me know if you need anything, dunno where to look at.

2

Ok, I duplicated the SD to another Pi for test, same thing.
Of course I updated rhasspy setting, host IP etc

docker image ls, docker container ls, only one running.
with MQTT explorer, only hermes/tts/say message

The echo continue even after hermes/tts/sayFinished

What could I check ?

3

supervisor.conf from fresh start after cleaning

2021-02-15 15:41:13,470 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2021-02-15 15:41:13,478 INFO supervisord started with pid 173
2021-02-15 15:41:14,484 INFO spawned: 'dialogue' with pid 189
2021-02-15 15:41:14,493 INFO spawned: 'speech_to_text' with pid 190
2021-02-15 15:41:14,499 INFO spawned: 'speakers' with pid 191
2021-02-15 15:41:14,506 INFO spawned: 'wake_word' with pid 192
2021-02-15 15:41:14,518 INFO spawned: 'intent_recognition' with pid 196
2021-02-15 15:41:14,537 INFO spawned: 'webhooks' with pid 202
2021-02-15 15:41:14,546 INFO spawned: 'intent_handling' with pid 205
2021-02-15 15:41:14,567 INFO spawned: 'text_to_speech' with pid 208
2021-02-15 15:41:14,589 INFO spawned: 'microphone' with pid 213
2021-02-15 15:41:15,601 INFO success: dialogue entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,601 INFO success: speech_to_text entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,602 INFO success: speakers entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,603 INFO success: wake_word entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,603 INFO success: intent_recognition entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,604 INFO success: webhooks entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,604 INFO success: intent_handling entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,606 INFO success: text_to_speech entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-15 15:41:15,606 INFO success: microphone entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

All sees right there

4

Seems I can’t reproduce it after:

sudo nano /boot/config.txt

=>

dtoverlay=disable-wifi
dtoverlay=disable-bt

Will keep an eye (or two) and let you know

1 Like
5

I can’t remember exactly what I did wrong, but I had something similar when the dialog management was misconfigured and 2 instances handled the dialog at the same time. Then I always got 2 times the same sound.

6

I saw such messages, but I don’t think this is the same problem. Here I can have it 5 or 6 times repeated, but not entire sentence, then another time entire sentence etc, all are at once and tts can’t cope with that, making cut sentences with echo.