MMM-AssistantMk2 / MMM-Hotword Issue

[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.

[JonoGee]

Just tested. Recording & playing back fine with arecord and aplay. No problems and no error messages. Thanks for taking the time for getting in touch anyway. I’d almost given up on this.

[BJ Duncan]

No dramas at all.

Now you need to double check that you are pointing to the correct device number for your audio with the Assistant module.
In a terminal at the root directory (pi@raspberrypi:~ ) Check the device list for audio input:

arecord -l

This should provide you a list of CAPTURE Hardware Devices. The numbers you want to write down is the Card number, and device number.
As an example on my device I have it as Card: 2 Device: 0

Now within the config.js of the MagicMirror ensure that the device number is the same. Here is what it looks like within my config.js:

{
		  module: "MMM-AssistantMk2",
		  position: "bottom_bar",
		  config: {
		    record: {
		      recordProgram : "arecord",  
		      device        : "plughw:2",
		    },
		
		    notifications: {
		      ASSISTANT_ACTIVATED: "HOTWORD_PAUSE",
		      ASSISTANT_DEACTIVATED: "HOTWORD_RESUME",
		    },
		  }
		},
		{
		  module: "MMM-Hotword",
		  config: {
		    chimeOnFinish:null,
		    mic: {
		      recordProgram : "arecord",  
		      device        : "plughw:2",
		    },
		    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,
		    },
		  },
},

Notice within both my modules because my card number is ‘2’, that the

device : "plughw:2",

So make sure your number corresponds with your Card number.

Give that a test and we will go from there.

[JonoGee]

@BJ-Duncan said in MMM-AssistantMk2 / MMM-Hotword Issue:

arecord -l

I get this…

pi@raspberrypi:~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: sndrpigooglevoi [snd_rpi_googlevoicehat_soundcar], device 0: Google voiceHAT SoundCard HiFi voicehat-codec-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
pi@raspberrypi:~ $ 

[JonoGee]

@JonoGee I recognised both devices as 0 so I changed accordingly. Now i get this error message. Mirror opens but closes immediately…

[MMM-PushBulletNotifications][Info] 13:58:15.164 - PushBullet connected
[HOTWORD] begins.
[HOTWORD] Detector starts listening.
/home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js: symbol lookup error: /home/pi/MagicMirror/modules/MMM-Hotword/snowboy/lib/node/binding/Release/electron-v3.0-linux-arm/snowboy.node: undefined symbol: cblas_sdot
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the magicmirror@2.7.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-07-01T12_58_15_977Z-debug.log
pi@raspberrypi:~/MagicMirror $