MMM-CalendarExt3

[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