mmm assistant mk2

A Former User

Tips For all

Don’t Forget to activate hardware acceleration of rpi in raspi-config (OPEN GL)
needed for YT video / cast / weblinks in fullscreen and for have more reactive mirror

dvbit

@Bugsounet So I have "Output Device Settings " item greyed out in desktop sound menu.
entries:

Analog
HDMI
USB Kinect Audio
Output Audio Device Settings : Greyed out

Edit:
Before sending Firmware to Kinect after boot (to enable it) the Ouput Device Settings Option is NOT there (also no Kinect Audio available)
After sending it both Kinect and Output Deive Settings Appear

trying to play the response using cvlc works but there is a PulseAudio error:

VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
[01cb1d60] vlcpulse audio output error: PulseAudio server connection failure: Connection refused
[01cd0fc8] dummy interface: using the dummy interface module...

Now rebooting and trying the plugin without uploading kinect audio firmware.

By the way the Pulseaudio refuse seems to me consistent with the failed audio for the plugin

DOH! I cannot try the plugin without the kinect audio firmware pushed (no other mic is attacched)

dvbit

@dvbit said in mmm assistant mk2:

HDMI

One little Step ahead.
Disabling Audio Output gives no audio feedback but then the mirrorr goes back into waiting state.
So it get’s stuck in “Spinning State” because the audio fails.
Maybe it’s obvious but I think it is interesting.

and this from the log is also useful:

[2020-06-01 19:27:11.533] [LOG]    [SNOWBOY] Retry restarting...
[2020-06-01 19:27:13.588] [LOG]    [LPCM16] WARN: arecord: main:828: audio open error: Device or resource busy

[2020-06-01 19:27:13.589] [LOG]    [SNOWBOY] Retry restarting...

So my audio ouput device is "owned " by some other process I guess

aplay -l gives:

pi@MagicMirror:~/MagicMirror $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3

sdetweil

@dvbit do

ps -ef | grep aplay

and see if its still running…

dvbit

@sdetweil nope I just grep my grep :-D

reddyman

Hmmm sorry to go a bit off topic but has anyone tried the new Assistant2Display module with the new GoogleAssistant? I can’t get it to work but I suspect I am missing something very obvious. I just don’t know what.

I can’t get the screen, briefToday, or Pir to work. I don’t get any errors, just nothing happens.

Config file:

{
  module: "MMM-GoogleAssistant",
  position: "fullscreen_above",
  config: {
   A2DServer: {
      useA2D: true,
      }, 
    assistantConfig: {
      //latitude: 51.508530,
      //longitude: -0.076132,
      },
    micConfig: { // put there configuration generated by auto-installer
      recorder: "arecord",
      device: "plughw:2",
      },
    snowboy: {
      Model: "smart_mirror", 	
	},
    }
},
{
  module: "MMM-Assistant2Display",
  position: "top_left",
  config: {
    debug:true,
  },
  pir: {
      usePir: true,
      pin: 4,
      reverseValue: false
  },
  screen: {
  useScreen: true,
  delay: 1 * 60 * 1000,
  turnOffDisplay: true,
  ecoMode: true,
  displayCounter: true,
  text: "Auto Turn Off Screen:",
  detectorSleeping: false,
  governorSleeping: false,
  rpi4: false
},

briefToday: {
      useBriefToday: true,
      welcome: "brief Today"
    },

},

I don’t see the debug working either? Nothing generated on the terminal while the mirror is running at least.

[2020-06-01 16:51:49.870] [LOG]    [ASSISTANT] MMM-GoogleAssistant Version: 2.0.0
[2020-06-01 16:51:49.885] [LOG]    [SNOWBOY] Model selected: smart_mirror
[2020-06-01 16:51:49.893] [LOG]    [SNOWBOY] snowboy v1.5.0 Initialized...
[2020-06-01 16:51:49.902] [LOG]    [ASSISTANT] Assistant2Display Server Started
[2020-06-01 16:51:49.908] [LOG]    [ASSISTANT] Google Assistant is initialized.
[2020-06-01 16:51:49.916] [LOG]    [A2D] MMM-Assistant2Display Version: 2.0.0
[2020-06-01 16:51:49.928] [LOG]    [A2D] Assistant2Display is initialized.

Anyone see what I’m missing? I suspect it’s something super simple but I can’t figure out what.

sdetweil

well, I though i’d give it a try… see what all the fuss is about!

on the install y/n prompts, the protocol is the Uppercased letter is the default, so whn you hit enter is does the default
it doesn’t do anything, have to enter Y or N (and then it takes off without waiting??)
audio doesn’t work for me…
and none of the choices match the system config (and none of them work)
system config, sounds fine, music, web sounds, system sounds.

aplay -l info
Screenshot at 2020-06-01 16-54-32.png

dvbit

A big thank You to @Bugsounet for his help in troubleshooting.
It was nothing to do with the modules but with my asoundrc config.
the ouput card/device were not correct.
Thanks again!

A Former User

@dvbit: no problem ! with pleasure ;)

A Former User

@reddyman : turn on modules. just YouTube by default is turn on
link / photo is disabled by default

 config: {
    debug:true,
    // make you config there !
  },
 // not there
....

reddyman

@Bugsounet said in mmm assistant mk2:

 config: {
    debug:true,
    // make you config there !
  },
 // not there
....

…I am an idiot. Hahaha, I knew it was something super simple. Smh, thanks for putting up with idiots like me :p

A Former User

@reddyman : don’t worry, it’s arrive to me too sometime !

James Farmer

First, I say thanks to @Bugsounet , I only started my mirror a few weeks and have had Assistant working. Upgraded to GoogleAssistant and it is much quicker.

Unfortunately I have a few problems with it now, one is sound, but im 99.99% sure because i have sound config wrong. Nothing to do with module. !
The only other issue i have is i use pages and when googleAssisatnt comes on screen part of it is still hidden by the modules on screen.
Just wondering if anyone have this problem. ?
Ive set it to fullscreen_above in GoogleAssistant so thought this wouldnt be a problem. it worked ok with AssistantMK.

Thankyou

A Former User

hi,

what the problem ?
for pages:
I don’t know what this developer means …
edit pages.css
change it to:

.fullscreen.above {
    z-index: 9999
 }

page should now works correctly

James Farmer

@Bugsounet Thanks that has fixed it, I need to have another go at learning css to try and sort out all the positions.

Ill get back to trying to sort out sound.

Thanks again

JohnBachini

@Bugsounet

HI, Amazing work with GoogleAssist, it seems to be more responsive and accurate than AssistantMK2.

Have an issue with the display of the googleAssistant banner. My Mirror is full screen, ie in custom.css i have :-

 body {
     margin: 0px;
     position: absolute;
     height: 100%;
     width: 100%;
}

Which i hope is correct, im struggling with css side of things !! :-)
But when the banner appears i have this issue,

As top of banner is missing and width

I looked at GoogleAssistant.css, but couldnt work out what needs to change.

A Former User

@JohnBachini :

{	
  module: "MMM-GoogleAssistant",
  position: "fullscreen_above",
  config: {
    ...
  }
},

don’t work with this position ?

Edit : Ah yes don’t work

JohnBachini

@Bugsounet

Yes i have it set to fullscreen_above, i confirmed it works fine if i remove the css code i posted above

A Former User

@JohnBachini: I don’t find too :face_with_tears_of_joy: :face_with_tears_of_joy: :face_screaming_in_fear:

I got lost in my css code !!!

JohnBachini

@Bugsounet :-) So custom.css overides main.css , so does GoogleAssistant.css overide all ?