@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:
-
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.
-
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!