MMM-AssistantMk2

[cola0927]

Hi, I just tried installing MMM-AssistantMk2 by following the instruction. After saving the config.js (use default configuration) nothing shows up and all I can see is a black screen but a movable mouse pointer. I can’t even quit the mirror. I have no idea what do to now, do I have to start over from the very beginning? :loudly_crying_face:

[teitlebot]

@cola0927 many of us had this issue and thats why we run it in servomode

[teitlebot]

@Module-Developers Why do you set this up as a smart TV. Why cant it be set up as a google assistant with video like the new displays they sell now?

[cola0927]

@teitlebot oh, ok, thanks. It’s my first mirror, no relative experience before. I’ll be more careful next time.

[mirror.master]

Dying to use this module, but im stuck on node auth_and_test.js i keep getting the GLIBBCXX_3.4.21 not found error. tried the solutions found on the module page and a few others spots. but to no avail. any suggestions?

[A Former User]

@cola0927 said in MMM-AssistantMk2 & MMM-GAction:

Hi, I just tried installing MMM-AssistantMk2 by following the instruction. After saving the config.js (use default configuration) nothing shows up and all I can see is a black screen but a movable mouse pointer. I can’t even quit the mirror. I have no idea what do to now, do I have to start over from the very beginning? :loudly_crying_face:

Show me your error logs. there could be many reasons about that symptom.

[A Former User]

@teitlebot said in MMM-AssistantMk2 & MMM-GAction:

@Module-Developers Why do you set this up as a smart TV. Why cant it be set up as a google assistant with video like the new displays they sell now?

Is there a google assistant with video at the setup moment? Wasn’t it on my development. If it exists, go ahead sure.

[mirror.master]

dude try a: pm2 stop mm while ssh and then check your config. you are never stranded lol

[A Former User]

@mirror-master said in MMM-AssistantMk2 & MMM-GAction:

Dying to use this module, but im stuck on node auth_and_test.js i keep getting the GLIBBCXX_3.4.21 not found error. tried the solutions found on the module page and a few others spots. but to no avail. any suggestions?

GLIBCXX problem shows your RPI doesn’t be running on Raspbian Stretch or proper dev-modules are not installed. My suggestion is… to use Stretch

[mirror.master]

upgrading now in hopes. thanks my friend. i have several pi’s with diff versions . when i was paranoid and less exp’d i was cloning my pie config, but forgot that one was jessie , one is stretch and another is whatever the hell i installed. Im pretty sure this is the older OS. Thanks again

[cola0927]

@sean Keyboard input or mouse clicking had no effect, maybe because I missed the “rebuild binaries” step.

So I started over again today and this time the microphone icon appeared after MMM-AssistantMk2 was installed, but couldn’t detect the voice, even after installed MMM-Hotword and MMM-NotificationTrigger.

Here is my config.js, basically used default values.

{
                        module: "MMM-AssistantMk2",
                        position: "lower_third",
                        config: {
                        }
                },
                {
                        module: "MMM-Hotword",
                        config: {
                        }
                }, 
                {
                        module: "MMM-NotificationTrigger",
                        config: {
                          triggers:[
                            {
                             trigger: "ASSISTANT_ACTION",
                             triggerSenderFilter: (sender) => {
                               console.log(sender)
                               if (sender.name == 'MMM-AssistantMk2') {
                                 return true
                               } else {
                                 return false
                               }
                              },
                             triggerPayloadFilter: (payload) => {
                               console.log(payload)
                               return true
                             },
                             fires: [
                               {
                                 fire:"SHOW_ALERT",
                                 payload: (payload) => {
                                   return {
                                     type: "notification",
                                     title: payload.type,
                                     message: payload.command
                                   }
                                 },
                               },
                             ],
                           },
                         ]
                       }

                },

Could you please let me know which part(s) I should modify? Thank you!

[A Former User]

@cola0927
Your MMM-NotificationTrigger configuration is wrong.

{
      module: "MMM-NotificationTrigger",
      config: {
        triggers:[
          {
            trigger: "HOTWORD_DETECTED",
            fires: [
              {
                fire:"HOTWORD_PAUSE",

              },
              {
                fire:"ASSISTANT_ACTIVATE",
		delay: 200,
                payload: function(payload) {
                  return {
                    "profile": payload.hotword
                  }
                }
              },
            ]
          },
          {
            trigger: "ASSISTANT_DEACTIVATED",
            fires: [
              {
                fire:"HOTWORD_RESUME"
              }
            ]
          },
        ]
      }
},

Try this.

[cola0927]

@sean Thank you for your prompt reply. I replaced my MMM-NotificationTrigger configuration, but still not working.

In the terminal, it shows that

assistant ready
Conversation Error: { Error: 14 UNAVAILABLE: Service unavailable.
    at Object.exports.createStatusError (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/common.js:87:15)
    at ClientDuplexStream._emitStatusIfDone (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client.js:235:26)
    at ClientDuplexStream._receiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client.js:213:8)
    at Object.onReceiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:1290:15)
    at InterceptingListener._callNext (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:564:42)
    at InterceptingListener.onReceiveStatus (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:614:8)
    at /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/client_interceptors.js:1110:18
  code: 14,
  metadata: Metadata { _internal_repr: {} },
  details: 'Service unavailable.' }

Does it mean that something is incorrect in MMM-AssistantMk2?

[A Former User]

@cola0927
I think that might be the same issue with this;
https://github.com/eouia/MMM-AssistantMk2/issues/16

[A Former User]

@cola0927
Or most of those cases are caused by your mic setup. Check your configuration whether record.device has a proper name. (If your mic is default device, leave that field as null but when your mic has another name like plughw:1, set that field with it.

[cola0927]

@sean After I changed the device name in both MMM-AssistantMk2 and MMM-Hotword, the module worked partially. I had to hit microphone icon to let its start listen to me, but that was a one-time response.

Do you have any idea what the problem is? Thank you so much.

[A Former User]

@cola0927
Show me your configuration related with MMM-NotificationTrigger. I think MMM-NotificationTrigger cannot relay the connection between Hotword and Assistant.

[cola0927]

@sean I used the one that you told me previously in config.js with a default MMM-NotificationTrigger.js

{
                        module: "MMM-NotificationTrigger",
                        config: {
                          triggers:[
                            {
                              trigger: "HOTWORD_DETECTED",
                              fires: [
                                {
                                  fire:"HOTWORD_PAUSE",

                                },
                                {
                                  fire:"ASSISTANT_ACTIVATE",
		                  delay: 200,
                                  payload: function(payload) {
                                    return {
                                      "profile": payload.hotword
                                    }
                                  }
                                },
                              ]
                            },
                            {
                              trigger: "ASSISTANT_DEACTIVATED",
                              fires: [
                                {
                                  fire:"HOTWORD_RESUME"
                                }
                              ]
                           },
                         ]
                       }

                },

[teitlebot]

@cola0927 what word are you using for wakeup? Try snowboy.

[cola0927]

@teitlebot Yes, I tried. It showed that hotword had deteted my voice but then stopped listening instead of waking up assistant. I agree with @Sean that the problem is notification trigger is not working properly. Unfortunately I have no idea how to correct it.