Read the statement by Michael Teeuw here.
MMM-AssistantMk2 / MMM-Hotword Issue
-
@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 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 $ -
@JonoGee If devices are set as…
hw:0,0The mirror works, but Assistant/Hotword doesm’t. I just changed to …```
plughw:0and it crashes -
What type of microphone is it? Is it USB?
Also, what version of Raspbian are you using? And is it Raspberry Pi 3+ ? -
@BJ-Duncan
The Mic is a combined Speaker / Mic HAT as see here… https://www.raspiaudio.com/raspiaudio-aiyI am running Raspberry Pi3+
Version…pi@raspberrypi:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.9 (stretch) Release: 9.9 Codename: stretch pi@raspberrypi:~ $ -
Sorry @JonoGee mate, I may not be the best person to resolve as I have USB Mic so my settings will be different to yours.
I will attempt to do some research for you though and see if I can assist with a solution.
-
@BJ-Duncan
I realise both Speaker & Mic are on same Hat but does it make sense to you that the ID for aplay and arecord are exactly the same. Code included below…pi@raspberrypi:~ $ aplay -l **** List of PLAYBACK 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:~ $ 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 I mean I supposedly I have to set both IDs in config file to hw:0,0.
-
@BJ-Duncan What Mic do you use mate? I might just buy same one.lol
-
Hey @JonoGee, mate I have been researching but to no avail. Sorry mate on that. I’m just not too familiar with your set up.
The Mic and Speakers I got are just some cheap USB type models.
Speakers | MicIf you do go by this type of setup then the previous code I placed up should work #fingersCrossed ;-)
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login