ok, i deduct that you have skipped the local mimic build during setup.
Yet the tts module is set to âmimicâ, not âmimic2â. try to change that.
that said, you shouldnât do this in mycroft-core/mycroft/configuration/mycroft.conf,
this is what the .mycroft/mycroft.conf (user) resp. /etc/mycroft/mycroft.conf (system) are for
Ok we got somewhere⌠so I entered your 2 liner and rebooted.
Starting in debug mode now mycroft responds but not in the wake word. So in example if I write in the terminal set timer he asks " how long of a timer? " and if I tell him â5 minutesâ he starts the timer.
Any ideas? Should I keep this thread here or open a new one for the wake word?
the wake word is detected, but without confirmation output it seems. aplay some wav file. Iâm guessing mimic 2 is sending mp3 (which is played with mpg123)
yet this
2020-11-11 11:13:25.247 | INFO | 77226 | __main__:handle_record_begin:37 | Begin Recording...
2020-11-11 11:13:26.467 | INFO | 77226 | __main__:handle_record_end:45 | End Recording...
2020-11-11 11:13:28.703 | INFO | 77226 | __main__:handle_utterance:72 | Utterance: ['ip address']
would indicate that you hear it, just donât have the right sequence of words to trigger a skill
Yeah my mistake, that is from yesterday, check the timestamp⌠so a quick timelne
Initially when I did the install I could wake up mycroft/jarvis but after that he could not respond.
Today after boot up the system did not respond at all so I posted in the forum and you helped me fix the issue.
and changeback to hey mycroft as 2020-11-12 15:08:27.926 | WARNING | 5466 | mycroft.client.speech.hotword_factory:initialize:417 | Could not found find model for hey jarvis on precise.