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

@michael5r just asking…why nest-status need to send notifications to other modules ?

mmm-nest-status isn’t sending a notification directly to other modules, it’s sending a global notification.

But seeing that all modules listen for these notifications, the notification will also reach modules that don’t need or use it (which is where the console log you showed comes from - it’s basically all modules saying “I received a socket notification”, but it doesn’t mean they actually do anything with it).

That’s just how the magic mirror socket system works - every module that broadcasts data or status does this.

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

@michael5r after hours of tests i found out that if i use default clock and calendar module then after a few minutes nest module stop updating.If i dont use clock/calendar and comment them at config.js then nest module is working fine for days.I am not a developer but i suspect that has something to do with notifications between these modules…

I’ll see if I can recreate this with those modules - thanks for the doing the debugging!

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

EDIT 2: I opened the console at the developers tools inside mm and i notished that from the moment MMM-NEST-STATUS module starts spams with notifications clock and calendar modules like that

clock received a module notification: MMM_NEST_STATUS_UPDATE from sender: mmm-nest-status
calendar received a module notification: MMM_NEST_STATUS_UPDATE from sender: mmm-nest-status

until it stops and stop updating the nest status also.Is that normal?

Yes, that’s totally normal. The mmm-nest-status module is broadcasting a notification to all modules saying that data is available - it’s how the socket notification system works.

@costascontis No, that’s fine - directly below you’ve enabled read/write, so that supersedes the standalone read setting.

@costascontis It shouldn’t matter - I don’t use the Away read setting in this module. The settings that matter are the ones directly tied to the thermostat and smoke detectors.

@sdetweil said in MMM-Energy-Saver - an easy way to suspend/resume modules based on a PIR sensor.:

@michael5r also note that modules can be hidden on purpose. So wakeup should not show all modules.

My MMM-SleepWake saves a list of modules already hidden on sleep.

This also works across sleep/wake voice commands by MMM-voice/lucy

Sure - and in that case, the mmm-energy-saver module probably isn’t a good fit. But it works great when you only need to do what I describe above :)

@sdetweil It’s the same thing, though - when do you module.hide(), you trigger the suspend method for that particular module.

@agp42 said in MMM-Energy-Saver - an easy way to suspend/resume modules based on a PIR sensor.:

Hello,

interesting module, I worked myself too a lot about this topic for my Mirror, but the main problem was that most of the module don’t define the suspend/resume functions, and consequently even when they are hidden they continue to run in background and request to update their datas…
So my solution was to update most of the module I am using to add suspend/resume function to stop the update according to the module.hidden and the notification “USER_PRESENCE” (sent by the PIR sensor module).

Did you find a smarter way ?
What is your module really doing to save the energy ?

Thank you for your clues !

So … the mmm-energy-saver module really does 2 things:

1. It allows you to create a simple daily schedule where all modules are hidden and where your monitor is turned off. For instance, on my own mirror, this is set to take place between midnight and 7 am. During this time, any notifications from your motion sensor is ignored.

2. Outside of this schedule (deepsleep), it continually listens for the USER_PRESENCE notification from the mmm-pir-sensor module. When this notification is received it shows all modules (if they were previously hidden) and runs a timer in the background. If the timer runs out before any new USER_PRESENCE notifications are received, this module then hides all other modules on the mirror.

But this doesn’t solve the issue that you also mention - even though a module is hidden, most modules continue to load data in the background - which is a huge waste.

So I did the same thing as you - I updated all my own modules to extend the standard suspend and resume functionality that already exists in the magic mirror framework.

You can see example code here:
https://github.com/michael5r/mmm-nest-status/blob/fcbf291a26374e32901e993f9e109465819f59bf/mmm-nest-status.js#L613

Basically, when the suspend command is received, I set a module state called sleeping which also stops the module from getting new data.

When the resume command is received, the sleeping state is set to false and it immediately polls for fresh module data.

Would be nice if more modules supported this behavior!

@christian Sure - post it as an issue/feature request in the Github repo for this package and I’ll find some time to build it!

@christian Not currently - I’m just displaying them in the order that the API spits them out.