[Guide] Control MM via Google Home

[smackenzie5]

@Sean
OnScreenMenu is one of the 3rd Party modules here:
https://github.com/shbatm/MMM-OnScreenMenu

I used notificationReceived because it was similar to your example of SHOW_ALERT.
From alert.js - show_alert: function(params, sender) {
From MMM-NotificationTrigger.js - notificationReceived: function (notification, payload, sender) {
Maybe not correct but that’s why I did it.

Here’s where I got the example used for the content of notification and payload:
https://github.com/shbatm/MMM-AlexaOnOff/blob/master/README.md
Again, maybe not correct but that’s why I did it.

{
    module: 'MMM-OnScreenMenu',
    position: 'bottom_right',
},
{
    module: 'MMM-AlexaOnOff',
    config: {
        devices: [{ 
              name: "Magic Mirror",
              on: { 
                notification: "ONSCREENMENU_PROCESS_ACTION",
                payload: { actionName:'monitorOn' }
              },
              off: { 
                notification: "ONSCREENMENU_PROCESS_ACTION",
                payload: { actionName:'monitorOff' }
              },
        }]
    }
}

Thoughts?

Thanks,
Scott

[A Former User]

@smackenzie5
As far as I read OnScreenMenu module,
it needs notification like this;

• notification : ONSCREENMENU_PROCESS_ACTION
• payload:
  • “actionName” : “monitorOn”

So you can make your IFTTT & NotificationTrigger recipe like this;
IFTTT recipe

{
  "notification": "MONITOR_ON_FROM_IFTTT",
  "payload": null
}

MMM-NotificationTrigger

module: "MMM-NotificationTrigger",
config: {
  useWebhook: true,
  triggers: [
    {
      trigger: "MONITOR_ON_FROM_IFTTT",
      fires: [
        {
          fire: "ONSCREENMENU_PROCESS_ACTION",
          payload: {"actionName": "monitorOn"}
        }
      ]
    }
  ]
}

I didn’t test those codes on real machine so there could be some syntax error, but I believe you can understand the concept

[smackenzie5]

@Sean
You sir, are a freakin’ genius - it works perfectly.
Thanks again for all the effort.

[sgarg15]

@Sean If possible could you give an example of how our config file should look like if we wanted to use the google home to turn on and off the monitor?

[sgarg15]

Also if i were using MMM-Remote-Control besides MMM-OnScreenMenu, how would it work?

[sgarg15]

@Sean So i followed all the steps and looked at the conversation you had with smackenzie, but i still cant get my monitor to turn off, here my
config.js

    {
    			module: 'MMM-OnScreenMenu',
    			position: 'bottom_right',
		},
    {
    module: "MMM-NotificationTrigger",
    config: {
      useWebhook: true,
      triggers: [
        {
          trigger: "MONITOR_OFF_FROM_IFTTT",
          fires: [
            {
              fire: "ONSCREENMENU_PROCESS_ACTION",
              payload: {"actionName": "monitorOff"}
            }
          ]
        }
      ]
    }
    },

IFTTT request

{ "notification": "MONITOR_OFF_FROM_IFTTT", "payload": null }

and here the log when i say Magic (the keyword)

reqpost? { notification: 'MONITOR_OFF_FROM_IFTTT', payload: null }

[sdetweil]

@sgarg15 if you open the developers window console, you should see the notifications being sent

[sgarg15]

@sdetweil the notification is being but it isnt doing anything to the monitor

[sdetweil]

@sgarg15 so, the onscreen module should be configured to receive and process this, right?
ONSCREENMENU_PROCESS_ACTION

[sdetweil]

@sdetweil these control modules are just so complex to setup.