My display so far...

[j.e.f.f]

@rudibarani thanks. I’ll take a look tonight when I get home from work.

[j.e.f.f]

@rudibarani Ok try pulling the latest commit. I indeed broke the default timeFormat setting. I didn’t notice because my config was using an explicit configuration option.

[rudibarani]

@j.e.f.f Now its working again, but the timeformat still does not show up in the 24h format:

Thanks a lot and greetings from Germany.

[brandongomez]

I’m sure there’s a way to do this in css but not sure how. I want to make the icon and temperature smaller.

[j.e.f.f]

@rudibarani in your config, set the timeFormat to HH:mm and you shoudl see 24-hour format.

I just tried this. My config looks like this:

    {
        module: 'MMM-MyWeather',
        position: 'top_right',
        classes: 'default everyone',
        config: {
          apikey: '...', // private; don't share!
          pws: 'pws:IONTORON421', //Toronto Beaches
          units: 'metric',
          // other configs omitted for clarity 
          timeFormat: 'HH:mm',  //Set this here
        }
    },

And it looks like this:

[j.e.f.f]

@brandongomez You can target both of these in CSS as follows:

/* Icon */
.MMM-MyWeather .currentWeatherIconWrapper .currentWeatherIcon {
  max-width: 140px;
  max-height: 140px; /* play with these two values to get the size you want */
}

/* temperature text */
.MMM-MyWeather div.large span.bright {
  font-size: 65px;
  line-height: 65px; /* play with these two numbers to adjust text size */
}

[rudibarani]

@j.e.f.f Ah - you are using the moments-timeformat. Now it works :)
I was confused, as the timeformat in the config.js was either “12” or “24”.
Thanks for the clarification!

[j.e.f.f]

@rudibarani Yeah I like using the Moment.js format since it gives you the ultimate flexibility with how you want to display time.

Glad it’s working for you now! :)

[brandongomez]

@j.e.f.f Thanks for the quick response!

[pjkoeleman]

@j-e-f-f
In MMM-MyWeather …
I just saw that the clock for the sunset / sunrise is not displayed in the 24 hour format. Is there any option for setting this? Well searched but not found in the config options.

[j.e.f.f]

@pjkoeleman Let me look into this. Likely overlooked in the code.

[pjkoeleman]

@j.e.f.f
Thanks in advance

[j.e.f.f]

@pjkoeleman Try now. It’s a bit hacky… basically if your time format has a capital H in it, then it formats it in 24 hour time HH:mm, otherwise it will use 12 hour time h:mm a.

I should probably make this a separate time format config parameter, but this should do for now.

[pjkoeleman]

@j.e.f.f
Thanks, is working now like it should be doing.

So the module is not using ‘timeFormat’ as set in the main part of config.js
I thought that it would look and use the settings of ‘language’ and ‘timeFormat’ in the global settings of config.js

[j.e.f.f]

@pjkoeleman not directly, no, as it specifically comes down to how I have it configured. My time format for the forecast table is “h a” (e.g.: “9 pm”). This time format has no minutes, which is fine for the hourly forecast, but doesn’t work for sunrise/sunset. So when rendering the sunrise/sunset time it looks for the presence of a capital “H” in the time format config. If present, sunrise sunset is rendered as “HH:mm” (i.e.: 24 hour time format). Otherwise it is rendered as “h:mm a” (12 hour time format).

The right thing to do is separate sunrise/sunset time format out to its own configuration parameter.

[pjkoeleman]

@j.e.f.f
Thanks for clearing us up.

[brendyburgers]

would it be possible to have a copy of your program have been trying for a while now to come up with something like this, and does it work with touch???

[j.e.f.f]

@brendyburgers much of the above have now become modules. Which one were you interested in?

Sorry to say but none of my modules are touch enabled.

[rrrene]

@j.e.f.f

Hi Jeff, I just put your CSS code in my custom.css.

Unforunately for one Module the line below the header stays the „old“ grey color and won‘t change to your great blue.

What did I do wrong?

Best regards,
René

[j.e.f.f]

@rrrene said in My display so far...:

What did I do wrong?

Most likely nothing :)

If the issue is with just one module, then likely my custom CSS is being overridden with that module’s CSS. You need to inspect the markup to see what styles are being applied to that particular module and then write more specific CSS to override that.

You can access the inspector by starting MM in dev mode npm start dev.