@sdetweil I did find this line commented out near the top of the MMM-Remote-Control.js which may be where they are working to resolve this.

// Log.log(this.name + " received a module notification: " + notification + " from sender: " + sender.name);

@sdetweil Correct. There were 2 instances in the MMM-Remote-Control.js where I changed console.log to Log.log and this did resolve my issue. I was more curious to know if this was an issue with AlexaOnOff not having an update or if it was due to Remote-Control updating to a newer build.

@sdetweil Is this something that happened because I updated MMM-Remote-Control and MMM-AlexaOnOff does not have an update? If so, would it be better to update AlexaOnOff to have console.log instead of log.log? That being said, I could not find Log.log in AlexaOnOff.js anyways.

Are there other modules that will stop working if I change MMM_Remote_Control to Log.log? I saw it in there a couple of times and changed it. This did resolve the issue but I need to see if there are other Modules throwing red flags now.

Thank you for the Help! Hopefully MMM-AlexaOnOff gets an update to help everyone else with 3rd Gen Alexa devices get discovered.

@dazza120 Correct, nothing in the config.js but the defaults.

So IF I understand this log correctly, my mirror is receiving the Notification from my Alexa Device but the AlexaOnOff module is not operating correctly. Any suggestions?

module.js:154 MMM-WatchDog received a module notification: REMOTE_ACTION from sender: MMM-AlexaOnOff
module.js:154 MMM-Screencast received a module notification: REMOTE_ACTION from sender: MMM-AlexaOnOff
module.js:154 MMM-GoogleMapsTraffic received a module notification: REMOTE_ACTION from sender: MMM-AlexaOnOff
MMM-Remote-Control.js:43 Uncaught TypeError: console.log is not a function
    at Class.notificationReceived (MMM-Remote-Control.js:43)
    at sendNotification (main.js:95)
    at Object.sendNotification (main.js:502)
    at Class.sendNotification (module.js:368)
    at config.devices.forEach.d (MMM-AlexaOnOff.js:47)
    at Array.forEach (<anonymous>)
    at Class.socketNotificationReceived (MMM-AlexaOnOff.js:37)
    at module.js:246
    at r.<anonymous> (socketclient.js:25)
    at r.emit (index.js:83)

@dazza120 I have had my image tightly packed onto an 8gb SD Image and then run it on a 16gb image for more space. Overtime Cache and whatever else was maxing out my 8gb. I haven’t had any issues since rebuilding the image with newer MM and Modules. Running WatchDog and having it all on a 16gb image seems to have really helped.

@Stoffbeuteluwe Yeah, I have been reading that the 3rd Gen Alexa devices are not locating the modules. You might try discovery through the app or web browser http://alexa.amazon.com.

@dazza120 I never determined why but my mirror would “hide all modules” regularly. I would constantly wake up or notice that the screen was on but not displaying anything. A restart of MM would resolve but since running WatchDog this hasn’t been the case. It’s like services stopped working and WatchDog is supposed to restart any services that stop. I installed WatchDog at the same time I updated to the latest MM build so it could be coincidental.

YET ANOTHER UPDATE: I have gone through and added a few more modules to include MMM_AssistantMK2, MMM_AlexaOnOff and MMM-Screencast. Having the embedded Google assistant in the mirror helps get additional information when I see something about weather or my calendar. Having AlexaOnOff helps when I want to vocally turn the mirror on/off or even reboot or update. I use the screen cast occasionally to play fitness videos while correcting my form. I even added a much larger list of compliments including ones specific to weather that everyone tends to enjoy.

Lastly, I added the WatchDog module which has really helped stabilize the mirror. I recommend anyone running this on a Pi to have this module. This has been at times challenging but remains on of my favorite projects and gets used daily. I hope everyone enjoys theirs as much as I enjoy mine.

If the REMOTE_ACTION of MONITOROFF works from the remote UI then the notifications are sent and received and executed properly. Does anyone have any recommendations as to how I can test if the Notifications sent from my Alexa device to the module is received? Just trying to hash through this one. Any help is appreciated. Thank you.