Problem installing new module (beginner), CalendarEXT3 not displaying

MMRIZE

@sdetweil @Manino
Maybe your 3 calendars might have tons of events(at least 10) since long long ago time(at least 1 year).
Past events might be too many, so all of the quota for broadcasting was already consumed by the older events.
To test it, remove 3 calendars, try ‘us-holiday’ calendar of the default config example.

If so, check maximumNumberOfDays and maximumEntries of the default calendar module.

I think it is not the bug of that module but unexpected behaviour. Generally, for past events, People will regard newer events than older events as more important. But broadcasting of this calendar module contains older events prior to newer ones.

sdetweil

@MMRIZE said in Problem installing new module (beginner), CalendarEXT3 not displaying:

. But broadcasting of this calendar module contains older events prior to newer ones.

but you could walk from end of list back to before today, and now know forward looking and past looking… keep going back to the start date of the calendar view … this is what I do with a port of your code to another platform…

Manino

@MMRIZE bad news, all my calendars are new. No old event. I’m an apple user and usually not use google calendar at all. :(

And in september it’s kind of few events.

MMRIZE

@Manino
But your picture above post shows you have Google Calendar. Could you send me the real URLs of icals? eouia0819@gmail.com
To represent your symptom, I need real data.

@sdetweil

but you could walk from end of list back to before today, and now know forward looking and past looking… keep going back to the start date of the calendar view … this is what I do with a port of your code to another platform…

AFAIK, without proper maximumNumberOfDays and maximumEntries values, the bunch of broadcasting will be filled with prior events first up to maximumEntries. So the casted payload will not contain recent newer ones.
Is something changed in default calendar?

Manino

@MMRIZE You got mail! Yes, I do have Google Calendar. And it’s all brand new for me. No old event.

MMRIZE

@Manino
I tested URL you sent me. (Green is that one. I hope this will not be too privacy things.)

{
  module: "MMM-CalendarExt3",
  position: "bottom_bar",
  config: {
    mode: 'month',
    locale: 'sv-SE',
  }
},
{
  module: "calendar",
  position: "top_left",
  config: {
    broadcastPastEvents: true,
    calendars: [
      {
        symbol: "calendar-check",
        url: "https://ics.calendarlabs.com/709/45a0bb64/Fun_Holidays.ics",
        color: "red",
      },
      {
        url: "https://calendar.google.com/calendar/ical/7a9...4/basic.ics", // <- Your real iCAL URL
        color: "green",
      },
    ]
  }
},

Manino

@MMRIZE No pivacy things, its ok thank you.

Glad to see it works for you, in that way there is’nt anything wrong with my google calendar. I appreciate you took your time and look it up!

I did copy paste your config into mine and sorry to say but it did’nt work. Then i get back to my own config again but that does’nt work either.

You can see I get the calendar into the default one. But the month is all empty. And I have to choose “lower_third” becuase on “bottom_bar” september is drowning, I can hardly see it then. Something is really wrong. Maybe I have to start from the beginning again. I mean, it works for you so something is really wrong over here.

Manino

@MMRIZE this one is from an all brand new installation of the MM and EXT3. I did end the installation with the ”npm install”. Copy paste your config into mine and got this. I’am clearly doing something wrong but I can’t undestand what to do different.

MMRIZE

@Manino
Let’s test things.

Remove all other modules except calendar and MMM-CalendarExt3 then run again.
1-1) If no issue; Some of other modules might make interference.
1-2) Still happens; Run MM as dev mode (npm run start:dev) => This will show front-end dev console and there might be some useful console log. (or you can populate dev-console on MM with Ctrl+Shift+i or equivalent shortcut keys by your system)
Just in case, the first rendering takes time so wait a while after running it.

Manino

@MMRIZE Can you see something? I takes time for my posts to be accepted but now I have an all band new installation of the MM and the EXT3.

I did comment out(?) all the default models except the calendar. Correct? Still got the same view as above (my latest post), except the clock and date.

manino@raspberrypi:~ $ cd MagicMirror
manino@raspberrypi:~/MagicMirror $ npm run start:dev

magicmirror@2.24.0 start:dev
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js dev

[22.09.2023 09:26.03.030] [LOG] Starting MagicMirror: v2.24.0
[22.09.2023 09:26.03.044] [LOG] Loading config …
[22.09.2023 09:26.03.053] [DEBUG] config template file not exists, no envsubst
[22.09.2023 09:26.03.067] [LOG] Loading module helpers …
[22.09.2023 09:26.03.070] [LOG] No helper found for module: MMM-CalendarExt3.
[22.09.2023 09:26.03.620] [LOG] Initializing new module helper …
[22.09.2023 09:26.03.621] [LOG] Module helper loaded: calendar
[22.09.2023 09:26.03.622] [LOG] All module helpers loaded.
[22.09.2023 09:26.03.640] [LOG] Starting server on port 8080 …
[22.09.2023 09:26.04.084] [ERROR] Whoops! There was an uncaught exception…
[22.09.2023 09:26.04.097] [ERROR] Error: listen EADDRINUSE: address already in use ::1:8080
at Server.setupListenHandle [as _listen2] (node:net:1740:16)
at listenInCluster (node:net:1788:12)
at GetAddrInfoReqWrap.doListen [as callback] (node:net:1937:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:110:8) {
code: ‘EADDRINUSE’,
errno: -98,
syscall: ‘listen’,
address: ‘::1’,
port: 8080
}
[22.09.2023 09:26.04.098] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[22.09.2023 09:26.04.098] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information