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.

    Repeating Google Calendar invites showing up at wrong time

    Scheduled Pinned Locked Moved Solved Troubleshooting
    7 Posts 2 Posters 866 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.
    • M Offline
      mholzma
      last edited by sdetweil

      I have a recurring Google Calendar Event that is supposed to show up at 18:15 however the calendar shows it at 23:15 instead.

      Here is the excerpt from the ICS file.

      BEGIN:VEVENT
      DTSTART;TZID=America/Chicago:20230222T181500
      DTEND;TZID=America/Chicago:20230222T191500
      RRULE:FREQ=WEEKLY
      DTSTAMP:20230426T172808Z
      UID:arhpo9aql0lcctnpcdl0olhevp@google.com
      CLASS:PUBLIC
      CREATED:20220901T003716Z
      DESCRIPTION:
      LAST-MODIFIED:20230426T170307Z
      LOCATION:
      SEQUENCE:2
      STATUS:CONFIRMED
      SUMMARY:6:15 guitar - Sarah
      TRANSP:OPAQUE
      END:VEVENT
      

      And here is a picture of the stock calendar module:

      43cf6be7-187d-47cb-932d-ab11cbec2ec5-image.png

      Do I just need to recereate those entries or is something else going on?

      S 1 Reply Last reply Reply Quote 0
      • S Away
        sdetweil @mholzma
        last edited by

        @mholzma what time is your system set to ? we use that as the base for the calendar

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mholzma @sdetweil
          last edited by

          @sdetweil America/Central. The non repeating invites show up correctly.

          S 1 Reply Last reply Reply Quote 0
          • S Away
            sdetweil @mholzma
            last edited by

            @mholzma I am on central time too… and I see 18:15

            in your config.js change this

            	logLevel: ["INFO", "LOG", "WARN", "ERROR"],
            

            to this

            	logLevel: ["INFO", "LOG", "WARN", "ERROR","DEBUG"],
            

            then start your MM like this from the command line (if using pm2, do a pm2 stop all)

            npm start >somefile.txt

            wait til the calendar is up
            then ctrl-m to minimize MM
            ctrl-c to stop mm

            then edit the somefile.txt
            and look for

            [DEBUG] initial tz=America/Chicago
            [DEBUG] corrected tz=America/Chicago
            

            let me know…

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              mholzma @sdetweil
              last edited by

              @sdetweil, here is the log data I found and nothing seems off.

              [27.04.2023 15:31.17.650] [DEBUG] Event:
              {**<REDACTED>**}
              [27.04.2023 15:31.17.650] [DEBUG] start: Thu Feb 23 2023 00:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.650] [DEBUG] end:: Thu Feb 23 2023 01:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.650] [DEBUG] duration: 3600000
              [27.04.2023 15:31.17.650] [DEBUG] title: 6:15 guitar - Sarah
              [27.04.2023 15:31.17.650] [DEBUG] Search for recurring events between: Thu Apr 27 2023 15:31:17 GMT+0000 (GMT) and Thu Apr 25 2024 23:59:59 GMT+0000 (GMT)
              [27.04.2023 15:31.17.653] [DEBUG] Title: 6:15 guitar - Sarah, with dates: ["2023-05-04T05:15:00.000Z",**<REDACTED>**]
              [27.04.2023 15:31.17.653] [DEBUG] event.recurrences: undefined
              [27.04.2023 15:31.17.653] [DEBUG]  recurring date is Thu May 04 2023 05:15:00 GMT+0000 (GMT) offset is 0
              [27.04.2023 15:31.17.653] [DEBUG]  recurring date is Thu May 04 2023 05:15:00 GMT+0000 (GMT) offset is 0 Hour is 05
              [27.04.2023 15:31.17.653] [DEBUG] Corrected startDate: Thu May 04 2023 05:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.653] [DEBUG] initial tz=America/Chicago
              [27.04.2023 15:31.17.653] [DEBUG] corrected tz=America/Chicago
              [27.04.2023 15:31.17.653] [DEBUG] start date/time=Thu Feb 23 2023 00:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.653] [DEBUG] start offset=-360
              [27.04.2023 15:31.17.653] [DEBUG] start date/time w tz =Thu Feb 23 2023 00:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.653] [DEBUG] event date=Thu May 04 2023 05:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.653] [DEBUG] event offset=-300 hour=0 event date=Thu May 04 2023 05:15:00 GMT+0000 (GMT)
              [27.04.2023 15:31.17.653] [DEBUG] offset
              [27.04.2023 15:31.17.653] [DEBUG] adjust down 1 hour dst change
              [27.04.2023 15:31.17.654] [DEBUG] adjustHours=-1
              [27.04.2023 15:31.17.654] [DEBUG] duration: 3600000
              [27.04.2023 15:31.17.654] [DEBUG] saving event: false
              
              S 1 Reply Last reply Reply Quote 0
              • S Away
                sdetweil @mholzma
                last edited by

                @mholzma this is mine

                 recurring date is Wed May 03 2023 19:15:00 GMT-0500 (Central Daylight Time) offset is 300
                [26.04.2023 18:02.26.846] [DEBUG]  recurring date is Wed May 03 2023 19:15:00 GMT-0500 (Central Daylight Time) offset is 5 Hour is 19
                [26.04.2023 18:02.26.846] [DEBUG] new recurring date2 is Wed May 03 2023 19:15:00 GMT-0500 (Central Daylight Time)
                [26.04.2023 18:02.26.847] [DEBUG] Corrected startDate: Wed May 03 2023 19:15:00 GMT-0500 (Central Daylight Time)
                [26.04.2023 18:02.26.847] [DEBUG] initial tz=America/Chicago
                [26.04.2023 18:02.26.847] [DEBUG] corrected tz=America/Chicago
                [26.04.2023 18:02.26.847] [DEBUG] start date/time=Wed Feb 22 2023 18:15:00 GMT-0600 (Central Standard Time)
                [26.04.2023 18:02.26.847] [DEBUG] start offset=-360
                [26.04.2023 18:02.26.847] [DEBUG] start date/time w tz =Wed Feb 22 2023 18:15:00 GMT-0600 (Central Standard Time)
                [26.04.2023 18:02.26.847] [DEBUG] event date=Wed May 03 2023 19:15:00 GMT-0500 (Central Daylight Time)
                [26.04.2023 18:02.26.847] [DEBUG] event offset=-300 hour=19 event date=Wed May 03 2023 19:15:00 GMT-0500 (Central Daylight Time)
                [26.04.2023 18:02.26.847] [DEBUG] offset
                [26.04.2023 18:02.26.847] [DEBUG] adjust down 1 hour dst change
                [26.04.2023 18:02.26.847] [DEBUG] adjustHours=-1
                [26.04.2023 18:02.26.847] [DEBUG] duration: 3600000
                

                which says your system timezone is set to GMT time,

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  mholzma @sdetweil
                  last edited by

                  @sdetweil, you nailed it! Thank you so much.

                  I needed to add a timezone environment variable to my docker container. Thank you so much for pointing that out!

                  Planning to build a display (not smart mirror) for our kitchen and this was the hold up.

                  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