MMM-AssistantMk2

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

A Former User

@cola0927 @SubLim3
Well, sorry for the inconvenience. Your configuration looks no problem. The easy way to fix could be to test some suspicious points and log it, but it might need some experiences.

Do you have Telegram? I can help you with it in real-time. my Telegram ID is “@eouia”. Give me a chat anytime.

mirror.master

@sean Yes sir! Thank you! Updated everything to stretch and got my mkassistant to run! my next dilemma was linking hotword and notrigger but i gave up, make just make a physical button to click the mic, now on to those tutorials lol wherever they may be.

teitlebot

@Sean Any suggestions of integration facial recognition to the magic mirror?

A Former User

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

@Sean Any suggestions of integration facial recognition to the magic mirror?

I made this module to work with other modules by NotificationTrigger. So Another Facial recognition module could activate AssistantMK2 if there is a proper notification broadcasting. There is no need to implement that function in AssistantMk2 itself.

teitlebot

@sean Thank You. Some more learning on my part. I plan on installing
https://github.com/paviro/MMM-Facial-Recognition and will report back here.