I can't seem to configure the default clock for my life

Treestanx

I have been trying to change the timezone on the clock module for days. I don’t understand why when I add the config lines it bricks MM. Can someone help me out?

 module: "clock",
        position: "top_left",   // This can be any of the regions.
        config: {
             timezone: 'America/New_York'
}

cowboysdude

@Treestanx you’re missing some parts ;) Rule of thumb… you need to have equal { }
so for every { you need one of }… You’re missing two ;) One at the start and one at the end.

               {
		module: 'clock',
			position: 'top_left',
			config: {
				displaySeconds: false,
				timezone: "America/New_York",
		                     }
	      },

Mykle1

@Treestanx said in I can’t seem to configure the default clock for my life:

Can someone help me out?

I will try to help you.

            {
		module: 'MMM-Globe',
		position: 'bottom_center',
		config: {
		style: 'natColor',
		imageSize: 200,
		ownImagePath:'',
		updateInterval: 10*60*1000
	}
	},
	{
		module: 'clock',
		timezone: 'America/New_York',
		position: 'top_center'
	},
	{
		module: 'calendar',

Here is the clock portion of my config.js file between 2 other modules. Notice how the module before clock ends with },
The clock module should also end with }, as you can see from mine.

From what I’ve learned here, every { needs to have a corresponding } somewhere afterwards in the modules config.
AND, the last } in that modules config needs to have a comma after it. See the module above clock? It has 2 { and
2 corresponding } the last } having a comma afterwards.

I hope this helps. I’ve given some faulty advice before but I’d like to think I’ve helped a few people.

Mykle1

@cowboysdude said in I can’t seem to configure the default clock for my life:

You’re missing two One at the start and one at the end.

You beat me to it, bro. There was no answer when I started and then when I posted, it showed you already made it to the finish line. :thumbsup:

Treestanx

Why is timezone: in config in one example and in the other its under module?

cowboysdude

@Treestanx That my friend you’ll have to ask the guy who wrote it LOL