MMM-OpenWeatherMapForecast Doesn't display imperial units

rslohs

@mykle1 thanks for the suggestion, but that is set to imperial as well.

sdetweil

@rslohs its not “Units”, its “units”

this system is case sensitive, every letter matters

rslohs

@sdetweil that’s what I’m using in the config file.

{
module: "MMM-OpenWeatherMapForecast",
header: "Schoolcraft, MI Weather",
position: "top_right",
classes: "default everyone",
disabled: false,
config: {
apikey: "aaaaaaaa",
latitude: "aaaaaaa",
longitude: "aaaaaa",
iconset: "4c",
concise: false,
forecastLayout: "table",
units: "imperial",
}
},

scumbelly

@rslohs

A little late to weigh in but I can verify that imperial setting does not affect the Pop amount. It remains metric. Everything else is imperial.

Sorry.

scumbelly

@rslohs

Guess what? I was trying to troubleshoot an issue in this module re: scale and noticed the .js file has changed wind calculations and the following…

units: {
accumulationRain: {
imperial: “mm”,
metric: “mm”,
“”: “mm”
},
accumulationSnow: {
imperial: “mm”,
metric: “mm”,
“”: “mm”
},
windSpeed: {
imperial: “mph”,
metric: “m/s”,
“”: “m/s”
}
},

So it looks like imperial might work for you now. I’m not going to test because I need the older .js which I had to modify to get some calculations in kph to work .

Cheers

JohnGalt

My instance of this module also displays rainfall in “mm”, even though I have set units = “imperial” for the MagicMirror system as a whole and also in the module configuration.

I see that the Open Weather site has a page specifying “API response parameters with available units of measurement” (https://openweathermap.org/weather-data). There one finds a parameter table specifying Parameter and Description - as well as columns for “Standard”, “Metric” and “Imperial”.

The interesting thing is this: the table specifies temperatures correctly (“Kelvin”, “Celsius”, “Fahrenheit”) but for rain it calls out “mm”, “mm”, “mm” - or other variants for different fields, e.g.: “mm/hr” and “mm/hour”.

As such, I am inclined to just give up and accept the module’s behavior as a quirk of how Open Weather parses what it is getting from the NWS - but I thought i would see if anyone has a better idea.

kayakbabe

@JohnGalt have you tried MMM-OpenWeatherForecast instead? It seems to work better for me adn it uses the OpenWeather Map api too.

JohnGalt

@kayakbabe - Thanks for the tip. Can you tell me which one you use? A quick web search shows several modules with the same name. These two look like top contenders:

https://github.com/jclarke0000/MMM-OpenWeatherForecast
https://github.com/themaxgoldman/MMM-OpenWeatherForecast

JohnGalt

@kayakbabe PS: another issue with MMM-OpenWeatherMapForecast is that it doesn’t respect the “disabled: true” configuration. I had seen this before and ignored it since the module is active, but when I went in to disable it in preparation for trying one of the others, I am reminded that I cannot just disable it. I CAN put " /* and */ " around the whole thing of course, but that is just clunky, and more importantly may signal more serious coding issues.

JohnGalt

@kayakbabe FWIW, i installed the jclarke0000 module, and so far it looks pretty good - thanks again!