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

[MoreLinux]

@richland007 I had the same, but after deleting all the devices in the Alexa app, all my devices were found again.

[richland007]

@shbatm @MoreLinux I tried doing only one module and deleteing everything and re discovering again but it did not find any new devices … i am not getting what am i doing wrong but i am sure it is something on my end
Is there a way and where do i look for errors??
can i see someones config .js portion of the module??

thank you in advance
D

[MoreLinux]

@richland007 The devices in the config.js, did they have the same name as before the trouble started??

When yes, than Alexa does a discovery, but only finds known devices. That is what happened to me after I tested the module on my test-mirror and than re-did every step on my prod-mirror.

After deleting the found wemo devices in the Alexa app, I did a “Alexa, find my devices” and all the devices were found.

[richland007]

@morelinux See my Alexa is not finding any wemo devices at all from the beginning every time i asked to discover devices after installing the module no wemo’s were found.
i have plenty of other home automation devices but no wemo’s or virtual wemo’s in this case.

[MoreLinux]

@richland007 Are the mirror and Alexa on the same network??

[richland007]

@morelinux yes they sure are.
when the MM starts i do not get any errors on the MMM-AlexaOnOff or anything
I do not know if there is a debug mode for the module…i am stuck
please @shbatm help me
I also uninstall and re -installed it from the beginning and nothing changed.
I am dumb founded

D

[shbatm]

@richland007

First, as requested, here is an example config section:

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

When you start MagicMirror, you should see a line like this in your log file. If you don’t, then it’s a problem with the module installation. Make sure you’ve run npm install from inside the MMM-AlexaOnOff folder.

FauxMo service started. Listening on 192.168.1.100:21900

And netstat -tulpn | grep electron should show something like this:

tcp        0      0 0.0.0.0:21900           0.0.0.0:*               LISTEN      3554/electron
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      3554/electron

Make sure your mirror and Alexa are on the same Wi-Fi. Make sure you delete any duplicate devices in your Alexa app or at https://alexa.amazon.com/spa/index.html#appliances then restart Discovery.

[richland007]

@shbatm Hey thank you for your reply and happy new year.
I am convinced that my config.js entry (i use MMM-RemoteControl) are ok following your example.
however i do not see any

FauxMo service started. Listening on 192.168.1.xxx:21900

And when i run the

netstat -tulpn | grep electron

command i do not see a net service listening under the port 21900 either

I have unistalled and installed the MMM-AlexaOnOff module a couple of times and made sure that i have run npm install inside the cloned module folder but for some reason it is not doing what it is supposed to be doing not installing right

what do you think may be causing it??
D

[shbatm]

@richland007 it sounds like something simple has to be missing and the module isn’t loading, otherwise you would be seeing an error.

1. Please post your config anyways (or send to me in a chat if you prefer). It may be something simple missing.
2. Confirm you are using a Raspberry Pi, on WiFi, using IPv4 (not IPv6 or ethernet–those are supported but require additional config options).
3. Confirm there are no errors from the module in the logs. You can run pm2 restart mm && pm2 logs to follow the logs through the whole restart process.
4. You can also add some console.log(...) statements in the initialize function in node_helper.js to see if you can diagnose any issues with it loading. Again, if it was making it that far and not loading you should have seen an error.

[richland007]

@shbatm Here is my config.js entry

{
    module: 'MMM-AlexaOnOff',
    config: {
        devices: [{ 
              name: "Horoscope Module",
              on: { 
                notification: "REMOTE_ACTION",
                payload: { action: "SHOW", module: "MMM-horoscope" }
              },
              off: { 
                notification: "REMOTE_ACTION",
                payload: { action: "HIDE", module: "MMM-horoscope" }
              },
        }]
    }
},

and there is the pm2 logs

(the forum wont allow me to add a picture for some reason) but its all green when it comes to MMM-AlexaOnOff

I am on wifi on the same network as the echo, i am using IPv4 and of course on Rpi

I wish i could send you the picture of the pm2 logs… it says:
Connecting socket for: AlexaOnOff
Module helper started for module AlexaOnOff
Sockets connected & Module started

What do you think?? i do not see any errors

D