Apply color to future events in CalendarExt3

kkmirr04

@sdetweil
I do have color on the events list - hopefully this is what you were asking for

I would love to have it broken back out into two separate lists, but when I do that and integrate MMM-Pages, it refuses to load the second calendar stream on the events list and also into the calendar. Its like it just refuses to go out and check.
I think its a limitation of the Pages module, I’ve got it setup for the classes configuration. You can call the same module on different pages, but it doesn’t seem like I can call the default calendar module twice on the same page. I haven’t done much research on the Pages issue, thats my next one to tackle.

Interestingly, looking at the CalendarExt3 view today - none of the future events have color applied to them:

Think I got the code block correct this time - thanks for pointing that out to me.

{
      module: "MMM-CalendarExt3",
      classes: "page1",
      position: "bottom_bar",
      title: "",
      config: {
        mode: "week",
        instanceId: "main",
	showWeekNumber: false, 
	//useSymbol: true,
	//displayLegend: true,
        maxEventLines: 10,
	//useWeather: true,
        firstDayOfWeek: 0,
        calendarSet: ['xx_cal', 'yy_cal'],
        
      }
    },

sdetweil

@kkmirr04 ok, there is a quirk in the EXT3 family of modules .

They don’t know when the messages are coming. And don’t want to flash the screen with changes each time they arrive.
Some events of today from cal 1 and more from cal 2 at a different time

So they use a refreshInterval default 15 minutes

But you don’t want to wait 15 mins for the first draw.
So they have another setting waitFetch:5 seconds

After startup wait waitFetch time and draw whatever events have arrived. Even if none

THEN you have to wait refreshInterval time

You have both at default

A little downside on the waitFetch is you get NOTHING til it expires

sdetweil

Another question. When did you install ext3

You DID run npm install the that module folder right?

kkmirr04

@sdetweil

I believe ext3 was one of the first modules I installed when I started everything this weekend. I do remember having some errors so theres a good chance I messed something up. I just ran npm install again and it processed fine, but no changes on the functionality.

Would it make sense to delete out the folder and try downloading / configuring the module again?

sdetweil

@kkmirr04 no, there was a fix a couple weeks ago, but if you just loaded it, should be fine

Can you add waitFetch:20000,

To the EXT3 module config

sdetweil

@kkmirr04 can you try release 2.36 just released.

kkmirr04

I tried adding the waitFetch and updating and no changes on my end. Do you think doing a clean install might be the next best step?

sdetweil

@kkmirr04 can you show the default cal and ext3 on the same page. With the same events.

Can you remove the calendarSets from the ext3 config

npm install in the ext3 module folder is enough

kkmirr04

@sdetweil Here is the events with the calendar

Remove the calendar sets and then run npm install again? I did see there is an update for my NPM - should i do that update too?

I also just noticed theres an error with CalExt3 when I close MM
calext3 error.png

sdetweil

@kkmirr04 thanks. I will try to test this out in a little bit

No, ignore the npm message

Yes, we found a bug in MagicMirror when looking for module updates. No harm done

sdetweil

@kristjanesperanto

can you explain this? the default cal shows colored, but Ext3 does not

I can duplicate, text not colored in Ext3

Screenshot at 2026-05-04 17-31-42.png

but pop is all colored.

Screenshot at 2026-05-04 17-31-49.png

sdetweil

@kkmirr04 on your second cal instance not showing

can you show the config, xxx out the cal url…

I am using pages, with ext3 on diff and cal on diff without problem… (except for ext3 color)

kkmirr04

@sdetweil I think I might’ve just found its related to the month / week views of Ext3…

This is how I have it now:

{
			module: "calendar",
			classes: "page0",
			header: "What's Poppin'",
			position: "top_right",
			config: {
			   colored: true,
				calendars: [
					{
						name: "xx_cal",
						color: 'yellow',
						fetchInterval: 7 * 24 * 60 * 60 * 1000,
						symbol: "calendar-check-o",
						url: "basic.ics"
						
					},
				{
						name: "yy_cal",
						color: 'green',
						fetchInterval: 7 * 24 * 60 * 60 * 1000,
						symbol: "calendar-check-o",
						url: "webcal"
					},
				
				],
			    
			}
		},

When I separate them to two instances, this is the code I have:

{
			module: "calendar",
			classes: "page0",
			header: "XX Calendar'",
			position: "top_right",
			config: {
			   colored: true,
				calendars: [
					{
						name: "xx_cal",
						color: 'yellow',
						fetchInterval: 7 * 24 * 60 * 60 * 1000,
						symbol: "calendar-check-o",
						url: "basic.ics"
						
					},

					],
				}
			},
{
			module: "calendar",
			classes: "page0",
			header: "YY Calendar'",
			position: "top_right",
			config: {
			   colored: true,
				calendars: [
					{
					name: "yy_cal",
						color: 'green',
						fetchInterval: 7 * 24 * 60 * 60 * 1000,
						symbol: "calendar-check-o",
						url: "webcal"
					},
				
				],
			    
			}
		},

And without the Pages module, I do get both to load

I went to add Pages back in with the two calendar instance configuration and have EXT3 on week mode, the second calendar stream does not load

And still no color on calendar view on the second page

But then if I switch to month mode in EXT3 streams are loading in and some colors work - but there’s still two events (from the XX calendar) that loaded but did not get color applied.

As I’ve been messing with it, sometimes on the first run it will load both calendar streams when its in week mode, but it usually doesn’t load it after it runs once. Sometimes in month mode, it still doesn’t load the second calendar, so its not 100% accurate

sdetweil

@kkmirr04 interesting.

Also, you are using an old term , colored
We’ve update to coloredText, symbol,
There should have been a message in the console output at MagicMirror startup

pm2 logs —lines=xxx
xxx is the number of most recent lines in the output, default 15

I saw that when I was testing yesterday

When you get the not displayed, can you
Open the developers console

On the MagicMirror screen, ctrl-shift-I
Select the console tab and scroll around for errors(red text usually)

When one script has a fault in a browser, others will be impacted
Modules are all script

kkmirr04

@sdetweil I’ll keep messing with coloredText, so far everything is staying white when I use that. Here is the errors I’m seeing

sdetweil

@kkmirr04 custom.css not loaded just means there isn’t one. (The default as MagicMirror installed)
If you had used the scripted install it would have created an empty one so this error wouldn’t be there

There is the colored vs coloredText, coloredSymbol warning

No Obvious other errors in that part

Calendar sorting events=0, means there weren’t any?

Just for testing, if you disable pages and ext3
( add disabled:true, after the module:line)
Do both instances of calendar draw and with color?

If yes, then set disabled false on ext3

kkmirr04

@sdetweil with both disabled it did draw both instances with color

Then turning EXT3 back on I’ve got no color on any events again

sdetweil

@kkmirr04 that’s ext3 not showing color

In the off chance of some module install fluke
Delete the Mmm-CalendarExt3 folder
Then git clone
And npm install in the folder created by clone

Then restart MagicMirror

kkmirr04

@sdetweil No change unfortunately. Both event streams load fine and with color, but the calendar still is displaying everything just white, except for one event that did come with color

sdetweil

@kkmirr04 just for testing, if you have a mouse on that system
Mouse over the event without color and click. This will show a new view of that event with the rest in blur behind,

Does the text appear in the proper color?
Escape key to exit that view

Could you also add

coloredSymbol:true,

To the base calendar module config.
Next to

coloredText:true