@kkmirr04 they replace the colored:true which did everything,
Now you can control each separately

Inside the config: { section
Before the calendars: [ list

@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

@MarNog one thing about the ext3 family of modules.

They get the events from the default calendar module. But the events are broadcast by url separately.

Some will take longer than others.

Ext3 doesn’t want to flash the screen every time it receives a block of events. It doesn’t know when the events will come. So, it has its own refreshInterval time (10 mins default), then it draws whatever it has, and then waits again

But, you don’t want to wait 10 minutes for the first display , so it has a second timer

waitFetch:5000, 5 second wait before drawing any events

If the events arrive after 5 seconds, they dont get displayed til refreshInterval time.

So, you can adjust those two to improve your viewing experience

Note that longer waitFetch means more time after start before any events are displayed

If you use pm2 to launch MagicMirror, it captures the log messages about startup and events being broadcast.
You could examine those time stamps to determine how long each cal Might take, and use that as a guide to waitFetch time

The longer waitFetch means no events are displayed after startup til waitFetch expires

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

@smegbadger yes, we have a fix for that. It’s from the updatenotification module.

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

@kristjanesperanto

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

I can duplicate, text not colored in Ext3

but pop is all colored.

@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

@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

@1a2a3a yes…

all should be good now

@1a2a3a yeh, fine, but no wayland info there

I see a diff on my mm.sh

if wayland_display is not set, then I set it to
WAYLAND_DISPLAY=wayland-0
but your scripts use wayland-1

SO, lets try this

edit mm.sh again
change this line

  if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 1 ]; then 

back to

  if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then 

and change this line

export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}

to

export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-1}

and save mm.sh

then

pm2 stop all
pm2 start MagicMirror

@1a2a3a sensitive

name, address, zipcode, apikeys, passwords…

@1a2a3a yeh… weird indeed… those scripts are wayland based…

ok, open a new terminal window
and do

env

to dump out the environment variables…
check to make sure none expose any info you don’t want shown here and paste the cleaned list

@1a2a3a thanks…

@1a2a3a yeh, weird tho

can you show me output of

lsb_release -a
uname -a

weird it thinks wayland, but won’t run that way

@1a2a3a ok, it still thinks wayland is active.

nano  installers/mm.sh

change line

  if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then 

to

  if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 1 ]; then 

ctrl-o,
enter
ctrl-x

then

installers/mm.sh

@1a2a3a

pm2 stop all 
cd ~/MagicMirror
installers/mm.sh

@1a2a3a and MM is up or not?

pm2 status

has the cycle count changed?