Greetings All,

Just wrapped up support for the Leap Motion Controller.

https://github.com/manifestinteractive/MMM-Leap-Motion

IMPORTANT: This ONLY works with the Native Leap Motion App

You will not be able to use this with the Raspberry Pi, or any other hardware that does not have the Native Leap Motion App running in the background. Your Magic Mirror computer will need to be powerful enough to meet the Minimum Requirements to run the Leap Motion Controller.

Features

• Visual Indicator when your hand is detected, letting you know you can make a gesture
• Visual Representation of Gestures on Screen
• Supports Swipe Gestures: Up, Down, Left, Right, Forward & Back
• Supports Circle Gestures: Clockwise, Counter Clockwise
• Ability to limit which gestures you want to watch for

Just pushed up the Leap Motion Controller Module. Added a code snippet on how to get it to work with your module:

https://github.com/manifestinteractive/MMM-Leap-Motion

@veldrovive said in MMM-Page-Selector: A page switcher that can set positions of modules:

MMM-Page-Selector

This is exactly what I was looking for. I am building a Leap Motion Module ( for native Leap app on Windows, MacOS, etc … not Raspberry Pi ) that detects swipe gestures.

I will release that in the next few days and make a comment on here about it. But essentially you swipe left to go to a previous page, swipe right to go to the next, etc.

My Smart Mirror is going in a bathroom, and I wanted a way to navigate the pages without having to touch anything, including the mirror. This actually works pretty well.

I found your repo on GitHub a few days ago and have already been messing with it, and was trying to work out some bugs with the old pages prop you used to have on your module, but this new method of moving the pages to the modules we want to embed is much cleaner.

Bravo.

Greetings,

Just wrapped up a new Magic Mirror Module that adds Nest Thermostats.

https://github.com/manifestinteractive/MMM-Nest-Thermostat

Features:

• Fetches all thermostats in your house
• Can be displayed in one of four sizes
• Cherry-pick which thermostats to display
• Shows current status and temperature of thermostats
• There is also a bash script to help generate the Nest API Token

Description

Greetings All,

Just committed a new Magic Mirror Module to GitHub:

The module will let you pick between streaming video or auto-updating snapshots. You can also pick 4 different sizes to render with. Only want to show one or two of your camera’s and ignore the rest? That’s doable too.

I tried to make the setup easy by creating a bash script that walked you through creating a Nest API token for your mirror.

NOTES:

• video mode may not autoplay for all devices, as some devices require user interaction before video content will play. This is why I created the other mode …

• image mode will automatically update every three seconds with the latest snapshot from your security camera. Three seconds seemed about the fasted I could fetch the update and get a new image from Nest. I also made sure to load the image into memory first before updating the DOM, so there should not be any flickering as the images from your security camera are updated.

If you have any idea or suggestions on how to make this better, hit me up on GitHub or Twitter.

Screenshot

Download

[card:manifestinteractive/MMM-Nest-Camera]

@d90 not yet, I am currently building my smart mirror. Though as long as your contrast and brightness is high, my tests show that a considerable amount of light comes through just by adding this 40px white border to the Magic Mirror app.

@rak OK, so after digging into this more, it looks like this won’t work without an update to the way the config.js file is loaded.

Currently, it is being loaded two ways.

1. As an exportable module that can be used via require() statements
2. As vanilla javascript

So the dotenv would have worked fine ( and DOES work fine ) when used in a module context. However, the vanilla JS cannot reference module data this way. The solution would be to dig more into the ./js/app.js and ./js/main.js files and look at how they are handling the loadConfig functions and see if there is not a way to tweak it for your purposes.

Sadly, there is not much more I can think of to help with that without spending several hours tinkering around.

@rak This is most interesting :)

I am actually working on testing this now. There is no real reason this should not have worked, but you are 100% right, it seems to tank the config.

What’s really interesting is that I am tinkering around in the ./js/app.js file, and it’s actually not breaking when it’s being imported. The config file that comes in gets merged just fine and consoling it out, shows the correct dontenv getting replaced.

This means somewhere else along the line, this code is breaking.

Hopefully I can follow the config through the app and detect where that’s happening and post back ASAP.

@rak You may wish to use dotenv. You can either do this on a module level, or for your local install.

https://www.npmjs.com/package/dotenv

Here you would just make an .env file in your project root with something like:

API_KEY=MySuperSecretApiKey1

Then you should be able to update the config file with:

var localConfig = require('dotenv').config();

var config = {
...
   { ...
      apiKey = process.env.API_KEY,
   }

Just make sure to add the .env file to .gitignore so it won’t get committed via git.

Just created my first Mirror Magic Module. Add a pure white border around your Magic Mirror. This big white light illuminates your face and looks great with Modules or by itself.

MIRROR_LIGHTS_ON & MIRROR_LIGHTS_OFF

https://github.com/manifestinteractive/MMM-Frame-Light

If there is anything I can do to make this better, let me know. I plan to create a few more of these :)