Build an open future with us.

Invest in Mycroft and become a community partner.

No sound on wakeword recognition


#1

Mycroft (Picroft) detects wake word but doesn’t make a confirmation noise. I’ll say, “Hey Mycroft” and will hear total silence, but if I go on to give a command, it’s responsive.

How do I set the wake word sound?

Derek


#2

Hi there @DerekCaelin, I’m ruling out a volume issue here because the volume is OK when Text To Speech activates.

The Wake Word file itself is stored at;


ie - on your Picroft you’ll find the WAV file for the Wake Word “ding” at this file path.

Has this been modified at all?

Your logs may also have some clues as to why the Wake Word sound isn’t “dinging” - if the Raspberry Pi can’t play the WAV file for example then it may not play - for example if a library or a package is missing.


#3

I had this problem and did a little digging…

For some reason the ~/.mycroft/mycroft.conf had been changed to confirm_listening false.

Change it to true and the problem is solved.


#4

Hi folks,

Thanks to you both. I attempted to solve via @cbxbiker61’s solution but my mycroft.conf file doesn’t reference “confirm_listening”.

{
“play_wav_cmdline”: “aplay -Dhw:0,0 %1”,
“play_mp3_cmdline”: “mpg123 -a hw:0,0 %1”,
“enclosure”: {
“platform”: “picroft”
},
“tts”: {
“mimic”: {
“path”: “/usr/local/bin/mimic”
}
},
“ipc_path”: “/ramdisk/mycroft/ipc/”,
“hotwords”: {
“hey mycroft”: {
“module”: “precise”
}
},
“SkillInstallerSkill”: {
“path”: “/opt/venvs/mycroft-core/bin/msm”
},
}

I haven’t touched the “wake word” file, either.

Will keep poking around…


#5

Hey @DerekCaelin is this still occurring for you?


#6

I ended up reinstalling picroft. At this point, my mic is no longer detected, so technically this issue is resolved! :slight_smile:


#7

Oh, technically resolved, but not exactly a great outcome!
What sort of microphone is it? Anything in the error logs?