Read the statement by Michael Teeuw here.
MagicMirror using the wrong time
-
@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:
-
@blissb what is the locale above the tz?
-
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!
-
@sdetweil
Locale is:
-
@blissb great info!!! thanks.
this sounds like a bad moment lib. -
@blissb can you show me the list of active modules, in the order in config.js
thx
-
Is there an easier way to get them other than just scrolling through the config.js?
Modules in order:
alert
clock (correct after adding the timezone: option)
calendar
weather (Sunrise time is also 5 hours off - sorry if I failed to mention that earlier) -
@blissb you could grep for ‘module:’
-
@sdetweil
Doh!
-
@blissb I can’t tell you how many times I do that in a week! 😆
how did you upgrade mm?
