MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. hrt13
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    H
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 5
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Default Calendar Not Loading Events After New MM Update

      @sdetweil

      I think this is it, it may be in the past (I’ll look for a more current one, I didn’t think I was getting events from the past), also, sorry about the ^M’s:

      BEGIN:VEVENT
      DTSTART:20150228T005000Z
      DTEND:20150228T022000Z
      DTSTAMP:20260402T201324Z
      UID:somenumber@google.com
      CREATED:20150130T132500Z
      LAST-MODIFIED:20150130T132500Z
      LOCATION:GIH - Logsdon
      SEQUENCE:0
      STATUS:CONFIRMED
      SUMMARY:Hockey vs. C
      TRANSP:OPAQUE
      END:VEVENT
      
      posted in Troubleshooting
      H
      hrt13
    • RE: Default Calendar Not Loading Events After New MM Update

      @sdetweil Using pm2, I see a lot of “could not expand event” errors. Here’s one:

      " [2026-04-02 12:29:21.274] [ERROR] [calendar] Could not expand event “Hockey vs. C”: ical.expandRecurringEvent is not a function"

      Thanks

      posted in Troubleshooting
      H
      hrt13
    • RE: Default Calendar Not Loading Events After New MM Update

      @sdetweil Hi, I am having the same problem since upgrading this morning (MM v2.35)

      5 calendars, all from Google

      Platform: Raspberry Pi3 B
      OS: Debian GNU/Linux 11 (bullseye)

      I haven’t tried regenerating the calendar links, should I?

      posted in Troubleshooting
      H
      hrt13
    • RE: Failed to Connect to Wayland Display

      @sdetweil I modified your script from earlier to:

      #!/bin/bash
      cd ~/MagicMirror
      
      if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then
         # if WAYLAND_DISPLAYis set, use it, else set to -0
         export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
         npm run start:wayland
      else
         npm run start:x11
      fi
      
      posted in Troubleshooting
      H
      hrt13
    • RE: Failed to Connect to Wayland Display

      @atwist
      I know this may be a bit late, I had the same problem on my Raspberry Pi3 after I updated to the latest MM.
      I spent some time trying to get Wayland running, but wasn’t really successful. Finally, I changed my mm.sh script to:

      #!/bin/bash
      cd ~/MagicMirror

      npm run start:x11

      And that got it working again using: pm2 start|restart mm

      posted in Troubleshooting
      H
      hrt13
    • 1 / 1