MMM-AssistantMk2 (v3)

A Former User

@Chris
If you want to use MMM-Hotword as a trigger to activate this module, MMM-Hotword would be needed.
However, you can use another module as an activator that can detect your trigger and can emit some notification(customizable or not).
For example, You can use MMM-Clap instead of MMM-Hotword. In this case, you can activate this MMM-AssistantMk2 with a finger-snap instead of speaking hotword.

Chris

Thank you for your reply,
I thought that to trigger it, we could simply say “ok google” if we did not want to customize the keyword (Jarvis, Smartmirror …) using MMM-hotword.
Regards,

A Former User

@Chris
Unfortunately Ok Google(or any other hotword trigger detection) is not included in Google Assistant SDK itself by Google. That is why MMM-Hotword be needed.

A Former User

@Chris
Or you can make a version of ALWAYS LISTENING & ALWAYS REACTING FOR ANY VOICE, but I can bet nobody wants it. That is why trigger be needed.

Chris

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,

A Former User

@Chris
GassistPi might use Assistant SDK Library (Python) - Which has been deprecated by Google, so it could not be supported anymore. It had embedded hotword detector in the Library, but not included in SDK itself directly. Anyway, that is deprecated so we cannot use it anymore.

dvbit

@Sean sorry was a DUMB mistake from my side.
works FLAWLESSLY and it’s incredible the progress made.
Thanks !!

dvbit

About Hotword: have you tried Porcupine? seems to be very good

A Former User

hi, what is Porcupine ?

@bugsounet

A Former User

@Bugsounet
He said this; https://github.com/Picovoice/porcupine
Once I looked inside that. Maybe someday I could try it. Not guarantee. :D

dvbit

Video

dvbit

@Bugsounet I enabled magicwords.
Since I am Italian I looked under your iftt accounts for Italian but I could not find.
I understand it is WIP.
If you need help with the language (I don’t think but anyway I ask) please get in touch.

A Former User

At this moment, only French and English is enabled. I will update scripts for other supported language very soon !

A Former User

Humm… I will try this week end ;)

A Former User

@dvbit I have updated myMagicWord and post all supported language script
see wiki myMagicWord

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.