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.

@Sean
VERY interesting!

FWIW, there was NO issue with HAT previously! That’s why I thought it would be OK going forward with it. Dammit, I should have left well enough alone and not upgraded! Too late now, everything’s changed!

I don’t know enough about ALSA to fight my way out of a wet paper bag. But it is worth figuring out, because I’m not the only one who picked up a cheap HAT for $5 and figured it would work - the form factor is nice.

So I guess I’ll take this on and report back when I work it out. OR blow it off, connect some externals and get my Mirror done. Either way, thanks so much for the suggestion!

Re: MMM-Hotword
Hello, and hopefully hello to Sean, if you see this.

I have Hotword installed with MMM-AssistantMk2 on the latest build of MM2 (2.90), running on an RPi3. Everything except Hotword is running great! At one point, before upgrading everything, I had all this working fine, but now my pm2 logs show

0|mm  | [HOTWORD] Detector starts listening.
0|mm  | [HOTWORD] Final Result: { detected: false }
0|mm  | [HOTWORD] begins.

over and over in a loop… No attempt on my part gets it to recognize anything. I even removed all modules except Hotword (and the clock so I’d know it was running) and I get the same results.

I have deinstalled and reinstalled Hotword via the automatic script And the manual method. Installation appears to be fine, and components are there. Using this config:

{
			module: "MMM-Hotword",
			config: {
				chimeOnFinish:"resources/dong.wav",
				mic: {
				  recordProgram : "arecord",  
				  device        : "plughw:0",
				},
				models: [
				  {
					hotwords    : "smart_mirror",
					file        : "smart_mirror.umdl",
					sensitivity : "0.5",
				  },
				],
				defaultCommand: {
				  notificationExec: {
					notification: "ASSISTANT_ACTIVATE",
					payload: (detected, afterRecord) => {
					  return {profile:"default"}
					}
				  },
				  afterRecordLimit:0,
				  restart:false,
				},
			  },
		},

The line for “device : “plughw:0”,” is because I’m using the Google HAT and mic/speakers/etc. That’s not the issue, I don’t think, because the HAT has worked fine in the past with Hotword.

Please tell me I’m an idiot and that this is an easy fix I’m just not seeing right now.

Thanks, and thanks to Sean for all the good work on this module!

@sdetweil LIKE A CHARM. All is well with Assistant and Hotword, just as you describe. MMM-Buttons also required and npm install, as well as MMM-PIR-Sensor. So, basically, maintenance on all the plugins.

@sdetweil Thanks for these leads! Now that you mention it, why would I not need to do this… I’ll let you know how it goes…

Mine also not working on RPi3, and removing the exact same plugin does not remedy the situation. Sample config does make it behave, but it seems like there might be another plugin issue?

I’m running (or used to run)

Remote Control
DarkSky Forecast
Network Scanner
Volumio Playing
Roomba
Notification Trigger
Hotword
Assistant Mk2
Buttons
and PIR sensor.

I upgraded because Electron was leaking or whatever it does to slow to a crawl, and slushing back to a previous Electron had not fixed the problem. Too tired to try them all one at a time right now, but I guess I’ll go to it tomorrow.