MMM-ModuleScheduler - Module Schedules and Notifications

anatius

Hi,

I am trying to dim my mirror at nighttime - on weekdays between 10PM and 7AM, on weekends between 10Pm and 8AM. However, the below code does not do the trick - where is my mistake?

  		{
			module: 'MMM-ModuleScheduler',
			config: {
				global_schedule: [ 
					{from: '0 7 * * 1-5', to: '0 20 * * 1-5', dimLevel: '30'},					
					{from: '0 8 * * 0,6', to: '0 20 * * 0,6', dimLevel: '30'},					
				]
			}
		},

ianperrin

@anatius The config looks okay, can you check the output of the log pm2 logs mm once you have started MM2 and viewed it in a browser then post the results here?

It should look something like:

MMM-ModuleScheduler received INITIALISE_SCHEDULER
MMM-ModuleScheduler is setting the config
MMM-ModuleScheduler is removing all scheduled jobs
MMM-ModuleScheduler received CREATE_NOTIFICATION_SCHEDULE
MMM-ModuleScheduler received CREATE_GLOBAL_SCHEDULE
MMM-ModuleScheduler is creating a global schedule for all modules using "0 7 * * 1-5" and "0 20 * * 1-5" with dim level 30
MMM-ModuleScheduler is dimming all modules
MMM-ModuleScheduler has created the global schedule for all modules
MMM-ModuleScheduler will next show all modules at Mon Dec 19 2016 07:00:00 GMT+0000 (UTC)
MMM-ModuleScheduler will next dim all modules at Mon Dec 19 2016 20:00:00 GMT+0000 (UTC)
MMM-ModuleScheduler is creating a global schedule for all modules using "0 8 * * 0,6" and "0 20 * * 0,6" with dim level 30
MMM-ModuleScheduler is dimming all modules
MMM-ModuleScheduler has created the global schedule for all modules
MMM-ModuleScheduler will next show all modules at Sat Dec 24 2016 08:00:00 GMT+0000 (UTC)
MMM-ModuleScheduler will next dim all modules at Sat Dec 24 2016 20:00:00 GMT+0000 (UTC)

anatius

@ianperrin

Hi Ian,

Below is the relevant output of the log (error log is empty). Note that now (Monday at 3 PM) all modules are dimmed though they should not be…

MMM-ModuleScheduler received INITIALISE_SCHEDULER
MMM-ModuleScheduler is setting the config
MMM-ModuleScheduler is removing all scheduled jobs
MMM-ModuleScheduler received CREATE_NOTIFICATION_SCHEDULE
MMM-ModuleScheduler received CREATE_GLOBAL_SCHEDULE
MMM-ModuleScheduler is creating a global schedule for all modules using "0 7 * * 1-5" and "0 20 * * 1-5" with dim level 30
MMM-ModuleScheduler has created the global schedule for all modules
MMM-ModuleScheduler will next show all modules at Tue Dec 20 2016 07:00:00 GMT+0100 (CET)
MMM-ModuleScheduler will next dim all modules at Mon Dec 19 2016 20:00:00 GMT+0100 (CET)
MMM-ModuleScheduler is creating a global schedule for all modules using "0 8 * * 0,6" and "0 20 * * 0,6" with dim level 30
MMM-ModuleScheduler is dimming all modules
MMM-ModuleScheduler has created the global schedule for all modules
MMM-ModuleScheduler will next show all modules at Sat Dec 24 2016 08:00:00 GMT+0100 (CET)
MMM-ModuleScheduler will next dim all modules at Sat Dec 24 2016 20:00:00 GMT+0100 (CET)

Many thanks for your support!
Christian

ianperrin

Hi @anatius (Christian)

Okay, I think I see the problem, and a fix is in the works, its just going to take a little time until I can finish it.

I’ve created an issue on github which contains more details on why this is happening.

Until the fix is in place, you have two (understandably sub-optimal) options

leave the mirror running and it should self-correct after the next 8pm and/or 7/8am depending on when it is started :(
temporarily use the same expression for all days of the week, e.g.

global_schedule: [ {from: '0 7 * * *', to: '0 20 * * *', dimLevel: '30'} ]

anatius

@ianperrin

Hi Ian,

Thanks for the support. You are right indeed, the error corrects itself the first time the scheduler sets the module to undimmed. It is just that the starting conditions are not correct, but this is no big deal for me. It is just that I was too impatient to wait for the scheduler to change status for the first time…

Many thanks for your support!
Christian

lucallmon

Firstly, thanks for making such an awesome module!

However, I can get it to work with all of my modules except one… I can’t get it to work with MMM-Instagram. I have it set up just like all of my other modules, but this one just ignores the scheduler script and always runs, never following the code. Here is the module code in config.js:

		{
		      	module: 'MMM-Instagram',
		        position: 'top_right',
			classes: 'scheduler',
		        config: {
				module_schedule: [
					{from: '0 5 * * 1-5', to: '0 9 * * 1-5'},
					{from: '0 17 * * 1-5', to: '0 22 * * 1-5'},
					{from: '0 6 * * 6-7', to: '0 24 * * 6-7'}
				],
		                access_token: '//ACCESS_TOKEN//',
		                count: 200,
		                min_timestamp: 0,
		                animationSpeed: 2500,
                		updateInterval: 12000
			}
		},

any thoughts? here’s a picture of what it looks like when the scheduler is active: https://goo.gl/photos/K3S6HA7m61j5iSEe8

lucallmon

@ianperrin @cowboysdude

cowboysdude

@lucallmon Honestly I’m a bit lost on this one… I’m going to defer to @ianperrin for this one…

lucallmon

alt text
https://goo.gl/photos/dFMRL8JkvE5XWvaN7

This is what I get when I wake up and the monitor was supposed to go off at night and then turns back on in the morning. This happens every morning. Essentially, the monitor signal cuts but it never actually turns off or enters a low power state as it does when I actually shut down the Pi. This only happens when it’s overnight. When I do a trial off for a few minutes, it doesn’t do it. I think it might be the crappy old monitor, but I don’t know. Any thoughts?

lucallmon

I have found that this white screen that happens every day essentially freezes the entire Magic Mirror and I have to press CRTL+Q to restart. It doesn’t actually freeze the entire RPi.