@rsiggins
In my test, the module itself returns the right time of the target place converted to my local timezone. Anyway, there may be some special reason for your case.

Of course, the developer should look inside to know what really happened. But as a emergency cure, you can use some monkey-patching before real fixation from the developer.

{
	module: "MMM-ModuleMonkeyPatch",
	config: {
		patches: [
			{
				module: "MMM-OpenmapWeather",
				method: "processWeather",
				patch: function (original, args) {
					const [ data ] = args
					const yourDesiredOffset = 5 * 60 * 60 // 5 hours
					data.sys.sunrise = new Date((data.sys.sunrise + yourDesiredOffset) * 1000).valueOf()
					data.sys.sunset = new Date((data.sys.sunset + yourDesiredOffset) * 1000).valueOf()
					original(data)
				}
			},
		]
	}
}

@sil3ntstorm
I have never seen that symptom and have no idea to guess what happened.

Here are general methods to deal with the error;

1. Backup your current config.js
2. Try the original config. You can restore it from config.js.example

• If you still have an issue even with the original config, one of MM/OS/HW might be the reason.
  • Remove MM, then reinstall clearly again;
  • Not solved with newly installed MM; Format your SD card and reinstall OS. Then, reinstall MM.
  • Still not solved; your HW might have some issues.
• If you have no issue with the original, the issue probably came from one of the 3rd party modules;
  • Try adding the module one-by-one on the original config / Or you can remove the suspicious module one-by-one from your config.

@sdetweil
Ah, I misunderstood those identifiers are module name not class name.

@JeffreyDaro
To save the daily quota,

• Specify the album to scan, not whole or many albums. Scanning will consume your Quota, And the number of files in target albums will also affect consumption.
• You can only show 8640 pictures in a day at most, even with 10 seconds. With 60 seconds, you can show around 1400 pictures per day. If you have thousands of pictures in the album, unused pictures would also scanned. (scan 50 pictures would consume 1 call) It could be more efficient.
• Let’s compute: If you have 5000 pictures in your target album, you will consume 100 calls per scan, and to serve each image, at least 1 call per image would be consumed. But most of the scanned pictures would not be used at all.
• So, optimise your album. Carefully collect/select pictures to be shown with a proper number. Gather the pictures in one album like 'MM Wallpaper". Keep the number as low as possible, and assign longer updateInterval as some minutes, not seconds. It will help your quota consumption.

@sil3ntstorm
Very mysterious symptom.
And… The duplicated clocks are displaying different times quite differently! I cannot guess how this could happen.
Could you share the whole screen? because some modules seem duplicated, but some don’t, and I want to see where the duplications are placed.
(And your config.js also)

@sdetweil
You are right.
However the example seems somehow ambiguous (though config description) It might mislead someone.(like @UncleRoger or me) :D

@Kelemvor

@sil3ntstorm
It seems not all the config (because, you probably have news module.)
Do you have any module for position/page control?

[UPDATE] 1.7.1

• ADDED useMarquee config
• ADDED noMarquee event Object attribute
  From now, too long title will be rolling as marquee or ticker style.
  

@Kelemvor

.CX3A .cw {
  display: none;
}