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

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.

Please post your config anyways (or send to me in a chat if you prefer). It may be something simple missing.
Confirm you are using a Raspberry Pi, on WiFi, using IPv4 (not IPv6 or ethernet–those are supported but require additional config options).
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.
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

shbatm

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

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

I’m at a loss. I ran the install on a fresh install of MagicMirror (v2.7.0-dev) on the latest version of Raspbian with Desktop (Nov’18) and I got the output shown in this Gist: https://gist.github.com/shbatm/886fc811d314d136ccedeaf5663e5881. Notice the FauxMo service started. Listening on 192.168.10.92:21900 on the third to last line.

When I copy and paste your config section into my config it works fine. I run Discover Devices on Alexa and she finds “Horoscope Module” as a Wemo Switch.

What version of MagicMirror, node, and Raspbian are you using? Is it the most recent?

Try running FauxMo by itself and see if you can find the “fake” devices it creates:

cd ~/MagicMirror/modules/MMM-AlexaOnOff/node_modules/fauxmojs/example
node example.js

You should see: started.. and then be able to discover ‘office light’ and ‘office fan’

Edit: I did notice one thing: unless you’re using my fork of MMM-Remote-Control, the SHOW/HIDE functions require the module identifier, not the module name. The identifier will be something of the form module_4_MMM-horoscope and is the HTML ID of the module’s container (you can find this by using DevTools or digging into MMM-Remote-Control further.

richland007

@shbatm When i try to run the FauxMo example i see that it says: started …
but there is no service running on port 21900 when i do “netstat -tulpn”
I get a bunch of services running but none on that port.
And when i try to discover devices, Alexa comes up saying that no new ones were found agian… so no Office Lamp and no Office Fan

I am running Magic Mirror M 2.4.1
Node version is: v6.13.0
Rasbian Stretch 9.6 release (it is updated and upgraded as of today but i do not know if it is the lates release since i have been playing with it for a while)

one more time with some more explanation on the MMM-Remote-Control names please… i did not quite get it where would i find the names again and are they numbered by MMM-Remote-Control according to their place that they have on my congfig.js list ??

thank you for your help
Denis

shbatm

The example runs on different ports (10000, 10001 I think) but I don’t know why Alexa wouldn’t find the devices. There must be something with your network or firewall causing an issue.

The module may not be starting properly because it has a minimum MM version of 2.5.0. If you don’t want to upgrade, you can try changing line 21 in MMM-AlexaOnOff.js to match your version.

About MMM-Remote-Control: see https://github.com/Jopyth/MMM-Remote-Control#list-of-actions for more details. The IDs are created by MM when it starts, and yes it should match the order in your config. The easiest way I’ve found to get these is to open the remote.html page on your computer, go to Edit View, and right-click > Inspect Element on one of the menu items. You’ll get something like this:

I have a Pull Request for MMM-Remote-Control pending that will let you use the names directly, but it hasn’t been incorporated yet.