MMM-AssistantMk2 (v3)

[Kevinho195]

@Sean Thanks for your fantastic Assistant! I tried to install it with your new installer, but I failed to set up the correct speaker. It did not find my 3.5mm Jack speaker. How can I use the Jack output instead of usb?

[A Former User]

@Kevinho195
For speaker, frankly said, you don’t need any setup. Just plug the jack in then set it as default sound output of RPI (You can do it on Volume Icon of Raspbian Desktop Menu bar)
If your chromium browser can play some audio (like youtube site), it will work on my module.

[Chris]

@Sean
@Chris said in MMM-AssistantMk2 (v3):

I usually use Gassistpi which is not implemented in MagicMirror.

This reacted to Ok Google. That is why I thought it worked similarly.

Thank you for this additional information,

I will take the test this weekend

Regards,

Hello,

I just did a complete installation to test this module, I must admit that I really do not regret it.

I like Gassistpi but I must recognize your module is really very accomplished.

It is impressive in terms of reactivity and no longer triggers unexpectedly as Gassitpi did sometimes.

The installation method is really very well designed.

Really nice job.

@Bugsounet
Chapeau bas Messieurs

Regards,

[A Former User]

@Chris : merci à toi chris (je vois que tu es français), on a mis nos talents ensemble :) et c’est pas fini !

---

@Chris: thanks to you chris (I see that you are french), we put our talents together :) and it’s not finish !

@bugsounet

[nakedrabbit]

Congratulations, @Sean on a new build! The installation method went through like a charm, and I’m even happy to report that my build, a Pi3 with Google Hat, responded perfectly, even though v2 would not recognize it.

But I do have one snag trying to implement it.

Raspbian Stretch, Pi3B+, with Google Voice Hat, latest MM. Clean install of AssistantMk2, although I had an assistant.json and profile saved from a previous iteration. Installation went, as I say, beautifully, with the GCC 7 downgrade, proper assignment of the Google Hat input and output and everything. But MM would not load, and my logs showed the same gRPC module error we used to get on v2 from not having the right npm install.

So I followed the old instructions from that build, namely

npm install --save-dev electron-rebuild
./node_modules/.bin/electron-rebuild

in both the AssistantMk2 and Hotword directories, and that seems to have fixed the issue.

Now I’ve got it working, except it’s not working. The first “smartmirror” command engages the Assistant, the tone sounds, but no matter what I say, the module says it did not understand, goes away, and cannot be invoked again unless I restart MM entirely. Logs end with

[HOTWORD] Final Result: { detected: true,
0|mm | hotword: ‘SMARTMIRROR’,
0|mm | file: ‘temp/afterRecording.wav’ }

…but not a lot more info than that. Could be related to the mmap issue I know you are working on, but what do I know? So I thought I would report it.

[A Former User]

@nakedrabbit
thanks for report failed install, i will inspect :)

if log don’t show mmap error, i think it’s not this.
It could be a noisy environement or a mismake configuration

have you read this ?

[A Former User]

@nakedrabbit : can you tell me more about npm install problem ?
because i execute same commands with npm install

[nakedrabbit]

@Bugsounet Sure! When I used the auto installer on my RPi3B+, running Raspbian Stretch (I list all these because maybe it’s OK on Buster, I do not know) the npm install created “node-v64-linux-arm-glibc” in the ~/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_library/ directory

I know this because I’m running MM with PM2, and the PM2 logs clearly stated that the plugin was looking for “electron-v3.0-linux-arm-glibc” at that location and could not find it.

This was a well-documented bug with the v2 install process, and the commands that fixed it were

npm install --save-dev electron-rebuild
./node_modules/.bin/electron-rebuild

These are run from the MMM-AssistantMk2 directory AND the MMM-Hotword directory. Those were easy!

As to the memory issue, I went back just now to check the pm2 logs for errors, and yes, I see these entries:

0|mm | mmap() failed: Cannot allocate memory
0|mm | Failed to create permanent mapping for memfd region with ID = 3774675295
0|mm | Ignoring received block reference with non-registered memfd ID = 3774675295

But I was not sure if they were related to the npm install issue or not. I thought they might be leftover from when the proper grpc files were not there, because, frankly, I know nothing about this stuff.

And thirdly, yes, I did read about the proper config for the v3 version, and everything seems to be fine there. The plugin loads fine, even listens to me, but simply does not process the commands and then kind of locks up. The rest of the mirror runs fine, but the voice command is no longer responsive.

I set up MMM-Buttons to trigger the Assistant as well, and that also works to set off the listener, with exactly the same result - no parsing of the voice command, the eventual “Can’t understand this” dialogue box, and unresponsive until restart.

[A Former User]

I have open an issue for this for try to correct it but it’s an unstable branch (nightly build / dev)
If you have it, you can test :)

[A Former User]

Error “mmap () failed: Cannot allocate memory” will be fixed from version 3.1.0
we have coded a secondary code that does not use HTML5 audio.

possibly, if you are not using bluetooth.
it seems that pulseaudio is the source of the problem

if you don’t use bluetooth try;

sudo apt-get autoremove --purge pulseaudio

possibly a restart of the RPI to finish the changes.
and check the parameters with arecord -l, aplay -l
this was reported by a user.
I personally have no mmap error because I uninstall pulseaudio during the installation of raspbian

OR wait release V3.1.0