Read the statement by Michael Teeuw here.
Default Clock wrong after update
-
@sdetweil Correction to your statement. timezone is set to null by default.
timezone: null,
- therefore, that if line would evaluate to false unless you override withtimezone
config item. -
-
@sdetweil said in Default Clock wrong after update:
which means it only uses its own config values, not the global config.
This is what I was correcting. ;)
-
@BKeyport but he said,
changing it in the module config did NOT work
but
changing it in the GENERAL config DID work…and it was NOT set in the original config he was using prior to the upgrade
-
@BKeyport said in Default Clock wrong after update:
This is what I was correcting.
I don’t understand…
what I said was
this module only adjusts the timezone when
config :{ timezone: '??????', }
in its module definition
NOT when its set in the global configuration, (before modules defined)
timeFormat: 24, units: "metric", timezone:"UTC", <--- added this for testing, value NOT set in module config modules: [
so I don’t see what you are ‘correcting’
-
-
@sdetweil thats correct - when I changed timezone from ‘null’ to ‘America/New_York,’ the module did not work at all. When I went into the MM config.js and added the timezone line, it worked.
Which now I realize is also a bit frustrating because one of my modules also shows sunrise/sunset times, and thats still off (EST + 4 hrs).
-
@sdetweil and also, yes. prior to the upgrade, my general config was NOT set to a TZ prior to the upgrade. I
-
@drstang said in Default Clock wrong after update:
my general config was NOT set to a TZ prior to the upgrade.
correct… as there is no general timezone property
-
@sdetweil and what also confuses me is if I access the mirror via a web browser, the times are right!
-
@drstang I understand and agree with that…
the clock code runs in the browser… so one can only assume that the
moment code running in the browser is different between instances…