MMM-AssistantMk2

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

[SubLim3]

So I have been working on my mirror for a few weeks now and so far the MMM-AssistantMk2 module is the only thing I cant seem to get working. As mentioned in a number of previous post, when I apply the default module setup in the config.js and restart, I get an all black screen and nothing is responsive. I can SSH into the config.js and comment out the 5 lines for that module, reboot and all is good again. I have removed and rebuild the module with no errors and no new results.

Has anyone found the cause behind this and how to resolve? I do have Hotword and NotificationTrigger modules running with no problem. Let me know if I need to drop an image file or some log files for further help. I’m truly stumped here. Any help would be greatly appreciated. Thanks in advanced.

[teitlebot]

@sublim3 I dont know if there is a fix for this but thats why many of us are running in serveronly mode