@angeldeejay that looks great! I will test it and maybe use it instead of or together with my DevContainer https://github.com/HeikoGr/MMM-DevContainer

i filed an issue: https://github.com/jens-maus/node-ical/issues/495

it could be an edge case on my side.
@inteeraymee by any chance: did you use emClient anytime in the past?

only workaround for my setup is to pin to v2.34.0 .
Updating the calendars might be the best solution for me…

@sdetweil @inteeraymee

I have the same issue after updating from MagicMirror 2.34.0 to 2.35.0.

In my case this is not a general calendar config problem and not an auth/fetch problem either. Some calendars still load fine, others fail right after the update, which pointed me to a parser regression.

What I found:

MagicMirror 2.34.0 used node-ical 0.22.1
MagicMirror 2.35.0 uses node-ical 0.25.6
The affected calendars are fetched successfully with HTTP 200
The failure happens during ICS parsing
These are the two of the log lines I get:

[ERROR] [calendar] https://<server>/remote.php/dav/calendars/xx1/?export - iCal parsing failed: Cannot parse: 1-01-15T12:00:00Z
[DEBUG] [calendar] Parsed iCal data from https://<server>/remote.php/dav/calendars/xx2/?export with 130 entries.

The important detail in the broken ICS files is this VTIMEZONE block:

BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:DAYLIGHT
DTSTART:00010325T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:00011028T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE

I tested the exact same ICS file with both node-ical versions:

node-ical 0.22.1: parses successfully
node-ical 0.25.6: fails with Cannot parse: 1-01-15T12:00:00Z
I also verified that if I remove only that W. Europe Standard Time VTIMEZONE block from the failing ICS, the file parses again with node-ical 0.25.6.

So the problem seems to be a regression in node-ical 0.25.x when resolving VTIMEZONE definitions with year 0001 in DTSTART. The calendar fetch itself succeeds; the crash happens while parsing timezone metadata.

This may especially affect calendars coming from Outlook/Exchange/Nextcloud imports, because W. Europe Standard Time looks like a Microsoft-style timezone definition.

@meralith Danke für die Rückmeldung. Ich habe node.js in der Version 20.18.1 jetzt mal als Bedingung in der Readme formuliert.

Falls du noch irgendwoe Probleme, Fragen oder Anregungen hast - einfach melden!

@meralith die Fehler:

0|mm | [2839:0309/111715.890708:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|mm | [2839:0309/111715.891030:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)

kommen sicher nicht vom MMM-Webuntis Modul sondern vom Chrome / Electon und sind vermutlich harmlos.

• Welches Version von Node.js läuft bei dir (node -v)?
• Hast du npm ci --omit=dev (oder npm install ausgeführt?)
• Hast du Sonderzeichen im Anmeldenamen?

Alternativ kannst du mal den qrcode login ausprobieren.

@magicghost our school doesn’t offer this untis feature for us, so i can’t implement and test it. youcan add this feature if you want/can do it

i recently messed up the github repository.

If your last update was ~2 weeks ago you should be fine.
Otherwise your update may fail.

You can get the most recent versions in this way:
There was no new feature in the last days. Only a more robust session management (hopefully) and internal changes.

cd ~/MagicMirror/modules/MMM-Webuntis

# Reset to match the remote repository
git fetch origin
git reset --hard origin/master
npm ci --omit=dev

I’m sorry for any inconvenience!

you can change the encoding in winscp to utf-8 then it should work again

@magicghost yes, just define two modules. or maybe there are some fancy css hacks possible? i choose the first option for my two kids.

@magicghost

this should work as minimum working example for your requirements.

    {
      module: "MMM-Webuntis",
      position: "top_right",
      config: {
        displayMode: 'grid',
        grid: {
          nextDays: 1, // today plus tomorrow = 2 days
          maxLessons: 0, // max lessons per day (0 = no limit)
        },
        students: [
          {
            title: "NAME",
            qrcode: "untis://setschool?...", //your qrcode
          },
        ],
      }
    },

@htilburgs it‘s the original script. My script only tries to run this script locally on demand

@htilburgs i guess your modules are missing the minimal requirements for MagicMirror modules in the packages.json file.

I managed to lower the requirements…

@htilburgs the script looks if it is under an magicmirror/modules folder and takes this as root folder for modules.
otherwise it will take /opt/magic_mirror/modules

if your setup is different you need to adapt the script.

the script itself can be placed independently

@htilburgs now it should work for all installed modules

@htilburgs my main objection was to support the module development. so yes, at the moment it’s a per module check,

you need to put the script inside the folder of the module you want to check - not the MagicMirror folder itself

I am obsessed with the modul checker on the MagicMirror² 3rd Party Modules list…

so, i asked github copilot to implement an instant modul checker script.

technically it clones the modul checker repo, and the local files to /tmp/mm-modul-checker… and installs the deps.

you can find it in recently most active repo:
https://github.com/HeikoGr/MMM-Webuntis/blob/master/scripts/magicmirror-check.mjs

run it: node scripts/magicmirror-check.mjs and you will get:

> mmm-webuntis@0.6.1 check:mm
> node scripts/magicmirror-check.mjs

🔍 Setting up MagicMirror checker...
Fetching checker repository (git-free) via `degit` (first time only)...
📦 Installing dependencies...
✓ Copying local files (excluding node_modules)...
✓ Checking MMM-Webuntis (including uncommitted changes)
🔎 Running full module checks...
🔍 Running ESLint check on package.json...

================================================================================
MMM-Webuntis - MagicMirror Module Check Results
================================================================================

📋 Issues found (1):
  1. Information: There are updates for 1 dependencie(s):
- prettier  ^3.8.0  →  ^3.8.1

================================================================================
📄 Results saved to: magicmirror-check-results.md
Compare with: https://modules.magicmirror.builders/result.html
================================================================================

💡 Tip: Use --cleanup to remove checker files after check

@ochja it should be possible to add support for teacher accounts - but i have no ways to implement/support/test it.

Can you turn on logging (for MagicMirror and Webuntis module) an send me the logs?
You may need to redact the logs before sending me any files.

@OliWer Thank you for your kind words.

with the latest commit (from today) you can add this to your custom.css (older versions have slightly diverent css-classes, but it’s also possible):

.MMM-Webuntis .lesson-cancelled {
  text-decoration: line-through;
}

I’ve extended the readme to explain all possibilities

@RobertMuc

Versuch mal mit 823:

    students: [
      {
        title: 'Name des Kindes',
        studentId: 823,
        // qrcode: 'untis://setschool?url=**example**.webuntis.com&school=**example**&user=**<user>**&key=**<key>**',
        // OR use direct credentials if no QR code:
        username: 'user@example.com',
        password: '<password>',
        school: 'example',
        server: 'example.webuntis.com',  // without https://
      },

und QR Code funktioniert nicht? du kannst die Werte aus der webuntis Oberfläche direkt in den String an die entsprechende Stelle eintragen oder den QRCode mit einer entsprechenden App decodieren und hier den Wert übernehmen.

Der Screenshot zeigt jetzt auf die schnelle die Elternoberfläche, funktioniert bei den Kindern aber genauso: