# Core. 20.8.1 “hey .....” wake words are broken, Christopher okay
**URL:** https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196
**Category:** This category is being retired - Support
**Created:** [February 12, 2021, 1:57am UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196 "2021-02-12T01:57:04Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@nnagreg](https://community.openconversational.ai/u/nnagreg)
#### Post date: [February 12, 2021, 1:57am UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196/1 "2021-02-12T01:57:04Z")
Hey All,
I’m a newbie, but a deep techie… I’ve just finished installing the latest version of the stable software PICROFT this evening. I’ve experienced several problems with the WAKE word not responding.
Currently, only ‘Christopher’ is working. - responding sporadic, after repeating 4 times and very slow (after reaching 115 on the meter)
I’ve tried all others, which results in a non-response and the lightening bolt up in the corner. Commands are accepted via the keyboard but non-responsive with wake word.
The log:
:88 Audio contains no data
:341 Creating Wake word engine
:467 Wakeword doesn’t have an entry falling backto old listener config
:467 Loading "christopher’ wake word via precise
:487 Could not found find model for christopher precise
:467 Loading “christopher” wake word via pocketsphinx
:365 Creaing stand up word engine
:467 Loading “wake up” wake word via pocketsphinx
I’ve rebooted several times and attempted to set to default and attempted to change wake word, but still incurring problems.
NOTE: that I have the SUDO password function turned on… Not sure if that’s causing problems.
Any ideas? I’d be happy to try anything and report back what I’m seeing.
Thank you in advance, Greg
---
### Author:  [@baconator](https://community.openconversational.ai/u/baconator)
#### Post date: [February 12, 2021, 6:30am UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196/2 "2021-02-12T06:30:19Z")
Probably better to post the actual contents of the log next time.
You’re not running precise per what you did post, it’s on pocketsphinx instead. As for why, that’s not clear without more information.
---
### Author:  [@nnagreg](https://community.openconversational.ai/u/nnagreg)
#### Post date: [February 12, 2021, 3:41pm UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196/3 "2021-02-12T15:41:36Z")
Attached is a full copy of the LOG:
15:38:32.299 | INFO | 672 | ConfigurationSkill | Remote configuration updated
15:38:34.524 | WARNING | 678 | mycroft.client.speech.listener:run:88 | Audio contains no data.
15:38:34.667 | INFO | 678 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:328 | Creating wake word engine
15:38:34.672 | WARNING | 678 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:341 | Wakeword doesn’t have an entry falling backto old listener config
15:38:34.678 | INFO | 678 | mycroft.client.speech.hotword\_factory:load\_module:467 | Loading “christopher” wake word via precise
15:38:36.827 | WARNING | 678 | mycroft.client.speech.hotword\_factory:initialize:487 | Could not found find model for christopher on precise.
15:38:36.835 | INFO | 678 | mycroft.client.speech.hotword\_factory:load\_module:467 | Loading “christopher” wake word via pocketsphinx
15:38:37.102 | INFO | 678 | mycroft.client.speech.listener:create\_wakeup\_recognizer:365 | creating stand up word engine
15:38:37.115 | INFO | 678 | mycroft.client.speech.hotword\_factory:load\_module:467 | Loading “wake up” wake word via pocketsphinx
---
### Author:  [@nnagreg](https://community.openconversational.ai/u/nnagreg)
#### Post date: [February 12, 2021, 3:46pm UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196/4 "2021-02-12T15:46:52Z")
Everything was set up as default during the install.
“Christopher set listener to Precise” - Fails
16:33:45.852 | INFO | 664 | **main** :handle\_utterance:76 | Utterance: [‘set the listener to precise’]
16:33:49.528 | WARNING | 664 | mycroft.client.speech.listener:run:88 | Audio contains no data.
16:33:49.646 | INFO | 664 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:328 | Creating wake word engine
16:33:49.651 | INFO | 664 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:351 | Using hotword entry for christopher
16:33:49.656 | WARNING | 664 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:353 | Phonemes are missing falling back to listeners configuration
16:33:49.661 | WARNING | 664 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:357 | Threshold is missing falling back to listeners configuration
16:33:49.667 | INFO | 664 | mycroft.client.speech.hotword\_factory:load\_module:467 | Loading “christopher” wake word via precise
16:33:51.963 | WARNING | 664 | mycroft.client.speech.hotword\_factory:initialize:487 | Could not found find model for christopher on precise.
16:33:51.971 | INFO | 664 | mycroft.client.speech.hotword\_factory:load\_module:467 | Loading “christopher” wake word via pocketsphinx
16:33:52.249 | INFO | 664 | mycroft.client.speech.listener:create\_wakeup\_recognizer:365 | creating stand up word engine
16:33:52.257 | INFO | 664 | mycroft.client.speech.hotword\_factory:load\_module:467 | Loading “wake up” wake word via pocketsphinx
Then I went into the GUI website configuration - edit device - set to ‘Mycroft’
16:39:36.460 | INFO | 658 | ConfigurationSkill | Remote configuration updated
16:39:38.130 | WARNING | 664 | mycroft.client.speech.listener:run:88 | Audio contains no data.
16:39:38.319 | INFO | 664 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:328 | Creating wake word engine
16:39:38.325 | INFO | 664 | mycroft.client.speech.listener:create\_wake\_word\_recognizer:351 | Using hotword entry for hey mycroft
16:39:38.331 | INFO | 664 | mycroft.client.speech.hotword\_factory:load\_module:467 | **Loading “hey mycroft” wake word via precise**
16:39:40.847 | INFO | 664 | mycroft.client.speech.listener:create\_wakeup\_recognizer:365 | creating stand up word engine
16:39:40.855 | INFO | 664 | mycroft.client.speech.hotword\_factory:load\_module:467 | **Loading “wake up” wake word via pocketsphinx**
16:40:15.748 | INFO | 664 | **main** :handle\_wakeword:71 | Wakeword Detected: hey mycroft
Does this mean that both (Precise & PocketSphinx) are running?
It appears to work with ‘Hey Mycroft’ now
---
### Author:  [@gez-mycroft](https://community.openconversational.ai/u/gez-mycroft)
#### Post date: [February 18, 2021, 1:58am UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196/5 "2021-02-18T01:58:27Z")
Hey there, both Precise and PocketSphinx run.
In the default configuration for “Hey Mycroft” Precise listens for the wake word, whilst PocketSphinx is used for “wake up”. This is when you tell Mycroft to “go to sleep”. It will then stop responding to queries until you say “Hey Mycroft, wake up”.
It uses pocketsphinx for this so that the utterance doesn’t need to be sent off the device. Hence while asleep, Mycroft won’t send any audio to the speech recognition service.
---
### Author:  [@pcwii](https://community.openconversational.ai/u/pcwii)
#### Post date: [May 8, 2021, 3:00am UTC](https://community.openconversational.ai/t/core-20-8-1-hey-wake-words-are-broken-christopher-okay/10196/6 "2021-05-08T03:00:01Z")
> [@nnagreg](#):
>
> lightening bolt up in the corner
Just a word of warning, this is usually a sign of an undersized power supply and can cause all kinds of anomalies including corruption of the sd card.