[MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io)

SubLim3

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.

sdetweil

@SubLim3 open the developers window, ctrl-shift-i, then select the console tab across the top.

U can add text to search the console in the filter field.

You should see all the notification events

Stoffbeuteluwe

for me the test device is working (Office lamp or fan) but can’t find my modules

SubLim3

@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.

Stoffbeuteluwe

@SubLim3 i tried the app but doesn’t work…no device found

Stoffbeuteluwe

@MoreLinux I have MM running on Mac I think you have a RPI …maybe this can be my problem

Stoffbeuteluwe

@Stoffbeuteluwe is there anybody with a working module MMM-AlexaOnOff on Mac?

test device is working …but no other device

Stoffbeuteluwe

@Stoffbeuteluwe anybody an idea?

SubLim3

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)

sdetweil

@SubLim3 edit the MMM-Remote-Control.js, and change all

console.log

To

Log.log

SubLim3

@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.

sdetweil

@SubLim3 you are supposed to change console.log TO Log.log

So currently u will not find it.

Log.log is supposed to be used in the module.js file

SubLim3

@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

@SubLim3 that is a bug in remote control.

Don’t know how/when it might have got there

SubLim3

@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);

js989

Hi - I’m struggling with this module too. I have it installed with the dependencies. I can see that the ports are opened and listening. Alexa cannot find the devices. I’ve tried the examples too which have not been discovered yet either.

I have an Echo dot gen 3 in the house, on the same network as the mirror. I’ve tried searching for the device from the echo and the web portal - neither has worked. Any tips?

sbrundage85

@js989 Same situation here. Have not been able to figure it out. I found this resource which I believe may be a possible problem but have not been able to work through it. https://github.com/n8henrie/fauxmo/issues/38

sdetweil

looking at this app, I think alexa v2+ devices have removed the builtin support for wemo devices which this depends on.

so, you would have to install the belkin wemo skill… which requires actual devices

sdetweil

but MMM_AlexaControl works, same concept… I use it for 4 Mirror devices (with alexa devices, not goggle home or GA)