Hi there,

Just created & released my first MM module - it’s called mmm-nest-status and displays your Nest thermostats and protect smoke detectors on your magic mirror. There are a couple of other Nest modules out there, but I found them be either buggy, ugly or unmaintained, so I thought it was time for a brand new module.

It shows all states of your thermostats and protects, but also supports multiple view modes, sizes and designs, so there’s a good chance you’ll be able to use it no matter how you’ve set up your mirror.

Check it out here:

There are a ton of screenshots in the repo, showing all the different view modes, but here’s a couple of representative ones:

Hope you find it useful!
Michael

UPDATES

12-09-2018: Version 1.2.0
Refactors the data-getting to use the socket system built into the magic mirror project - this will allow my upcoming mmm-nest-cameras module to use the same Nest data without having to do multiple calls to the Nest API.

12-12-2018: Version 1.3.0
Socket updates, small tweaks.

12-27-2018: Version 1.4.0
Adds motionSleep and motionSleepSeconds options which allow you to suspend this module when no movement has been detected for X number of seconds.

12-28-2018: Version 1.4.1
Changes motionSleep to tie into the regular suspend and resume functions exposed by MM

I’ve done this in my config.js file:

const DISABLED = {};

if (RPI_DEV) { // I'm setting this value automatically based on the system
    DISABLED.weather = false;
    DISABLED.clock = false;
    DISABLED.calendar = false;
    DISABLED.tools = false;
    DISABLED.hue = true;
    DISABLED.newsfeed = true;
    DISABLED.nest_cameras = true;
    DISABLED.nest_status = true;
    DISABLED.telegram = true;
    DISABLED.hotword = true;
} else {
    DISABLED.weather = false;
    DISABLED.clock = false;
    DISABLED.calendar = false;
    DISABLED.tools = false;
    DISABLED.hue = false;
    DISABLED.newsfeed = false;
    DISABLED.nest_cameras = false;
    DISABLED.nest_status = false;
    DISABLED.telegram = false;
    DISABLED.hotword = false;
}

And then for each module you can do something like this:

{
    module: 'clock',
    position: 'top_left',
    config: {
        displaySeconds: false,
        displayType: 'digital',
        dateFormat: 'dddd, MMM D, YYYY'
    },
    disabled: DISABLED.clock
},

@phideltdexter said in MMM-Hue-Lights - new module for your Philips Hue lights!:

I also thought about that. I had 2 entertainment areas setup already. One in living room and another generic one. I removed them just to make sure, it removed one duplicate of Living Room, but not the others.

In addition when I disable all the filters I have a list of groups that takes up almost my entire screen. The majority of which are not in the Hue App, which is why initially I thought it had to be pulling from somewhere else besides the Hue App.

Ahhh … I think I know what this is - I think these are multisource groups and lightsources. Give me a minute to come up with a fix that ignores them from the group list.

Hi,

Just released a new, small module called mmm-energy-saver.

This module works in conjunction with MMM-Pir-Sensor to automatically suspend & resume all your modules based on movement detection. Furthermore, this module allows you to specify times when all the modules are suspended and your HDMI-connected screen is turned off as well.

Please note that the movement detection will not work unless you have the MMM-Pir-Sensor module installed (and working).

By design, this module has fairly limited functionality - which is nice because it makes it very easy to set up & use. If you, however, want a lot more control over the individual modules including setting specific timers based on days or showing alerts, I’d recommend checking out the MMM-ModuleScheduler module instead.

Anyway, check out the new module here:

@sebi76 No, it needs to be before that.

Place it at the top of the file, before this line:

var config = {

Great module - I really liked the fact that you had everything classed out, so it was super easy to manipulate the UI without having to screw with your JS.

Looks very nice on my mirror:

In case someone else has this problem, instead of rebooting just run the following in your terminal:

kill -9 $(lsof -t -i :8080)

That’ll kill the current process on port 8080.

@sebi76 Your syntax is wrong - you have this:

const DISABLED = {};
   
    DISABLED.clock = false;

},

It should just be this:

const DISABLED = {};
DISABLED.clock = false;

It’s that last }, that’s breaking your code.

@dazza120 said in MMM-Nest-Status - New module for your Nest thermostats and protect smoke detectors!:

@michael5r Hi yeah thats what i mean but that has shifted it further to the right and only the Nest protect battery stuff i need to move it in the opposite direction finally figure how to take a screen capture lol here is what i mean hue status lower right, the more bulbs you have the worse it will get as it moves up when bulbs are turned on! PS speeds aren’t this slow changed the config file for the speed test and it knocked of a zero so it was a 4 second test lol 0_1544518147439_2018-12-11-084242_1824x984_scrot.png

It looks like the module is in the middle_center or bottom_bar position, though - which is why it it takes up the entire width of the page. Shouldn’t it be using bottom_left?

Hi,

Just wanted to share a new module I published recently - it’s called mmm-dropbox and allows you to grab images from a Dropbox folder, have them automatically scaled down and displayed in 1 or more rows on your mirror.

As I also point out in the Read Me this is a module with a pretty specific focus - it does exactly what I describe above (and does it well), but it doesn’t support stuff like videos, setting a Dropbox image as the background of your mirror, displaying information about the image, etc. I built this for my wife & this is what she wanted - but, hey, there’s no reason you can’t use it on your mirror as well!

Here’s the repo:
https://github.com/michael5r/mmm-dropbox

And here’s a screenshot of what it looks like on the mirror with the default configuration:

Enjoy!

Thanks for doing this - much appreciated!

Hi guys - there’s a new version of the module out that should fix the Dropbox API issue. Please try it out and see if it works for you.

@JohnBachini said in MMM-Nest-Status - New module for your Nest thermostats and protect smoke detectors!:

@michael5r
Is this the same token obtained doing this .??

https://github.com/USA-RedDragon/badnest

No - the token my module needs is the old “Works with Nest API”-token.

@jasim Sorry, I don’t speak German - can you please post in english?

@jasim Yeah, but you must have set it up at some time - for instance, I use pm2 on my mirrors, so I can do pm2 stop mm to stop my magic mirror instance.

@jasim You already have another instance of Magic Mirror running (that’s the EADDRINUSE error) - you’ll need to stop that before running npm start dev. How do you normally start/stop your mirror?

@jasim You need to be in the folder of your Magic Mirror installation when you run these commands.

@jasim said in MMM-Hue-Lights - new module for your Philips Hue lights!:

@michael5r said in MMM-Hue-Lights - new module for your Philips Hue lights!:

@jasim said in MMM-Hue-Lights - new module for your Philips Hue lights!:

I updated the module and tested it for several hours. The module fails after 45 - 60 minutes (API ERROR) and no longer works.
And not only that, the entire mirror no longer works.
After removing the module from the mirror, the mirror works again.

Can you try running your mirror in dev mode and post some logs?

Would you tell me what to do, I am a layperson and not a professional.

Instead of running npm run start in your Magic Mirror folder to start the mirror, try running npm start dev which will open a browser console next to your mirror instance. Then look for any errors (marked in red) in there.

@jasim said in MMM-Hue-Lights - new module for your Philips Hue lights!:

I updated the module and tested it for several hours. The module fails after 45 - 60 minutes (API ERROR) and no longer works.
And not only that, the entire mirror no longer works.
After removing the module from the mirror, the mirror works again.

Can you try running your mirror in dev mode and post some logs?

I’ve released a new 1.4.0 version of this module that will hopefully help with the refresh issue - it now automatically reschedules an update, no matter whether there’s an error or not. Thanks to @ulrichwisser for pushing this fix.

Please download the version and see if that solves your issues.