MMM-AssistantMk2

A Former User

@markv @teitlebot
There could be many reasons for that case.
Maybe too many modules or too many front-end refreshing or animating, too many background process or anything else, even including internet speed.
I cannot point specific reason at this moment.
Anyway in my device, I use BT speaker and I have no problem about that. Sorry.

MarkV

@sean
Thanks for the reply.
I was scared of something like that. After a clean raspbian image i just installed MagicMirror and after that MMM-AssistantMK2, MMM-Hotword and MMM-TriggerNotification (with all the nmp rebuild errors). I’ve uninstalled the compleet LibreOffice and game packets wich come by default with raspbian.

I allready made a .asoundrc file like you can find around the internet.
aplay && arecord work fine without glitches.

Result .asoundrc

pcm.!default {
  type asym
  capture.pcm "mic"
  playback.pcm "speaker"
}
ctl.!default {
        type hw
        card 0
}
pcm.mic {
  type plug
  slave {
    pcm "hw:1,0"
  }
}
pcm.speaker {
  type plug
  slave {
    pcm "hw:0,0"
    rate 18000
  }
}

Results aplay -l && arecord -l

pi@MagicMirror2:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 7/7
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
pi@MagicMirror2:~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Result lsmod

pi@MagicMirror2:~/MagicMirror $ lsmod
Module                  Size  Used by
fuse                  106496  3
cfg80211              573440  0
rfkill                 28672  2 cfg80211
joydev                 20480  0
ads7846                20480  0
hwmon                  16384  1 ads7846
snd_bcm2835            32768  1
spi_bcm2835            16384  0
i2c_bcm2835            16384  0
fixed                  16384  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
evdev                  24576  8
snd_usb_audio         172032  0
snd_hwdep              16384  1 snd_usb_audio
snd_usbmidi_lib        32768  1 snd_usb_audio
snd_rawmidi            32768  1 snd_usbmidi_lib
snd_seq_device         16384  1 snd_rawmidi
snd_pcm                98304  2 snd_usb_audio,snd_bcm2835
snd_timer              32768  1 snd_pcm
snd                    69632  10 snd_hwdep,snd_usb_audio,snd_timer,snd_rawmidi,snd_usbmidi_lib,snd_seq_device,snd_bcm2835,snd_pcm
i2c_dev                16384  0
ip_tables              24576  0
x_tables               32768  1 ip_tables
ipv6                  434176  22

What would you suggest doing now? I’m a little stuck now, due to my lack of knowledge of Linux.

teitlebot

@sean What are you using for a mic?

A Former User

@teitlebot
I’m using logitech usb cam currently. Before that, Ps3eye, cheap chinese usb mic were tested.

MarkV

@sean @teitlebot
i’m using a cheap chinese usb mic :grinning_face_with_smiling_eyes:

teitlebot

just to update and help. I reinstalled everything without the AIY Google HAT and just using a usb mic and the issue of the audio choppiness went away. Still working on other issues like no kiosk mode and learning this complicated google home interface stuff but its really cool.

teitlebot

@markv have a look at this if your mic isnt working
https://github.com/eouia/MMM-AssistantMk2/issues/16

teitlebot

@jomwells @Module-Developers
Did anyone figure out how to add led or sound, like a beep to show when google is listening and speaking. I dont think I’m good enough with linux to do this without a tutorial. Is it something that needs to be implemented in the module or can i learn how to do it from a simple aiy kit?

A Former User

@teitlebot
https://github.com/eouia/MMM-AssistantMk2#outgoing-notifications-as-assistant-response
Basic notifications will be emitted by its status.
And you can modify module for catching the status to do your specific job.
See https://github.com/eouia/MMM-AssistantMk2/blob/93d7eca6a3995987554d8deb4f4cd76b44e3f096/MMM-AssistantMk2.js#L264
In .socketNotificationReceived(), you can catch each Assistant status.

Anyway, I’m considering to add simple ding-dong waves for convenience in next patch.

teitlebot

@sean I had to leave the assistant action part of the code out because it was causing errors in my config file.