MMM-CalendarExt3

[MMRIZE]

@almightyyoshi
You can hide it with CSS, or just drop out “position”.

[almightyyoshi]

@MMRIZE Dropping position worked. I thought I’d get an error or blank screen for that. Thanks again!

[luisestrada]

@almightyyoshi Every time i think this is fixed then it comes back again…

I have 3 calendars so I renamed calendar1 and calendar2, as I don’t want these calendars to conflict with CX3.
Then I have my calendar module and dropped the position as I don’t want to show it.
My CX3 loads empty and after a while the information appears, then it goes and then it comes back. I think I have not set up properly the refresh. I’ve tried many combinations but nothing works

{
module: “MMM-CalendarExt3”,
position: “bottom_bar”,
title: “Calendario”,
waitFetch: 10000, // (ms) waiting the fetching of last calendar to prevent flickering view by too frequent fetching.
refreshInterval: 1000 * 60 * 1, // (ms) refresh view by force if you need it.
glanceTime: 1000 * 60 * 1, // (ms) Return to original view when you move to other moment by notification.
//animationSpeed: 2000, // (ms) Refreshing the view smoothly.
rotateInterval: 0,
eventTimeOptions: {
timeStyle: “short”
},
fetchInterval: 1000,
config: {
mode: “week”,
instanceId: “WeeklyCalendar”,
locale: ‘es-CO’,
maxEventLines: 3,
firstDayOfWeek: 0,
weekIndex: 0,
weeksInView: 4,
broadcastPastEvents: true, // <= IMPORTANT to see past events
calendarSet: [‘Cal1’, ‘Cal2’, ‘Cal3’, 'Cal4, ‘Cal5’],
}
},

And Go Jays Go!! :beaming_face_with_smiling_eyes:

Screen Shot 2022-06-06 at 3.14.02 PM.png

[sdetweil]

@luisestrada do you have 3 instances of
module:‘calendar’
?

[luisestrada]

@sdetweil said in MMM-CalendarExt3:

@luisestrada do you have 3 instances of
module:‘calendar’
?

Yes, I have 3 modules, the holidays (shows 3), the birthday calendar (shows 2) and the normal calendar (shows 8).

[sdetweil]

@luisestrada each sends out its own list of entries. maybe calext3 is replacing a with b with c

[luisestrada]

@sdetweil said in MMM-CalendarExt3:

@luisestrada each sends out its own list of entries. maybe calext3 is replacing a with b with c

That’s exactly what i thought, so thats why I created 3 different modules by copying the entire module in a separate folder and renaming it, similar to this: https://forum.magicmirror.builders/topic/14724/run-two-instances-of-the-same-module-sometimes-tutorial

but still, if I have 3 modules called, calendar, calendar1 and calendar2, it does it

[MMRIZE]

@luisestrada
Well, I was worried about just that case when I developed this module - multiple calendar instances. I thought Nobody would use the calendar module like that. So I haven’t considered supporting that case. But I was wrong.

The current behaviour of this module is replacing whole events when the notification arrives, not combining each. So you cannot get proper whole events from multi-emitter of notifications.

I’ll modify the module in a few days to stack each event not replace it. Wait for a little.

[MMRIZE]

@luisestrada
By the way, your configuration is not quite effective. Some options are located in the wrong place, some are invalid.

• All module-specific user configuration should be placed in config: { ... }. Your waitFecth or eventTimeOptions and something more would not be applied.

• there is no fetchInterval or rotateInterval option in CX3.

• broadcastPastEvents is not for CX3 module but for calendar module.

• refreshInterval: 1000 * 60 * 1 means redraw calendar every 1 minute. Is it really needed?

[sdetweil]

@luisestrada the info inside(event broadcast) is still the same
and u didn’t need to do the rename. it supports multiple instances

[sdetweil]

@MMRIZE u can see in config if multiple instances and maybe the ‘from’ on notification

[luisestrada]

@MMRIZE said in MMM-CalendarExt3:

@luisestrada
Well, I was worried about just that case when I developed this module - multiple calendar instances. I thought Nobody would use the calendar module like that. So I haven’t considered supporting that case. But I was wrong.

The current behaviour of this module is replacing whole events when the notification arrives, not combining each. So you cannot get proper whole events from multi-emitter of notifications.

I’ll modify the module in a few days to stack each event not replace it. Wait for a little.

Thank you, I will show you my code so you all can understand the mess I did :beaming_face_with_smiling_eyes:

@MMRIZE said in MMM-CalendarExt3:

@luisestrada
By the way, your configuration is not quite effective. Some options are located in the wrong place, some are invalid.

• All module-specific user configuration should be placed in config: { ... }. Your waitFecth or eventTimeOptions and something more would not be applied.

• there is no fetchInterval or rotateInterval option in CX3.

• broadcastPastEvents is not for CX3 module but for calendar module.

• refreshInterval: 1000 * 60 * 1 means redraw calendar every 1 minute. Is it really needed?

It was supposed to be ten minutes but because I was trying and adding and testing, I forgot to change it back

[luisestrada]

@sdetweil said in MMM-CalendarExt3:

@luisestrada the info inside(event broadcast) is still the same
and u didn’t need to do the rename. it supports multiple instances

All calendar were working under the same name, however i thought it was the cause of the blank CX3 so that’s why i tried to create one version for each module as a last resort

[luisestrada]

My code with the changes based on your feedback (and it seems to be working for now) Thank you!

//Calendar hidden Module
        {
            module: "calendar",
            //position: "top_left",
            header: "Eventos",
            config: {
                broadcastPastEvents: true, // <= IMPORTANT to see past events
                instanceId: "WeeklyCalendar",
                calendars: [
                    {
                        url: "URL1",
                        name: "Cal1", // <= RECOMMENDED to assign name
                        color: "#0760d1", // <= RECOMMENDED to assign color
                        symbol: false
                    },
                    {
                        url: "URL2",
                        name: "Cal2", // <= RECOMMENDED to assign name
                        color: "#2a4d56", // rgb(92%, 33%, 55%), // <= RECOMMENDED to assign color
                        symbol: "birthday-cake"
                    },
                    {
                        url: "URL3",
                        name: "Cal3", // <= RECOMMENDED to assign name
                        color: "#333", // rgb(92%, 33%, 55%), // <= RECOMMENDED to assign color
                        symbol: "bank"
                    },
                    {
                        url: "URL4",
                        name: "Cal4", // <= RECOMMENDED to assign name
                        color: "#3f0101", // <= RECOMMENDED to assign color
                        symbol: "flag"
                    },
                    {
                        url: "URL5",
                        name: "Cal5, // <= RECOMMENDED to assign name
                        color: "#765f02", //rgb(58%, 24%, 45%) // <= RECOMMENDED to assign color
                        symbol: "flag"
                    },
                    ],
            }
        },
// CX3 Module
        {
            module: "MMM-CalendarExt3",
            position: "bottom_bar",
            title: "Calendario",
            config: {
                mode: "week",
                instanceId: "WeeklyCalendar",
                locale: 'es-CO',
                maxEventLines: 3,
                firstDayOfWeek: 0,
                weekIndex: 0,
                weeksInView: 4,
                waitFetch: 1000 * 10, //	(ms) waiting the fetching of last calendar to prevent flickering view by too frequent fetching.
                refreshInterval: 1000 * 60 * 10, //	(ms) refresh view by force if you need it.
                glanceTime: 1000 * 60 * 10,	// (ms) Return to original view when you move to other moment by notification.
                eventTimeOptions: {
                    timeStyle: "short"
                },
                //useSymbol: false,
                calendarSet: ['Cal1', 'Cal2', 'Cal3', 'Cal4', 'Cal5'],
                }
        },

Now these 3 calendars seem not to be conflicting with CX3

{
			module: "calendar2",
			header: "CAL2",
			position: "top_left",
			config: {
				calendars: [
					{
                        url: "CAL2"
                    },
				],
				maximumEntries: "2",
                wrapEvents: true
			}
		},
{
			module: "calendar2",
			header: "CAL3",
			position: "top_left",
			config: {
				calendars: [
					{
                        url: "CAL3"
                    },
				],
				maximumEntries: "3",
                wrapEvents: true
			}
		},
{
			module: "calendar2",
			header: "CAL",
			position: "top_left",
			config: {
				calendars: [
					{
                        url: "CAL"
                    },
				],
				maximumEntries: "5",
                wrapEvents: true
			}
		},

Sorry for the long message

[luisestrada]

@luisestrada said in MMM-CalendarExt3:

My code with the changes based on your feedback (and it seems to be working for now) Thank you!

I talked too fast, I pressed submit and the issue came back :anxious_face_with_sweat:

[MMRIZE]

@luisestrada
By your configuration;

• It will be refreshed every refreshInterval by force. You’ve set up 10 minutes.
• It will be refreshed after 10 seconds(waitFetch) of the last calendar parsed. a more frequent parsing of your calendar would be a more frequent updating view. If your 5 calendars finish their parsing in 10 seconds together, the view will be updated once. Meanwhile parsing your 5 calendars would take dozen seconds sequentially, the view will be flickering. In that case, set waitFetch longer.

Anyway, I’ll release more improved version for frequent CALENDAR_EVENTS in a few days. Plz wait a little.

[luisestrada]

@MMRIZE said in MMM-CalendarExt3:

@luisestrada
By your configuration;

• It will be refreshed every refreshInterval by force. You’ve set up 10 minutes.
• It will be refreshed after 10 seconds(waitFetch) of the last calendar parsed. a more frequent parsing of your calendar would be a more frequent updating view. If your 5 calendars finish their parsing in 10 seconds together, the view will be updated once. Meanwhile parsing your 5 calendars would take dozen seconds sequentially, the view will be flickering. In that case, set waitFetch longer.

Anyway, I’ll release more improved version for frequent CALENDAR_EVENTS in a few days. Plz wait a little.

Thank you @MMRIZE , I took your recommendations.

[luisestrada]

Hi again,

I read I did not have to do anything to get the weather displayed, however I still don’t see it. Any idea why?

[MMRIZE]

@luisestrada
Displaying the weather icon is an experimental feature. It would be applied from the next version of MagicMirror (ver 2.20) which will be released the next July.

At this moment(with the current MagicMirror 2.19), you can try like this;

cd MagicMirror // Your MM installed directory
git pull // to update latest version. If your MM was quite old, you might need additional command `npm install`
git checkout develop // Change the branch to develop version.

You don’t need this method after July.

[sdetweil]

@MMRIZE if they used my script to install they need a different command
see
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code