@MichMich - some great ideas, keep them coming.
I’ve created issues (or rather enhancements) for these on GitHub - https://github.com/ianperrin/MMM-ModuleScheduler/issues. Feel free to review, comment etc.
@MichMich - some great ideas, keep them coming.
I’ve created issues (or rather enhancements) for these on GitHub - https://github.com/ianperrin/MMM-ModuleScheduler/issues. Feel free to review, comment etc.
@KirAsh4 said in Can somebody with permissions rename my posting bc I have renamed my module...:
It’s confusing to readers when an original post gets changed later. It’s better to make an announcement in the thread. Keep the original for posterity.
Agreed, so would it be possible for creators of threads in the module showcase to have the permission to move comments to the module troubleshooting section and add tags. That way the original showcase remains navigable?
@MichMich said in MMM-ModuleScheduler:
One other feature request:
It would be nice if there is a way to schedule a hide show based on a classname. This way I can give all my modules a class like “day” and “night”, and make a schedule:
Great idea. I was planning on adding a global module_schedule functionality, i.e. the ability to hide all modules at 10pm, rather than having to configure multiple schedules on a per-module basis.
I think the idea of class-based module groups makes for an interesting extension of the idea.
So to take your config example, if the global schedule definition includes the classes property, only those modules with that class are affected. If the global schedule definition omits the classes field then all modules are affected.
One for next week I suspect!
@Alvinger interesting, I’ll check it out.
You may also be interested in taking a look at MMM-Remote-Control. It contains a heap of functions to control your mirror (including turning the monitor off and on, rebooting the pi, restarting the MM process etc) remotely.
I’ve been working with @Jopyth to expose this functionality via the use of sendNotification.
This should allow schedules like:
notification_schedule: [
{notification: 'REMOTE_ACTION', schedule: '30 9 * * *', payload: {action: 'MONITOROFF'}},
{notification: 'REMOTE_ACTION', schedule: '30 18 * * *', payload: {action: 'MONITORON'}}
]
Check out the repository on GitHub - the latest code includes this capability
@Jopyth - another great update. Thanks
I’ve added an issue (feature request really) on GitHub to explore whether the functionality of this module could be exposed to other modules so it could be triggered using sendNotification.
e.g. sendNotification('REMOTE_ACTION', {query: 'MONITOROFF'}
I’ve also drafted a pull request with an idea of how this could be done.
If this could be implemented, then things like turning the monitor on and off or restarting MM could be scheduled using a combination of this module and MMM-ModuleScheduler
Agreed.
And perhaps best practice should be that any module wishing to show/hide other modules should include a config option to toggle the use of the force flag.
Let the user decide!
Does this fit the use case?
ModuleA is configured to be hidden at 9am and shown at 6pm by ModuleB using a schedule.
At 9am ModuleB (the scheduler) hides ModuleA.
At 11am ModuleC (Remote Control) is used to show ModuleA.
At 11:30am ModuleC (Remote Control) is used to hide ModuleA.
At 6pm, ModuleB (the scheduler) shows ModuleA
Am I correct in thinking that without the force flag, neither ModuleB or ModuleC could show ModuleA at 11am or 6pm respectively?
An update to MMM-ModuleScheduler is now available which includes the ability to
animationSpeed
option)schedulerClass
option)Check out the updated documentation for more information.
Having looked at the code, there may be certain circumstances where the module is initially hidden, even when the dimLevel option is defined. I believe this only relates to schedules are defined using arrays with a particular show > dim > show > dim sequence.
I’ve pushed an update to try an fix this, so feel free to update the module and give it a go.
Alternatively, (and also highly recommended) would be to minimise the number of cron jobs create by simplifying your schedule as follows
{
module: "clock",
position: "top_left",
classes: "scheduler",
config: {
// Show at 06:00 and 16:00, then dim to 50% at 09:30 and 22:30 every day
module_schedule: {from: '0 6,16 * * *', to: '30 9,22 * * *', dimLevel: '50'},
}
},
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?