MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Google Calendar error during Authorize

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    2 Posts 2 Posters 119 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      RonR
      last edited by

      I’m brand new to Magic Mirror have gotten my OpenWeather module working now I’m trying to get Google calendar to work. I have gone through the setup and to the Authorize step and it throws errors. I know the request worked because I see the next 10 calendar events on my terminal screen so I have some of it working.

      OH, I and running an RPI 4 with 4 gb ram and MM version 2.32.0

      The error log is:
      0|mm | [2025-07-23 19:03:05.712] [ERROR] MMM-GoogleCalendar Error. Could not fetch calendar: MyGoogleCalendarIDHere Error: Error
      0|mm | Message: Not Found
      0|mm | Stack: Error: Not Found
      0|mm | at Gaxios._request (/home/ron/MagicMirror/modules/MMM-GoogleCalendar/node_modules/gaxios/build/src/gaxios.js:142:23) ***Translate Response???
      0|mm | at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      0|mm | at async OAuth2Client.requestAsync (/home/ron/MagicMirror/modules/MMM-GoogleCalendar/node_modules/google-auth-library/build/src/auth/oauth2client.js:429:18) ****r2 = await this.transporter.request(opts); ************
      0|mm | [2025-07-23 19:03:05.728] [ERROR] (node:1415) UnhandledPromiseRejectionWarning: TypeError: request?.response?.data?.error?.toUpperCase is not a function
      0|mm | at Class.checkForHTTPError (/home/ron/MagicMirror/modules/MMM-GoogleCalendar/node_helper.js:257:44)
      0|mm | at /home/ron/MagicMirror/modules/MMM-GoogleCalendar/node_helper.js:301:30
      0|mm | at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      0|mm | (Use electron --trace-warnings ... to show where the warning was created)
      0|mm | [2025-07-23 19:03:05.731] [ERROR] (node:1415) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

      If you see a series of ‘*’ it is what I found at the line number the error points at.

      Authorize.js is supposed to return a URL to use in MM but I get the errors.

      Thanks in advance for any help.

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @RonR
        last edited by sdetweil

        @RonR i dont know that module. we provide support for google calendars as part of the base
        package. get the ical format url, public or private
        and put that in the url: property
        see the startup config.js which uses a calendarlabs url

        to get the url

        open your calendar in a web browser, select the specific source in the left nav, click the 3 dot menu to the right, settings
        scroll down to sharing, select the ical format url (not embed)
        or secret url

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post
        Enjoying MagicMirror? Please consider a donation!
        MagicMirror created by Michael Teeuw.
        Forum managed by Sam, technical setup by Karsten.
        This forum is using NodeBB as its core | Contributors
        Contact | Privacy Policy