MMM-ModuleScheduler - Module Schedules and Notifications

ianperrin

@cowboysdude said in MMM-ModuleScheduler:

Just curious would it be possible not to hide but to dim specific modules?

I’ve pushed an update which includes the ability to dim a module. Please feel free to update the module and use the example configuration to test it out.

cowboysdude

@ianperrin That sir is AWESOME! Thank you!

dr4ke616

Hey @ianperrin

Great module by the way. Im messing about with it, and works really well.

Do you think it would be possible to broadcast a notification to the module(s) that are being shown / hidden so they could react to it?

So for example if any given module were able to check for SHOW_MODULE, HIDE_MODULE or DIM_MODULE in the notificationReceived function so that the module could react to it and handle some specific behaviour?

What do you think?

strawberry 3.141

@dr4ke616 hide module will call the hide method of the module

quote from the readme When a module is hidden (using the module.hide() method), the suspend() method will be called. By subclassing this method you can perform tasks like halting the update timers. so you can do the specific behaviour you want in there

for show module it’s the resume method

dr4ke616

@strawberry-3.141 I didnt notice this - thanks for pointing it out. Thats exactly what i need!

plumcraft

Hi,

Great idea, i’ve tried your module but i does not work for me. I might have missed a step or something.

I did put in the config file your module (after download and setup with npm install))) :

{
   module: 'MMM-ModuleScheduler'
},

And then :

{
  module: 'MMM-WunderGround',
  position: 'top_right',
  config: {
    module_schedule: {from: '0 14 * * *', to: '0 18 * * *' },
    apikey: 'xxxxxxxxx', // private; don't share!
				pws: 'pws:IBOULOGN39', //culemborg
				hourly: '1',
				fctext: '1',
				fcdaycount: "5",
				fcdaystart: "0",
				hourlyinterval: "3",
				hourlycount: "2",
				alerttime: 10000,
				alerttruncatestring: "french:"
			},
			classes: 'for_all default'
		},

It’s 13:30 and the weather is still showing on the mirror.

Thanks for your help

Note from admin: Please use Markdown on code snippets for easier reading!

cowboysdude

You’re missing the trigger ;)

Here do this:

{
module: ‘MMM-WunderGround’,
position: ‘top_right’,
classes: 'scheduler',
config: {
module_schedule: {from: ‘0 14 * * *’, to: ‘0 18 * * *’ },
apikey: ‘ad100f1e35ae51d2’, // **private; don’t share!**  
pws: ‘pws:IBOULOGN39’, //culemborg
hourly: ‘1’,
fctext: ‘1’,
fcdaycount: “5”,
fcdaystart: “0”,
hourlyinterval: “3”,
hourlycount: “2”,
alerttime: 10000,
alerttruncatestring: “french:”'
}
},

Note from admin: Please use Markdown on code snippets for easier reading!

ianperrin

@plumcraft

As @cowboysdude said, you need to configure the classes option to trigger the scheduler.

As you already have the classes option set up for what looks like @paviro 's MMM-FacialRecognition module I would suggest trying the following config.

{
  module: 'MMM-WunderGround',
  position: 'top_right',
  config: {
    module_schedule: {from: '0 14 * * *', to: '0 18 * * *' },
    apikey: 'ad100f1e35ae51d2', // private; don’t share!
    pws: 'pas:IBOULOGN39', //culemborg
    hourly: '1',
    fctext: '1',
    fcdaycount: '5',
    fcdaystart: '0',
    hourlyinterval: '3',
    hourlycount: '2',
    alerttime: 10000,
    alerttruncatestring: 'french:'
  },
  classes: 'for_all default scheduler'
},

Please do report back if you are successful because I haven’t tested the compatibility of the two modules :)

cowboysdude

Opps didn’t realize you were using Facial Recognition… LOL

Thanks @ianperrin !!

plumcraft

@ianperrin @cowboysdude

Thank you both, it works with paviro’s MMM-FacialRecognition module.

cowboysdude

Okay I have another curve ball for you… how about … the ability to turn the mirror off and back on with this? :)

plumcraft

+1, would be great to add this feature :)

dr4ke616

+1, be really nice if it not only just dimmed the running modules, but actually shut off the monitor.

cowboysdude

@dr4ke616 Well you could actually do it with a straight cronjob … something like this…

55 6 * * * /home/pi/monitor_on.sh

And off the same way :) It’s like making your own schedule…

dr4ke616

@cowboysdude thanks for pointing that out. Thats a better idea I didn’t think of :)

ianperrin

@cowboysdude said in MMM-ModuleScheduler:

Okay I have another curve ball for you… how about … the ability to turn the mirror off and back on with this? :)

So I’m thinking there are a number of approaches here.

One approach might be to add a mechanism to schedule the sending of notifications e.g
notification_schedule: [{cronTime: '0 22 * * *', notification: 'MONITOR_OFF'}, {cronTime: '0 9 * * *', notification: 'MONITOR_ON'}]

Another module could then be built (or may already exist) to listen to the notifications and react accordingly, e.g. control the monitor.

What do you think?

cowboysdude

Right now I’m doing it with crontab… my schedule is complex hahahah

BUT you have a great idea there, That sir would work perfectly!!!

Yes that would work… currently people are doing it with either the camera or PIR sensor but for those who have neither this would be a great replacement!

My schedule works like this:

On at 7 am
Off at 9 am
On at 5 pm
Off at 11 pm

However, this will change because I only want that to happen M-F on Sat and Sun I want it differently…

On top of using the scheduler to show different things throughout those times… I gotta tell you how much I really like this module! :)

Alvinger

I can’t get the dimLevel to work on the clock. I have the following config:

{
 module: "clock",
 position: "top_left",
 classes: "scheduler",
 config: {
  module_schedule: [
   {from: "00 06 * * *", to: "30 09 * * *", dimLevel: "50"},
   {from: "00 16 * * *", to: "30 22 * * *", dimLevel: "50"}
  ]
 }
},

When the time reaches “to” the clock just disappears rather than being dimmed.

What am I doing wrong? (I am running the latest version of the module)

cowboysdude

@Alvinger

Try this instead:

{from: '0 06 * * * ', to: '30 09 * * * ', dimLevel: ‘50’},
{from: '0 16 * * * ', to: '30 22 * * * ', dimLevel: ‘50’}

ianperrin

@Alvinger:

A few quick observations,

Firstly I’d suggest removing the leading zeros from each field in the cron expression, i.e. changing 00 06 * * * to 0 6 * * * - some parsers may support this but I believe the cron tab specification states the valid values for the minute field is 0-59 and hour field is 0-23. If in doubt, try using http://crontab.guru/ to test your expressions.

Next up, make sure you updated to the latest version (git pull from the module directory and restart the mirror) to ensure the dim functionality is available to your mirror.

If after ensuring the cron expressions are correct and you have the latest version, you are still experiencing this problem, can you check the output of the log (pm2 logs mm). You should have something like this

MM-ModuleScheduler received CREATE_MODULE_SCHEDULE
MMM-ModuleScheduler is scheduling clock using '0 6 * * *' and '30 9 * * *'
MMM-ModuleScheduler is dimming clock
MMM-ModuleScheduler has scheduled clock
MMM-ModuleScheduler will next show clock at Wed Oct 15 2016 06:00:00 GMT+0000 (UTC)
MMM-ModuleScheduler will next dim clock at Wed Oct 15 2016 09:30:00 GMT+0000 (UTC)

Can you share the output of your log here so I can take a look?