Read the statement by Michael Teeuw here.
CalendarExt3 and Google Calendar event display
-
@movingfish
MMM-GoogleCalendar
is incompatible with the standard default MM’s calendar module. It spits out incompatible broadcasting notifications, so you should convert it withpreProcessor
ofMMM-CalendarExt3
.Let’s check something in your config.
preProcessor
should be located in config block ofMMM-CalendarExt3
{ module: "MMM-CalendarExt3", position: "bottom_center", title: "Events Calendar", config: { preProcessor: (e) => { if (e.startDate) return e // when event coming from default module, skip conversion. if (e.start?.dateTime) { e.startDate = new Date(e.start.dateTime).valueOf() } else if (e.start?.date) { e.startDate = new Date(`${e.start.date}T00:00:00`).valueOf() } if (e.end?.dateTime) { e.endDate = new Date(e.end.dateTime).valueOf() } else if (e.end?.date) { e.endDate = new Date(`${e.end.date}T00:00:00`).valueOf() } e.title = e.summary e.fullDayEvent = (e.start?.date) ? true : false return e }, ... // Your other configuration } },
- You may need
broadcastEvents: true,
inMMM-GoogleCalendar
module. I don’t know why, but that option is disabled by default unlike the default calendar module.
{ module: 'MMM-GoogleCalendar', header: "My Google Calendar", position: "top_left", config: { broadcastEvents: true, // <-- You may need this calendars: [ ...
- Not related to this issue, but you did something wrong.
- in
mode: "month"
,weekIndex
andweeksInView
are out of sense. It has meaning only inmode: "week"
. en-EN
is not a proper locale. Useen-US
or justen
. (Of course, it depends on where you live,en-GB
,en-IN
,en-AU
, …)- If you set a proper locale, you don’t need to declare
firstDayOfWeek
. That value will be assigned automatically by your locale. - You are refreshing the module every 2 minutes. Is it really needed?
-
@MMRIZE Thank you again for looking into this and the advice. A lot of this was a project on a whim mixed with OpenAI. Overestimated its ability to give coherent css and js.
-
I did not immediately see the preProcessor for MMM-CalendarExt3 in the docs so that is clearly something I missed.
-
After a lot of random tweaks figured I was overcomplicating and went back to the default ‘sample-config’ from the Ext3 module which has been a relief.
**Opinion - is there any greater benefit to the ‘Google secret link’ (calendar) vs OAuth (MMM-GoogleCalendar)? Seems inherent security benefit with OAuth but not sure. That is what started me down using the separate module.
- again - thanks. some easy fixes.
shouldnt need to refresh the module that regularly. will adjust when I go to ‘prod’
Can consider this solved at this point.
As an aside - also want to thank @sdetweil . Anybody reading this in the future make sure to review this page and it will make modifying css much easier.
https://forum.magicmirror.builders/topic/14862/help-with-a-couple-css-issues/4?_=1696523432686 -
-
@movingfish and you can comment out the position for the calendar modules, they will still send broadcast used by ext3
-
@movingfish
Secret ics URL is easier to handle. But your config.js is weaker for peeping. (There is another alternative MMM-CalDAV) -
@MMRIZE said in CalendarExt3 and Google Calendar event display:
You may need broadcastEvents: true, in MMM-GoogleCalendar module. I don’t know why, but that option is disabled by default unlike the default calendar module.
broadcastEvents: true
This solved the issue I had completly, the Google calendar doesnt broadcast the events by default and I just saw the difference in the debug output comparing the normal “Calendar” and the “MMM-GoogleCalendar”.The calendar events from MMM-GoogleCalenda appear correctly after i used broadcastEvents: true in the config.
Cheers :),
Klaus -