MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast

jenga

I am trying to adjust the hours under the hourly forecast to reflect a different time zone. I was reviewing the code and I see UTC references. How can I adjust this to CST?

nitewing76

@jenga Maybe you are having the same issue I am with incorrect current/hourly time & temperature conversion?

lavolp3

@j-e-f-f That looks REALLY tasty! Thank you for the great work!

swvalenti

@j-e-f-f Am I missing a way to turn off current weather alerts? Once a weather alert like high wind or snow it drops my tables down and throws other modules off.

BKeyport

@j-e-f-f As always, great work. 😉

cowboysdude

As of Saturday, May 1, 2021, the free Yahoo Weather API will be retired.

So as more time goes by the free weather api’s are dropping like flies…

jms3700

Thanks For this great job! 👍

MajorC

@cowboysdude it would be nice if someone with knowledge could have a look at the API of www.yr.no

The forecast is very good and they are providing free world wide data.

ebolisa

@j-e-f-f Thanks for sharing.

Does it work on Pi Zero? In my case it doesn’t load. I just see FORCAST and then “Loading…” forever :astonished_face:
Using defaults, no changes made.

j.e.f.f

@jenga said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

I am trying to adjust the hours under the hourly forecast to reflect a different time zone. I was reviewing the code and I see UTC references. How can I adjust this to CST?

The API returns UTC time for everything as well as a timezone offset for the long/lat you provide. The module translates UTC into local time using these two bits of information. Say you’re living in London, but you configure this module with Long/Lat for New York, then the time you’ll see is local to New York. I can’t request a different timezone in the API.

UPDATE

So quick to jump to conclusions am I… this was a bug in my code. OpenWeather documentation says the hourly time forecasts are provided in UTC, and elsewhere in the API response a timezone offset is provided. I took this to mean that in order to see local time for the forecast I needed to add the offset to the hourly time. As it turns out this is not the case. OpenWeather does not explicitly say this anywhere in the docs that I could find, but the JSON response is already translated to whatever local timezone the request was made from. So if I live in London and I make a request for weather in Chicago I’ll see the hourly forecasts in local London time, not in local Chicago time.

I’ve changed the code so that I no longer add the offset to hourly forecast times. Do a git pull in the MMM-OpenWeatherForecast directory, then restart MM. Should be fixed up.