Default Clock wrong after update

[drstang]

@sdetweil Thanks for the reply. Unfortunately - no luck. Still displaying UTC instead of EST.

[sdetweil]

@drstang thx… and you are certain the SYSTEM timezone is set to EST

i can’t upload a pic of the config page on the pi… weird

[drstang]

@sdetweil Yep - did it several times to make sure!

And the Mirror will show EST when I access it via a web browser!

[BKeyport]

@drstang does setting the timezone config option adjust it ?

https://docs.magicmirror.builders/modules/clock.html#configuration-options

[drstang]

@BKeyport thanks but unfortunately that does not work either - it results in the clock module not even loading (unless there was something else I should have adjusted)…

EDIT: I realized I changed the modules config initially, which didn’t work. But I changed the main config (duh - reading is key) and added the config/timezone line, which worked!! thank you!

[BKeyport]

@drstang At least you can override it for now…

[Richard238]

Just updated my MM, clock is showing 18:13 when it’s 11:54…

[sdetweil]

@drstang I don’t understand this, the code does

		if (this.config.timezone) {
			now.tz(this.config.timezone);		

which means it only uses its own config values, not the global config.

when I set it like this

		{
			module: "clock",
			position: "top_left",
			config:{
				displaySeconds:false,
				timezone:"UTC"
			}
		},

it correctly changed the displayed time from 08 (us central time) to 13

if I set it like this

	timeFormat: 24,
	units: "metric",
	timezone:"UTC",
	modules: [

it did not change the displayed time (as expected)

[BKeyport]

@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 with timezone config item.

[sdetweil]

@BKeyport correct,

so a ‘forced’ timezone would not be set

this is the same code as before.