How to send a notification

Alyx

@hango Hi Hango!

Ok so I’ll add that first line to my MMM-SelfieShoot.js (the module that needs to be actioned by another)

And the second will be inside the MMM-AlexaControl.js? I’ll test it now :)

Alyx

Did it there but doesn’t seem to appear in Alexa, The other functions such as restart and monitor off/on works but I’m having trouble having this appear/ work.

sdetweil

@alyx so in alexacontrol, you have to create a notification device

notifications: [
    {
        name: 'Notificaition 1',
        port: 11100,
        OnOff: false,
        notification: ["NOTIFICATION", "PAYLOAD"]
    }
]

name is the thing Alexa will know
the tcp/ip port number to use for Alexa to contact this machine
and the notification info should look familiar

then u restart MagicMirror
( in the MagicMirror startup messages you should see a line listening on ??? where ??? is the port number you used in the notification entry)
and then Alexa discover devices

then whatever name is, should be discovered.

then you invoke it with
Alexa, turn on xxxx
where xxxx is the name of your device
(because alexacontrol creates fake wemo electric outlets)

note that notifications shown above is a list [], so each {} is a notification device

and this stuff goes in the alexacontrol module
config:{}
section

Alyx

@sdetweil I have that set up al;ready but my alexa cant discover it for some reason. If you need you can see it in my config.js file above

sdetweil

@alyx nice, but you missed one key point

and this stuff goes in the alexacontrol module
config:{}
section

u have in the general module section not in the module config

Alyx

@sdetweil Ah! that worked thanks :) Next issue it doesnt call the module when activated lol

sdetweil

@alyx so, now open the developers window, ctrl-shift-i, and look at the console tab

u may be able to see some module report the notification

or install my samplemodule as it reports all notifications received
https://github.com/sdetweil/SampleModule

in the Alexa app u can control devices manually, so that makes testing a lot easier

Alyx

@sdetweil Hi sam,

Great so i can see that the notification isnt being sent via the dev console, it shows up via Alexa app but isnt communicating to the MM. Would you happen to know the cause?

 {
        module: 'MMM-AlexaControl',
        position: 'middle_center',
	

	config:{
		
            image: true,
	    deviceName: "mirror",
            pm2ProcessName: "mm",
            vcgencmd: "hide",
	    startPort: 11001,
	    refresh: true,
	    restart: true,
	    //stop: true,
	    reboot: true,
	    shutdown: true,
	    monitorToggle: true,
	    //cecAddress: "0.0.0.0",
	    //usb: false
	    pages: 3,
	    notifications:[
    {
        name: 'Next page',
        port: 11102,
        OnOff: false,
        notification: ["PAGE_INCREMENT", 'payload']
    },
     {
        name: 'Previous page',
        port: 11103,
        OnOff: false,
        notification: ["PAGE_DECREMENT", 'payload']
    },
    {
        name: 'Selfie',
        port: 11104,
        OnOff: false,
        notification: ["SELFIE_SHOOT", 'payload']
    }
],
        }
    },

sdetweil

@alyx not really. if u stop MagicMirror, and then tell Alexa to turn on your notification device, you should get a ‘not responding’ message from alexa

that will tell you the two are really connected.

Alexa turn on selfie

Alyx

@sdetweil Yep that makes sense but it isnt popping up below is a quick snapshot of the dev panel


MMM-MotionDetector.js:75 MMM-MotionDetector: DiffCamEngine init successful.
module.js:195 MMM-AlexaControl is suspended.
module.js:195 MMM-NASA is suspended.
module.js:195 MMM-ISS-Live is suspended.
module.js:195 MMM-MotionDetector is suspended.
module.js:195 lifecounter is suspended.
module.js:195 compliments is suspended.
module.js:195 MMM-chromecast is suspended.
MMM-NASA.js:132 Hailing NASA
module.js:202 MMM-page-indicator is resumed.
module.js:202 MMM-Selfieshot is resumed.
module.js:202 MMM-Astro is resumed.
module.js:202 MMM-MoonPhase is resumed.
module.js:202 clock is resumed.
eventtracking-log.services.video.ibm.com/eventtracking.web.player/:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
eventtracking-log.services.video.ibm.com/eventtracking.web.player/:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
eventtracking-log.services.video.ibm.com/eventtracking.web.player/:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
eventtracking-log.services.video.ibm.com/eventtracking.web.player/:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
eventtracking-log.services.video.ibm.com/eventtracking.web.player/:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
eventtracking-log.services.video.ibm.com/eventtracking.web.player/:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
MMM-AlexaControl.js:75 RECEIVE monitor NOTIFICATION=SLEEP_WAKE
MMM-AlexaControl.js:75 RECEIVE monitor NOTIFICATION=SLEEP_HIDE
MMM-AlexaControl.js:75 RECEIVE monitor NOTIFICATION=SLEEP_WAKE
MMM-pages.js:97

The errors lead to this page
400 Bad Request
‘json’ or ‘msgpack’ parameter is required