Read the statement by Michael Teeuw here.
MMM-CalendarExt3
-
@chriskar correct
mode:week
weeksInView:3
weekIndex:0 //first week to see, -1 is last week, defaultetc
-
ok thanks, this worked fine!
what about the overlaping issue? css code is mostly AI generated so it probably has a lot of junk in -
@chriskar i do not know on css
he provides lots of control, but wrap seems difficult -
Hi,
I updated to MM 2.32 this morning and ever since then, I have noticed that the CW entry in my MMM-CalendarExt3 is stuck at “CW1”:
I assume the newest changes have something to do with it
Any idea if I can solve this or do I need to wait for a module update ?
Thanks -
@p1lspeda I see the same bug, but not sure where it is
a temp fix is to add this line to the CX3 config section
minimalDaysOfNewYear:1, // week number of 1st week in your country (should be 0 or 1)
there was an open issue on this inthe CX3 repo
https://github.com/MMRIZE/MMM-CalendarExt3/issues/215I posted this workaround there too
-
@sdetweil
Great.
Thanks for help (again!) -
Hi folks,
Trying to get MMM-CalendarExt3 working on my Pi Zero W running MM v2.30.0 and running into an issue where the calendar is blank. Relevant config.js below:
{ module: "calendar", config: { broadcastPastEvents: true, maximumEntries: 10000, colored: true, calendars: [ { fetchInterval: 1* 60 * 1000, symbol: "calendar-check", name: "p_and_b", color: "rgba(255, 0, 0, 1)", url: "..." }, { fetchInterval: 1* 60 * 1000, name: "cal2", color: "rgba(0, 0, 255, 1)", url: "..." } [ } }, { module: "MMM-CaendarExt3", position: "bottom_bar", title: "family dashboard", config: { mode: "month" instanceID: "basicCalendar", locale: 'en-US' maxEventLines: 5, firstDayOfWeek: 1, calendarSet: ["p_and_b", "cal2"] } },
Can anyone help me understand why my monthly calendar is coming up blank and a workaround?
-
@kribbitykrab ok, this is worse on pi 0w
Ext3 gets the calendar events from the default calendar
the calendar module fetches each url separately and broadcasts the events to other modules if they want to use them
but EXT3 doesn’t want to flash redraw the cal each time a block of events show up
so it also has a
refreshInterval
take whatever events have arrived since last time and display ( default 30 minutes)
now there is another tuning thing
if it drew immediately on startup it would be empty, cause startup is faster than fetch. but EXT3 doesn’t know how many cal urls might supply events.
so there is thewaitFetch
config parm (default 5 seconds)
wait that long after startup before displaying any events
then next will be updateintervalpi0w is SOOOOOOO slow ,no events arrive before waitFetch
so next time is updateInterval timeso you can adjust these some
you are probably
impacted by this bug too, timeout on the connection between front and back ends
see https://forum.magicmirror.builders/post/127456 -
@sdetweil As always, thank you for the response!
I added the pingInterval and pingTimeout lines to both MagicMirror/js/server.js and MagicMirror/js/socketclient.js as described in your link.
I have also moved my fetchInterval into the config portion of my calendar module as you requested, and increased it to 10minutes. I added a waitFetch of 10sec into my MMM-CalendarExt3 module config, along with a refreshInterval of 10minutes.
When I run MM now however, I am unable to reach localhost. I get an error on Midori booth that says Could not connect: Connection refused. Potentially something to do with the server.js and socketclient.js fiddling? Appreciate further guidance!
-