Read the statement by Michael Teeuw here.
MagicMirror using the wrong time
-
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?
-
@sdetweil I have a script that moves the MM directory to backup, gets rid of the various package-lock.json files, then does a git pull && npm install --only=prod --omit=dev
-
@blissb ok. see these
https://github.com/sdetweil/MagicMirror_scriptsand
https://github.com/sdetweil/MagicMirror-backup-restore
I’m wondering if the npm install in the vendor folder failed. that is where moment is loaded
the fact that clock and weather and calendar are all messed up., is pretty interesting
