MMM-Worldclock

[BKeyport]

@macg I doubt there’d be any performance boost, as the whole browser/javascript is constantly scanning for changes. The original code this is based on used the second for the refresh as it assumes the second would be the minimum displayed unit.

There’s really no such thing as idle anymore.

As for CSS - please, adjust it, adding to your custom.css file - and publish what you do here. Sean’s CSS is good, mine is weaker, but I’m learning and playing at the pace my job allows. Changes that I evaluate would help the core will be included.

[MacG]

@bkeyport By updating all of a second, I didn’t get to all the style classes with Chromium’s developer tools. But luckily you had already posted the essential ones.

I cared about the horizontal layout and yours has been tweaked a bit. The first clock with UTC time didn’t get a flag or globe, so it didn’t need to be as wide as the others. The text color and size were adjusted with MM variables. The size is 6px smaller than my standard (24px). The time difference to UTC time was hidden. With “display: none” I had no success, therefore my way over the transparent text.

At the config.js is:
style: ‘top’,
offsetTimezone: null,

And here al my lines for the custom.css:

/* Arrange clocks horizontally */
.MMM-Worldclock .worldtime {
      display: flex;
      flex-direction: row;
}
.MMM-Worldclock .world{
      width: 100px;
}
.MMM-Worldclock .world-0{  /* 1st clock = UTC clock */
      width: 70px;
}

/* Time title font color and size */
.MMM-Worldclock .zone {
      font-size: calc(var(--font-size) - 6px);
      color: var(--color-text-bright);
}

/* Hide time difference to UTC */
.MMM-Worldclock .gap {
      font-size: 1px;
      color: transparent;

The screenshot of this is in my previous post.

For the time zones, I looked here to see which ones are accepted. At first, I thought that America/Texas or America/Houston would be possible. But this is not the case.

[sdetweil]

@macg America/Texas, Houston is really America/Chicago

[BKeyport]

@macg They went for the biggest city in the timezone. I’m annoyed by that too. Los Angeles shouldn’t represent all of Pacific Time, damnit.

[SoleLo]

@macg can you share how you got them to be horizonal?

[MacG]

@solelo With the first eight lines of the posted snippet of my custom.css, you get the horizontal representation. Copy them into your custom.css and adjust the pixel width.

@BKeyport Pick Vancouver or the time zone itself (PST8PDT). :winking_face: That’s why I found the list of possibilities so helpful.

@sdetweil Yes, I had chosen the Windy City then, too.

[SoleLo]

@macg Thanks! I added it to my custom.css but it didn’t change. Is there anything else I should be checking?

[MacG]

@solelo Actually, no. For completeness here are my settings from config.js:

		{
			module: 'MMM-Worldclock',
			position: 'top_left', // This can be any of the regions, best in top_left or top_right regions
			config: {
			// See 'Configuration options' for more information.
				timeFormat: 'HH:mm', //Global time format, as defined in moment.js format()
				style: 'top', // Which way do you want the flag and description from the clock? choices are 'top', 'left','right','bottom'
				offsetTimezone: null, // Timezone you want to show the difference from. null, "", or omitted from config will be UTC.
				clocks: [
					{
						title: "Weltzeit",
						timezone: "UTC",
						// timeFormat: "HH:mm MM/DD", // Time format override. 
						// altflag: "world.png" // if you'd like a flag from a file on your mirror device. 
					},
					{
						title: "Vancouver", // Too long of a title could cause bad text align.
						timezone: "America/Vancouver",
						flag: "ca", // If you'd like a flag from the standard library 
					},
					{
						title: "Boca Chica", // Too long of a title could cause bad text align.
						timezone: "America/Chicago", //When omitted, Local time will be displayed. 
						flag: "us", // If you'd like a flag from the standard library 
					},
					{
						title: "Sydney", // Too long of a title could cause bad text align.
						timezone: "Australia/Sydney",
						flag: "au", // If you'd like a flag from the standard library 
					},
				]
			},
		},

Did you restart MM or do a reload (Ctrl-R)?

[SoleLo]

@macg

I added your custom css but the title is showing overlapped and I have it as style left, should I change it to top like yours?

[MacG]

@solelo Adjust the width to 200px

 .MMM-Worldclock .world {
       width: 200px;
 }

The module may also have an alignment problem on the right side. Further customization of custom.css may be required.

[SoleLo]

@macg Ok thanks I’ll mess around with it some more and see if I can get it customized. I figured it was simple as adding your custom css snippet in but I guess not

[MacG]

@solelo Just try to set the width higher and higher, eventually nothing will overlap anymore. But it will probably be quite wide, with the cities next to the time. Maybe that’s why style: ‘top’ is the better choice.

[sdetweil]

@solelo see this

https://forum.magicmirror.builders/topic/14862/help-with-a-couple-css-issues?_=1632064035932

u can change the styles livee and then save it to custom.css…

note that you can doc the dev window at the bottom too, using the 3 dot menu next to the X to close the dev window

[MacG]

A supplement to the development tools. When you open it, you can select “Sources” and pause script execution with the “pause button” or F8 in the lower third. This makes it easier to get through all the style classes, which otherwise update every second.

[goldyfruit]

I used to install the original woldclock module, just switched to this one and it worked out of the box.

Thanks for the work. :clapping_hands:

[SymmetriC]

How do I center horizontally at the top of the screen instead of left?

[sdetweil]

@SymmetriC put it in the top_center position

[BKeyport]

@sdetweil or top_bar

[SymmetriC]

@sdetweil Thank you! That worked and the solution was easier than I thought! lol

[JohnGalt]

@BKeyport, @ulrichwisser and all: Please let me know if the following questions would be better served under a new topic, but since my issues originated with this older module, and the new module shares the same name I thought it appropriate to post under this topic…

Issue: the old module is no longer supported by the developer, who suggests using a newer module which uses the same module name. After cloning the new module, the instructions call for doing an ‘npm ci’ command, which fails due to a lack of an existing package-lock,json file.

Question: Is there something different I should be doing, o si this something the developer needs to fix?

Old module: https://github.com/BKeyport/MMM-Worldclock
New module: https://github.com/ulrichwisser/MMM-Worldclock
Error Message:

pi@mirror1:~/MagicMirror/modules $ cd MMM-Worldclock
pi@mirror1:~/MagicMirror/modules/MMM-Worldclock $ npm ci
npm ERR! code EUSAGE
npm ERR!
npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm ERR! [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm ERR! [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info

npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-05T17_16_59_150Z-debug-0.log
pi@mirror1:~/MagicMirror/modules/MMM-Worldclock $