I have updated my months to be words instead of numbers, and at first it was working, but now it is not hiding the second example module:

1st Example

module_schedule: {from: '* * * FEB *', to: '59 23 28 FEB *', dimLevel: '100'},

For March I am using:

2nd Example

module_schedule: {from: '* * * MAR *', to: '59 23 30 MAR *', dimLevel: '100'}, 

I would expect as of today (February 23rd, 2025) , the FEB would show, and it does. I don’t expect to see the MAR module, but it continues to show.

For now I have it committed it out, but How can I get this to hide for now, and start showing March 1st?

@sdetweil

I’m just saying that’s not what crontab.guru says:

it makes it confusing.

@sdetweil

I have noticed something strange with this module.

In my log I get this message :

[2025-02-01 09:42:27.196] [LOG]   MMM-ModuleScheduler is scheduling MMM-EasyPix using "* * 1 1 *" and "59 23 31 1 *" with dim level undefined
[2025-02-01 09:42:27.206] [WARN]  Month '1' is limited to '29' days.

February has “29” days. Not January.

So the month in my config file that I use from “https://crontab.guru/” doesn’t match what you would expect from this scheduler.

In the documentation it say
“Months 0-11 (Jan-Dec)”

I have updated to use this as a key:

Month
1 = February
2= March
3 = April
4 = May
5 = June
6 = July
7 = August
8 = September
9 = October
10 = November
11 = December

I noticed month “0” doesn’t work for January.

Now that we are in February, it seems to be working after I set what I want to see in February as the month to be “1”

I did some digging, it seems I had the “classes:” wrong in the first one.

It needs to be:

classes: "scheduler",

So more like this:

	{module: "MMM-EasyPix",
		pages: {"Main Calendar": "bottom_right"},
		position: "bottom_right",
		classes: "scheduler",
		config: {
			module_schedule: {from: '0 0 1 3 *', to: '59 23 31 3 *'}, 
			picName: "Leprechaun.png", 
			maxWidth: "75%",        
			updateInterval: 30 * 60 * 1000,
			}
    },

Now, I can’t get anything to show up unless I take out the “module_schedule” like the code below. when add it back in, nothing shows up.

With today being January 30th, 2025 this should fall after “from” and before “to”.

	{module: "MMM-EasyPix",
		pages: {"Main Calendar": "top_right"},
		position: "top_right",
		classes: "scheduler",
		config: {
			/*module_schedule: {from: '0 0 1 1 *', to: '59 23 31 1 *'},*/
			picName: "Yeah_Mon.png",
			maxWidth: "75%", 
			updateInterval: 30 * 60 * 1000, 
		}
    },

Any suggestions on what else I am missing?

I recently tried to install MMM-ModuleScheduler trying to get this suggestion to work:

seasonal characters

I tried to follow the documentation online, but I can’t seem to get the MMM-EasyPix to hind until for now, and then show in March.

This is what I have in my config file:

   {module: 'MMM-ModuleScheduler',
        config: {
        }
    },

	{module: "MMM-EasyPix",
		pages: {"Main Calendar": "top_center"},
		position: "top_center",
		classes: "march",
		config: {
			module_schedule: {from: '* * 1 3 *', to: '* * * 4 *'}, /* march */
			picName: "Leprechaun.png", 
			maxWidth: "75%",        
			updateInterval: 30 * 60 * 1000,
			}
    },

Do I have the config file correct? or is there something else I am missing?

@sdetweil

Yes I see your analysis.

Are you saying that the calendar tool (google) is not separating the event out and making it a new UID?

I still don’t know how to get around that.

When I confirm, should I make a new event and then delete the repeating event for that day?

@sdetweil

yes, I am in the New York time zone.

@sdetweil

This is what I get:

_fix_clipping

• develop
  master

@sdetweil
inside my config:

                        mode: "month",
                        firstDayOfWeek: 0,
			locale:'en-US',
			headerTitleOptions: {month: 'long'},
			fontSize: "20px",
			eventHeight: "22px",
			maxEventLines: "6",
			useWeather: false,
			displayLegend: true,
			useIconify: true,

Yes, I think I have 2.30 and many calendar fixes installed…

Here is they entry for one of the entries on the 1-28-25 (duplicate of the “Alyce” entry)

BEGIN:VEVENT
DTSTART;TZID=America/New_York:20250128T103000
DTEND;TZID=America/New_York:20250128T113000
DTSTAMP:20250129T181146Z
UID:m6rjo4c4r97p3jm4i84aiud6ld_R20250128@google.com
RECURRENCE-ID;TZID=America/New_York:19691231T190000
CREATED:20221212T202854Z
LAST-MODIFIED:20250124T145109Z
LOCATION:**Protected Data ** (removed for protection data)
SEQUENCE:3
STATUS:CONFIRMED
SUMMARY:**Alyce Entry ** (removed for protection data)
TRANSP:TRANSPARENT
END:VEVENT

EGIN:VEVENT
DTSTART;VALUE=DATE:20250128
DTEND;VALUE=DATE:20250129
RRULE:FREQ=WEEKLY;WKST=SU;INTERVAL=2;BYDAY=TU
DTSTAMP:20250129T181146Z
UID:m6rjo4c4r97p3jm4i84aiud6ld_R20250128@google.com
CREATED:20221212T202854Z
LAST-MODIFIED:20250124T145109Z
LOCATION:**Protected Data ** (removed for protection data)
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:**Alyce Entry ** (removed for protection data)
TRANSP:TRANSPARENT
END:VEVENT