MagicMirror using the wrong time

[sdetweil]

@blissb cool, now find one with Lima

[blissb]

@sdetweil

Not an exhaustive search – but so far every single “Lima” entry has been an all-day event, and I’m not seeing a “saving event” line for any of the ones I’ve checked so far. Here’s an example:
[19.11.2023 18:25.21.190] [DEBUG] Event:
{“type”:“VEVENT”,“params”:[],“created”:“2023-11-14T21:23:37.000Z”,“dtstamp”:“2023-11-14T21:23:54.000Z”,“lastmodified”:“2023-11-14T21:23:54.000Z”,“sequence”:“2”,“uid”:“dd7170db-8f64-43ec-9dca-ed806d4c35a2”,“start”:“2023-11-24T05:00:00.000Z”,“datetype”:“date”,“end”:“2023-11-25T05:00:00.000Z”,“status”:“CONFIRMED”,“summary”:“Judiciary Holiday”}
[19.11.2023 18:25.21.191] [DEBUG] start: Fri Nov 24 2023 00:00:00 GMT-0500 (GMT-05:00)
[19.11.2023 18:25.21.192] [DEBUG] end:: Sat Nov 25 2023 00:00:00 GMT-0500 (GMT-05:00)
[19.11.2023 18:25.21.193] [DEBUG] duration: 86400000
[19.11.2023 18:25.21.194] [DEBUG] title: Judiciary Holiday
[19.11.2023 18:25.21.195] [DEBUG] if no tz, guess based on now
[19.11.2023 18:25.21.195] [DEBUG] initial tz=America/Lima
[19.11.2023 18:25.21.196] [DEBUG] corrected tz=America/Lima
[19.11.2023 18:25.21.197] [DEBUG] start date/time=Fri Nov 24 2023 00:00:00 GMT-0500 (GMT-05:00)
[19.11.2023 18:25.21.198] [DEBUG] start offset=-300
[19.11.2023 18:25.21.200] [DEBUG] start date/time w tz =Fri Nov 24 2023 00:00:00 GMT-0500 (GMT-05:00)
[19.11.2023 18:25.21.201] [DEBUG] event date=Fri Nov 24 2023 00:00:00 GMT-0500 (GMT-05:00)
[19.11.2023 18:25.21.202] [DEBUG] event offset=-300 hour=0 event date=Fri Nov 24 2023 00:00:00 GMT-0500 (GMT-05:00)
[19.11.2023 18:25.21.203] [DEBUG] adjustHours=0
[19.11.2023 18:25.21.203] [DEBUG] Processing entry…

[sdetweil]

@blissb

[19.11.2023 18:25.21.195] [DEBUG] if no tz, guess based on now
[19.11.2023 18:25.21.195] [DEBUG] initial tz=America/Lima

that means the system timezone is set to Lima.

[blissb]

@sdetweil

And yet it is not according to everything I can see.

[sdetweil]

@blissb how about thru the preferences, in the menu, top left on the desktop
this is a pi, yes?

[blissb]

@sdetweil
I know I haven’t said it, but I really appreciate you looking at this… it’s been driving me nuts since the last update messed things up.

I just tested hard-coding the timezone in calendarfetcherutils.js – replaced “moment.tz.guess()” with “America/New_York” on line 29. That has removed the “Lima” entries in the debug log, but it has not corrected the time issue.

Yes, I’m running on a Pi. Here’s what’s in preferences:

[sdetweil]

@blissb what is the locale above the tz?

[blissb]

@sdetweil

On my second MagicMirror I restored the backup of the last version of MM, and made no other changes. The debug info shows no instances of the “lima” timezone, and all times are correct.

I went back to the most recent version, reran with debug, and the “Lima” instance is back, as are the wrong times.

I’ll be reverting to the previous version of MM for the moment, but please let me know if there’s anything else I can do to help with troubleshooting this really annoying issue!

[blissb]

@sdetweil
Locale is:

[sdetweil]

@blissb great info!!! thanks.
this sounds like a bad moment lib.