MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast

motdog

So I am working on two mirrors. The first set up this module with no problem I created a new api key for the second mirror and when the forecast shows, its missing a day. Today is Friday but when I use this config, the first date showing up in the forecast is Sunday. Makes no sense.

Help please

	{
			  module: "MMM-OpenWeatherMapForecast",
			  header: "Kansas City Weather",
			  position: "top_right",
			  classes: "default everyone",
			  disabled: false,
			  config: {
			    apikey: "xxxxxxxxxxx",
			    latitude: "39.0997",
			    longitude: "94.5786",      
			    iconset: "5c",
		            concise: false,
			    maxDailiesToShow: 5,
			    showHourlyForecast: false,
			    forecastLayout: "table"
  }
},

mielu80

@j-e-f-f
Big thanks to you,sir !
Now the module is just perfect for me,everything is exactly as I wished.

swvalenti

@j-e-f-f here is my config and see the picture, I would like to only see the alert in red and the first line “elevated risk of wildfire”. That doable? Sorry for all the questions on this I’m trying to work the problem.

.MMM-OpenWeatherForecast .weather-alert .weather-alert-description {
    display: 1;
},
.MMM-OpenWeatherForecast .weather-alert .weather-alert-source {
    display: none;
},
.MMM-OpenWeatherForecast .weather-alert .weather-alert-description {
  -webkit-line-clamp: 2; /* adjust this as desired */
}

goldyfruit

Just starting to use it, changed few settings and I’m all set.
Great job!

Stoffbeuteluwe

Great module thank you …Jeff

motdog

I am finding a weird quirk. For the future forecast days once noon local time hits, the next day forecast disappears

Today it showed Friday as a forecast day, after noon hit the next 3 days shown in forecast are sat, sun & Mon.

My config is posted above

j.e.f.f

@motdog let me look into this. My code assumes the first daily forecast is “today” and starts with the second one in the collection. It’s possible this is something the API does and I just hadn’t noticed before. It would make sense because I’ve typically worked on this module during the morning. Will test later.

0m4r

@j-e-f-f can it be a timezone issue?
are the APIs expecting time in UTC? Moment does operates on user timezone (or browser timezone in this case)

j.e.f.f

@0m4r If it is then it’s a bug in the API. The API is supposed to return all data time shifted to the time zone for the long/lat you specify.

I should know more soon. Running a test right now and just waiting for the clock to tick past noon.

j.e.f.f

@0m4r Still troubleshooting this. I don’t see this happening when I use my own long/lat. Will try with yours, but I will need to wait until it ticks past 12:00pm your time. (I’m in London, so will need to check later this evening).

One thing I did notice, though… the long lat you have in your config is for Shanghai, China, not Kansas City. You forgot the “minus” sign in front of the longitude property. Maybe that fixes it?