Read the statement by Michael Teeuw here.
MMM-CalendarExt3
-
@sdetweil Thanks Sam - do you mean “maxEventLines”?
If yes I have set them up to 10 now and still nothing
module: "MMM-CalendarExt3", position: "bottom_center", config: { mode: "month", instanceId: "basicCalendar", locale: 'en-UK', fontSize: '25px', refreshInterval: 10000, maxEventLines: 10, firstDayOfWeek: 1, calendarSet: ["KD", "Tini"], } },
-
@KD no in the base calendar module. default
maximumEntries defaults to 10,
that is where you have broadcastPastEvents:true -
@sdetweil Thank you Sam, i tried that and still nothing…
Here is my config now:
{ module: "MMM-CalendarExt3", position: "bottom_center", config: { mode: "month", instanceId: "basicCalendar", locale: 'en-UK', fontSize: '25px', refreshInterval: 10000, maxEventLines: 10, firstDayOfWeek: 1, calendarSet: ["KD", "Tini"], } }, { module: "calendar", config: { broadcastPastEvents: true, maximumEntries: 100, calendars: [ { name: "KD", className: "KD", url: "https://calendar.google.com/calendar/ical/basic.ics", color: "green" }, { name: "Tini", className: "tini", url: "https://calendar.google.com/calendar/ical/basic.ics", color: "pink" }, ] } },
-
@KD for the short term add
position: “top_left”,
to the calendar module location
let’s make sure it is working
-
@sdetweil Thanks Sam - I now get Loading… than “error in the calendar module check log for more details” and finally no upcoming events… not sure how I have broken it as it was working yesterday… i also tried to replace the default calendar with
git checkout modules/default/calendar/calendar.js
As per one of your other posts in the forum but got "updated 0 (zero) paths from the index…
-
@KD u have to be I the MagicMirror folder for the git checkout to work
you should not have changed that file anyhow
all config is done thru config.js
can u show the output where u start mm?
either npm start
or if you use pm2, thenpm2 logs --lines=50
calendarext3, gets it’s info from the default calendar. so if it has problems, then u get nothing
-
@sdetweil here is an output from “npm start”
kd@raspberrypi:~/MagicMirror $ npm start > magicmirror@2.20.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [11.09.2022 14:00.12.728] [LOG] Starting MagicMirror: v2.20.0 [11.09.2022 14:00.12.736] [LOG] Loading config ... [11.09.2022 14:00.12.743] [LOG] Loading module helpers ... [11.09.2022 14:00.12.745] [LOG] No helper found for module: clock. [11.09.2022 14:00.12.747] [LOG] No helper found for module: MMM-CalendarExt3. [11.09.2022 14:00.13.011] [LOG] Initializing new module helper ... [11.09.2022 14:00.13.012] [LOG] Module helper loaded: calendar [11.09.2022 14:00.13.013] [LOG] No helper found for module: weather. [11.09.2022 14:00.13.554] [LOG] Initializing new module helper ... [11.09.2022 14:00.13.556] [LOG] Module helper loaded: MMM-BackgroundSlideshow [11.09.2022 14:00.13.558] [LOG] All module helpers loaded. [11.09.2022 14:00.13.725] [LOG] Starting server on port 8080 ... [11.09.2022 14:00.13.745] [LOG] Server started ... [11.09.2022 14:00.13.747] [LOG] Connecting socket for: calendar [11.09.2022 14:00.13.748] [LOG] Starting node helper for: calendar [11.09.2022 14:00.13.749] [LOG] Connecting socket for: MMM-BackgroundSlideshow [11.09.2022 14:00.13.750] [LOG] Sockets connected & modules started ... [11.09.2022 14:00.14.038] [ERROR] Whoops! There was an uncaught exception... [11.09.2022 14:00.14.046] [ERROR] Error: listen EADDRINUSE: address already in use 127.0.0.1:8080 at Server.setupListenHandle [as _listen2] (node:net:1372:16) at listenInCluster (node:net:1420:12) at GetAddrInfoReqWrap.doListen [as callback] (node:net:1559:7) at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8) { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '127.0.0.1', port: 8080 } [11.09.2022 14:00.14.048] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? [11.09.2022 14:00.14.052] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues [11.09.2022 14:00.14.099] [LOG] Launching application. MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load swrast driver [11.09.2022 14:00.17.129] [LOG] Shutting down server... [11.09.2022 14:00.17.136] [LOG] Stopping module helper: calendar [11.09.2022 14:00.17.137] [LOG] Stopping module helper: MMM-BackgroundSlideshow kd@raspberrypi:~/MagicMirror $
-
@KD yep, two copies running
pm2 stop all
then u can do npm start -
@sdetweil Apologies yes i had a PM2 job in the background…
Here is the fresh output:
kd@raspberrypi:~/MagicMirror $ npm start > magicmirror@2.20.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [11.09.2022 14:07.14.079] [LOG] Starting MagicMirror: v2.20.0 [11.09.2022 14:07.14.088] [LOG] Loading config ... [11.09.2022 14:07.14.094] [LOG] Loading module helpers ... [11.09.2022 14:07.14.097] [LOG] No helper found for module: clock. [11.09.2022 14:07.14.099] [LOG] No helper found for module: MMM-CalendarExt3. [11.09.2022 14:07.14.368] [LOG] Initializing new module helper ... [11.09.2022 14:07.14.370] [LOG] Module helper loaded: calendar [11.09.2022 14:07.14.371] [LOG] No helper found for module: weather. [11.09.2022 14:07.14.976] [LOG] Initializing new module helper ... [11.09.2022 14:07.14.978] [LOG] Module helper loaded: MMM-BackgroundSlideshow [11.09.2022 14:07.14.979] [LOG] All module helpers loaded. [11.09.2022 14:07.15.149] [LOG] Starting server on port 8080 ... [11.09.2022 14:07.15.168] [LOG] Server started ... [11.09.2022 14:07.15.170] [LOG] Connecting socket for: calendar [11.09.2022 14:07.15.172] [LOG] Starting node helper for: calendar [11.09.2022 14:07.15.173] [LOG] Connecting socket for: MMM-BackgroundSlideshow [11.09.2022 14:07.15.174] [LOG] Sockets connected & modules started ... [11.09.2022 14:07.15.516] [LOG] Launching application. MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load swrast driver [11.09.2022 14:07.19.711] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ - Interval: 300000 [11.09.2022 14:07.19.985] [INFO] BACKGROUNDSLIDESHOW: Reading directory "modules/MMM-BackgroundSlideshow/exampleImages/" for images. [11.09.2022 14:07.20.006] [INFO] BACKGROUNDSLIDESHOW: 171 files found [11.09.2022 14:07.20.057] [INFO] BACKGROUNDSLIDESHOW_NEXT_IMAGE [11.09.2022 14:07.20.058] [INFO] BACKGROUNDSLIDESHOW: reading path "modules/MMM-BackgroundSlideshow/exampleImages//DSC_0038.JPG" [11.09.2022 14:07.20.493] [INFO] Calendar-Fetcher: Broadcasting 0 events. [11.09.2022 14:07.29.492] [LOG] Shutting down server... [11.09.2022 14:07.29.493] [LOG] Stopping module helper: calendar [11.09.2022 14:07.29.494] [LOG] Stopping module helper: MMM-BackgroundSlideshow kd@raspberrypi:~/MagicMirror $
-
@KD said in MMM-CalendarExt3:
Calendar-Fetcher: Broadcasting 0 events.
so, the calendar module didnt find any events…
if you download the ICS file and look inside,
see the BEGIN VCALENDARBEGIN VEVENT
…
.
.
END VEVENTEND VCALENDAR
we can turn on debug to get more detail
change the config.js
logLevel: ["INFO", "LOG", "WARN", "ERROR"],
to
logLevel: ["INFO", "LOG", "WARN", "ERROR","DEBUG"],
then start mm with
npm start >somefile.txt
wait til the cal message comes up
then
ctrl-c (in the terminal window where u did npm start, or ctrl-q (if u didn’t start with pm2, as pm2’s JOB is to keep MM running, so it will restart it after it shuts down unexpectedly