Ah feels like also needs to consider “windChill” & “heatIndex”. I’m betting they’re mutually exclusive.
Read the statement by Michael Teeuw here.
Posts
-
RE: default Weather, current with wethergov issues
-
RE: default Weather, current with wethergov issues
@sdetweil , thanks, I did find those but I’m also trying to figure out a way so when I change the code it doesn’t break the existing. I’m just giving it thought now.
To convert kph to mph: *0.621371. I 'm used to MPH and m/s or kph wouldn’t register with me. I can handle temperatures and distance in metric but not wind speeds.
-
RE: default Weather, current with wethergov issues
Okay, I see the issue with windSpeed. The URL returns windSpeed in km_h-1 (k/h), the convertSpeed(metSec) function appears to be m/s. I’m not sure how to fix this for general use. I’ll try to fix it for my use first.
-
RE: default Weather, current with wethergov issues
I figured out the Feels like being 32F, it’s getting a null in the heat index from weather.gov. I’ve added code to check for null and use the currentWeather.temperature instead. I’ll send diffs later (where do I send them?) when I’ve finished with the windSpeed.
if(currentWeatherData.heatIndex.value) { currentWeather.feelsLikeTemp = this.convertTemp(currentWeatherData.heatIndex.value); } else { // If null, set it to the current temperature currentWeather.feelsLikeTemp = currentWeather.temperature; }
Sorry it took so long for me to figure out this env. I’m using the browser to debug now. I’ve not done this much. :-)
-
RE: default Weather, current with wethergov issues
@scumbelly , huge thanks for the help. What URL did you use to get the XML? For weather.gov, I’ve been seeing JSON.
I think I’ll toss in a few log statements and see what weather.gov code is using.
-
RE: default Weather, current with wethergov issues
@scumbelly , the new weather module, the old is call currentweather and weatherforecast. Those are commented out in my config.
-
RE: default Weather, current with wethergov issues
Here’s the weather config section:
units: "imperial", // global ... { module: "weather", //position: "top_right", position: "bottom_left", config: { type: "current", weatherProvider: "weathergov", //Default value: openweathermap //windUnits: "imperial", // this is messed up in the code tempUnits: "imperial", useBeaufort: false, fade: false, // See 'Configuration options' for more information. //apiBase: "https://api.weather.gov/points/", //weatherEndpoint: "/forecast/hourly", // for current lat: 40.25571, lon: -74.39416, } },
I basically get this:
-
default Weather, current with wethergov issues
I’m playing around with Weather/Current/weathergov setting for the US and I see a lot of issue. First the Windspeed is 33 NNW (it’s 7 NNW) and the temperature 54F ‘feels like’ 32F.
When I visit the weathergov API URL for lon/lat I see “5 to 10 mph” instead of a windspeed. My guess is that this may be part of the issue. I’m not really sure how to debug this as some of the javascript looks very different than what I’m used to.
Any pointers on how I can help, please let me know.
-
RE: MagicMirror² v2.15.0 is available don't work.
@sdetweil thanks, I made the changes but the results are the same. I think there’s something else wrong with the weather.gov part of the module.
-
RE: MMM-CalendarExt2: Black Screen
@jack819 , I may have given you bad advice. It shouldn’t cause any issues. Sorry about that.
So starting over, Did you do all of this (and have no errors)?
cd ~/MagicMirror/modules git clone --depth=1 https://github.com/eouia/MMM-CalendarExt2 cd MMM-CalendarExt2 npm install