MMM-AssistantMk2 / MMM-Hotword Issue

JonoGee

@sdetweil Just. Still crashing with the same error message

JonoGee

@JonoGee There is discussion about this here…
https://github.com/Kitt-AI/snowboy/issues/126
But i don’t understand what commands I need to run. It doesn’t read very clear to my only being an absolute amateur and all. Does it make sense to you?

sdetweil

@JonoGee is this a pi zero?

pi@raspberrypi:~/MagicMirror $ sudo apt-get install libatlas-base-dev libatlas3gf-base
Reading package lists... 0%
Reading package lists... Done
Building dependency tree       
Reading state information... Done

didn’t install libatlas-base-dev.

may have to install openblas
I had to on my odroid

JonoGee

@sdetweil No. its a Pi3 B+
How do i install openblas then?

sdetweil

@JonoGee Google search. What is r u running raspian, ubuntu?

JonoGee

@sdetweil Hi good morning. I am running Raspian.

JonoGee

@JonoGee
Error message I am getting now in console is as so…

MMM-GoogleTasks received a module notification: HOTWORD_SLEEPING from sender: MMM-Hotword
module.js:154 MMM-WatchDog received a module notification: HOTWORD_SLEEPING from sender: MMM-Hotword
module.js:154 MMM-Cursor received a module notification: HOTWORD_SLEEPING from sender: MMM-Hotword
null:1 GET http://0.0.0.0:8080/modules/MMM-Hotword/null 404 (Not Found)
module.js:154 MMM-Tools received a module notification: CALENDAR_EVENTS from sender: calendar
module.js:154 clock received a module notification: CALENDAR_EVENTS from sender: calendar

I have managed to get AssistantMk2 talking to me now in mirror but Hotword/Mic is still not functioning

sdetweil

@JonoGee hm… used to be that you needed MMM-Hotword to hear the Alexa or OK Google (or whatever special ‘Hot’ word), that signaled MMM_AssistantMk2 to listen for search words or commands…

each used the mic separately, Hotword first, then Assistant.

I know Sean has released new versions, which I haven’t tested yet

JonoGee

@sdetweil As far as I am aware, I have used the latest released versions of each. I guess I’ll just have to wait and see if someone updates it or fixes problem or something. Thanks anyway for your time and help. I have made a bit of progress though. It just seems to be Snowboy now.

BJ Duncan

Have you test your microphone to see if it working in general?

From home directory:

arecord test.wav

and talk for about 5 seconds into your microphone.
Then cancel that by Ctrl+C

Once you have cancelled the test check your directory to ensure that the ‘test.wav’ file is there:

dir

if your file shows up then you can test that file to ensure it recorded your voice from the microphone:

aplay test.wav

You should be able to hear back what you just recorded.
If you can, that means it is a configuration setting that just needs to be tweaked. If not, then there is something wrong with either the microphone settings or audio settings within the pi itself.

I will keep monitoring and let me know how you go.