MMM-ModuleScheduler - Module Schedules and Notifications

[Alvinger]

@ianperrin
It works! It was probably the code update that fixed even though I also simplified the cron expression.

All my other schedules (which hides, not dims, modules) worked before even with arrays having double quotes and leading zeroes. And they still work.

Great work @ianperrin, and thank you for a must-have module!

[ianperrin]

An update to MMM-ModuleScheduler is now available which includes the ability to

• Send notifications using a schedule - thanks for the idea @cowboysdude
• Control how quickly modules are shown/hidden (animationSpeed option)
• Override the name of the class used to identify the modules which have a schedule (schedulerClass option)

Check out the updated documentation for more information.

[cowboysdude]

That is awesome!! You just keep making this better and better!!! Thank you!

[Alvinger]

@ianperrin @cowboysdude
Check out my new module MMM-tvservice in the System section of the forum. I took the idea from @ianperrin when he suggested a module to act on notifications.

[ianperrin]

@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]

@ianperrin The actions available are now also documented in the readme, so noone has to dig through all the code neccessarily. See this section, a table is down below.

[Alvinger]

@ianperrin @Jopyth: sorry, wasn’t aware that MMM-Remote-Control had that ability. I would recommend MMM-Remote-Control instead of MMM-tvservice to the general user as it covers all functionality needed.

MMM-tvservice is more for the linux enthusiast who wants a program to do one thing and one thing only. I am not running MagicMirror through PM2 but rather directly via systemd so I cannot use all functionality of MMM-Remote-Control without editing the source. Also, as I am running through systemd I do not need to prefix the commands with sudo as the service already runs as root.

[MichMich]

Very awesome work on this module! It might be interesting to look at the new show/hide mechanism: https://forum.magicmirror.builders/topic/241/revising-the-show-hide-mechanism/9

[MichMich]

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:

 {
        module: 'MMM-ModuleScheduler',
        config: {
            visibility_schedule: [
                {classes: 'day', schedule: {from: '0 6 * * *', to: '0 22 * * *' }},
                {classes: 'night',  schedule: {from: '0 22 * * *', to: '0 6 * * *' }}
            ]
        }
},

[ianperrin]

@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!