MMM-AssistantMk2

[A Former User]

UPDATED

[2.1.4] - 2019.03.26

• Added : Now you can use recipes. https://github.com/eouia/MMM-AssistantMk2/wiki/Usage#recipes

  recipe is an external js file containing definitions of command, transcriptionHook and action. Your configuration could be more shorter.

recipes:["hide_and_show_all_modules.js", "reboot.js", "screen_onoff.js", "shutdown.js"],

Feel free to request PR to share your recipes to others.

• Changed : onIdle, onDetected features are disabled by default.

[bryan_1]

@Sean
sorry for my bad English. I use the default recipes and set the language to German for all pattern (“spiegel reboot”, “monitor aus”, etc). Every thing works fine, only the “SHOWMODULES” doesn’t work. Although the hotword is correctly detected, but nothing happens. I set the pattern for SHOWMODULE to pattern: “alle module”,

This is also the same case if I use the OnIdle and OnActivate:
onIdle: {
timer: 10006020,
command: “HIDEMODULES”,
},
onActivate: {
timer: 0,
command: “SHOWMODULES”,
},

I can hide the modules, but after the hotword for SHOWMODULES being recognized the modules aren’t shown again. What do I wrong? Many thanks in advance.

[A Former User]

@bryan_1
Can you show me the recipe(command and transcriptionHook or gAction) about SHOWMODULES?

[bryan_1]

@Sean
thank you sean for your quick response. Actually I use the default hide_and_show_all_modules.js and change the pattern to german:
var recipe = {
transcriptionHook: {
“HIDE_ALL_MODULES”: {
pattern: “alle verstecken”,
command: “HIDEMODULES”
},
“SHOW_ALL_MODULES”: {
pattern: “alle module”,
command: “SHOWMODULES”
},
},
command: {
“HIDEMODULES”: {
moduleExec: {
module:()=>{
return []
},
exec: (module, params, key) => {
module.hide(1000, null, {lockString:“AMK2”})
}
}
},
“SHOWMODULES”: {
moduleExec: {
module:[],
exec: (module, params, key) => {
module.show(1000, null, {lockString:“AMK2”})
}
}
},
},
}

exports.recipe = recipe

[A Former User]

@bryan_1
try this instead module.show(1000, null, {lockString:“AMK2”})

module.show(1000, null, {lockString: "AMK2", force: true})

[bryan_1]

@Sean I’ll try it tonight (I’m still at work now :smiling_face_with_smiling_eyes: ) and let you know. Many thanks…you did really a great job :thumbs_up_light_skin_tone: :folded_hands:

[sdetweil]

related to this topic, I haven’t been able to understand what I need to do.

I am trying to coordinate between the voice module go to sleep/wake up, and my motion detection module MMM-SleepWake.

My displays will not turn off programmatically, so I have to hide/show modules

But you only show what was NOT already hidden at time of sleep.
Voice says sleep, motion says wake… but… I need to know what was already hidden, so I don’t wake them up (restore to same state)…

with MMM-voice we developed a notification process, where the voice module does the sleep, but informs my module who was already hidden… so IF motion wakes up, i don’t accidentally show modules I shouldn’t…

wake up voice command works ok, (changed screenOn to notify my module to wake)
go to sleep is missing…

this is the socketnotification code in MMM-voice.js after voice detects ‘go to sleep’, only if using the hide/show sleep approach

if (notification === 'STAND_BY_ACTION') {
            if (payload.type === 'show') {
                if (payload.hardware === false) {
                    MM.getModules().enumerate((module) => {
                        if (this.previouslyHidden.includes(module.identifier)) {
                            module.show(1000);
                        }
                    });
                    this.previouslyHidden = [];
                }

                this.sendNotification('STAND_BY', { status: false });
            } else if (payload.type === 'hide') {
                if (payload.hardware === false) {
                    MM.getModules().enumerate((module) => {
                        if (module.hidden === true) {
                            this.previouslyHidden.push(module.identifier);
                        } else {
                            module.hide(1000);
                        }
                    });
                }

                this.sendNotification('STAND_BY', { status: true, modules: this.previouslyHidden.slice(0) });

[A Former User]

@sdetweil
First, this module doesn’t manage module’s showing and hiding itself. Of course I provided some recipe about it, but it’s better to be considered as a just example. The main purpose of this AMK2 is to give an ability about voice command and to relay it to other module. Not to control all things by AMK2 itself.
I think real job should be done by proper extern module. So If you have any good module(which is existed already or be planned to be made by yourself) to manage modules’ showing and hiding(There would be several modules already for this job), just transfer proper commands(notifications) to that module to do its job.

[sdetweil]

@Sean ok, thanks… still don’t understand recipe process design…

voice triggers command? command is some routine? run in context of module.js?

[A Former User]

@sdetweil

• To catch the specific voice order : use transcriptionHook or gAction. gAction is more natural way for user without side-effect.(something similar with Alexa Skill). But transcriptionHook is easier to make. Here is a just sample.

transcriptionHook : {
  "MY_TEST_ORDER" : {
    pattern: "execute order 66",
    command: "MY_TEST_COMMAND"
  }
}

This will hook your transcription from your speech when you say “Execute order 66”.
But this is just a kind of trigger. The real job(MY_TEST_COMMAND) needs to be defined.

• To define what to do when this order is triggered. : define command.

command: {
  "MY_TEST_COMMAND": {
    notificationExec: {
      notification: "SHOW_ALERT",
      payload: {
        message: "Yes, my lord."
      }
    }
  }
}

This shows WHAT TO DO - to emit some notification(“SHOW_ALERT”) which alert module can understand and do as it’s job.

This is basic concept.