Read the statement by Michael Teeuw here.
-
@cowboysdude @ianperrin how would would I implement a schedule so that a module appeared for 5 minutes, then disappear and reappear in 5 minutes time?
I’ve tried this
module_schedule: { */5 * * * * },
2nd edit- I thought I’d got it with this…
module_schedule: { from: '*/2 * * * *', to: '*/3 * * * *'},
-
@Mitchfarino said in MMM-ModuleScheduler:
@cowboysdude @ianperrin how would would I implement a schedule so that a module appeared for 5 minutes, then disappear and reappear in 5 minutes time?
I’ve tried this
module_schedule: { */5 * * * * },
2nd edit- I thought I’d got it with this…
module_schedule: { from: '*/2 * * * *', to: '*/3 * * * *'},
Yes that should make it run every five minutes…
Copy and try this without brackets…
'*/5 * * * *'
example - schedule: ‘30 9 * * *’,
-
@Mitchfarino said in MMM-ModuleScheduler:
@cowboysdude @ianperrin how would would I implement a schedule so that a module appeared for 5 minutes, then disappear and reappear in 5 minutes time?
Try this
module_schedule: {from: '0/10 * * * *', to: '5/10 * * * *'},
Which should equate to the module being
- shown every 10 minutes starting from 0 minutes past the hour, i.e. 0, 10, 20 etc
- hidden every 10 minutes starting from 5 minutes past the hour, i.e. 5, 15, 25 etc
-
-
@Mitchfarino said in MMM-ModuleScheduler:
@ianperrin cheers mate!
I’ll have a look tonight!
Fantastic module by the way
Thank you and no worries.
Unfortunately, I’ve just done a quick test with the expressions I posted above and they didn’t work. :(
If you check the cron expressions i suggested using crontab.guru, it would appear they are non-standard. Therefore, I suspect they are not supported by the node cron module.
Not to worry, there’s always a solution! crontab.org states that step values can be used in conjunction with ranges. So the expressions I believe you require are as follows:
module_schedule: {from: '0-59/10 * * * *', to: '5-59/10 * * * *'},
-
-
@MichMich said in MMM-ModuleScheduler:
Any ETA for https://github.com/ianperrin/MMM-ModuleScheduler/issues/4 and https://github.com/ianperrin/MMM-ModuleScheduler/issues/6?
Wow - someone is keen ;)
The first iteration of #4 has been committed. Global schedules can now be added to show/hide/dim all modules - see the updated documentation for more info.
On the to list is to
- add support for showing/hiding/dimming modules in groups
- add the ability to exclude specific modules from the global schedules
#6 comes afterwards when I can switch my dev environment to the develop branch
-
- one schedule can now be used to hide/show/dim all modules - see global scheduling
- one schedule can now be create to hide/show/dim a group of modules - see group schedules
To do:
- add the ability to exclude specific modules from the global/group schedules
- unit and regression tests ;)
-
Nice work! LockStrings are not yet implemented, right? Until then I can’t use the module.
-
I’m using it like this… but it’s not working for some reason:
{
module: ‘MMM-ModuleScheduler’,
config: {
global_schedule: [
// SHOW MODULES WITH THE CLASS ‘daytime_scheduler’ AT 06:00 AND HIDE AT 22:00 EVERY DAY
{from: ‘50 6 * * *’, to: ‘0 9 * * *’, groupClass: ‘scheduler_mfm’},
{from: ‘50 6 * * *’, to: ‘0 23 * * *’, groupClass: ‘scheduler_mfd’},
{from: ‘0 6 * * *’, to: ‘0 23 * * *’, groupClass: ‘scheduler_sat’},
{from: ‘0 6 * * *’, to: ‘0 23 * * *’, groupClass: ‘scheduler_sun’},
{from: ‘0 6 * * *’, to: ‘0 23 * * *’, groupClass: ‘scheduler_nflg’},
{from: ‘0 6 * * *’, to: ‘0 23 * * *’, groupClass: ‘scheduler_nflng’}
]
}
},Then for example a module:
{ module: 'compliments', position: 'lower_third', classes: 'scheduler_mfm' },
I did update the module with ‘git pull’ so that’s okay but it’s not rendering correctly and shutting the module ‘off’
Did I miss something simple again? :)