@bjoern - I have created an initial version of MMM-ModuleScheduler and pushed it to github -https://github.com/ianperrin/MMM-ModuleScheduler

If you would like to test it, feel free to install it on your Mirror and report back here.

However, please remember that this is work in progress and has not yet been fully tested, so please do use with care.

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'} ]

@cowboysdude said in modules day and time Depending represented:

Only thing I can see wrong is the speed [decreased] of loading the mirror!

As part of the install process, npm install needs to be run to install the dependency on node-cron. This can take a little time, but is only required once. Having completed the install, I’m not seeing the performance issues you mention so we might need to look into that a little further.

@cowboysdude said in modules day and time Depending represented:

It’s turning anything off with 'classes: ‘scheduler’, attached no matter what time you set

The expected functionality is that the module is shown between the dates specified, so once the module has done it’s thing, it hides the modules and they are not shown until the next ‘from’ date.

In more detail, it should follow the following process once it receives the notification (DOM_OBJECTS_CREATED) that all modules have been loaded:

• It checks each module to see if it contains the ‘scheduler’ class
• If yes, it checks whether the module config includes the ‘module_scheduler’ option
• if yes, it checks whether the option includes the ‘from’ and ‘to’ properties
• if yes, it creates the cron jobs to show (‘from’) and hide (‘to’) the module
• if the next show (‘from’) date for the module is in the future and less than the next hide (‘to’) date, it hides the module
• when the ‘from’ cron job is triggered, it sends a notification to show the module
• when the ‘to’ cron job is triggered, it sends a notification to hide the module

Now, as this is work in progress I haven’t had time to check all permutations of modules and cron expressions. However, it’s logging is rather verbose so please do check out the console log (pm2 logs mm) to see what it thinks it is doing!

If you find problems, can you post your config (or at the least, which module you are trying to schedule and the values for the module_scheduler option?

Thanks

Earlier versions of the module would create duplicate cron jobs if the Mirror recreated the modules (e.g. after a page refresh in the browser). The current version attempts to resolve this.

Trailblazers who’ve already grabbed a copy of the module please run git pull from the module directory - see https://github.com/ianperrin/MMM-ModuleScheduler#updating for more details

@cowboysdude - rather than add two instances of the module, try the following expressions:

module_schedule: {from: '0 7,17 * * *', to: '0 8,23 * * *'}

This should create a schedule with jobs to show the module at 07:00hrs and 17:00hrs, and jobs to hide the module at 08:00hrs and 23:00hrs

I can see there are use cases where multiple schedules might be required, so I’ve created an enhancement request on github to cover that one - https://github.com/ianperrin/MMM-ModuleScheduler/issues/2

@cowboysdude said in modules day and time Depending represented:

I guess had I investigated cron I could have found that out myself… sorry.

Glad to help and no need to apologise at all