MMM-OpenWeatherForecast - loading issue

Como

I realize that the api 3.0 is required. I mentioned I signed up for it as seen below.
I also generated a new key which is showing as active. So unless I’m generating keys that are no longer allowed per openweather (which I wouldn’t think is possible), then I’m not sure what the problem is.

sdetweil

@Como yes, as i said, i will debug this when i get nack to my desk on monday

as for my reiteration of the v3.0 api, you said ‘free api’ , and there is no such thing anymore. just trying yo be precise

Como

Got it. Just wanted to make sure I was understanding too as I feel the oneweathermap site could be a little more clear on their keys. Thanks for all your hard work on this!

KristjanESPERANTO

Side note: If you are having problems with MMM-OpenWeatherForecast, make sure you are using Tom Hirschberger’s active fork. You can check this by running git remote -v in the module’s directory.

sdetweil

@KristjanESPERANTO @Como
rather than spend any time on this

rename your existing module out of the way and install
https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast

no config changes I don’t think… (maybe lat/lon for location/locationID)
Tom is very active in supporting his work…

sdetweil

@Como did you get this resolved?

Como

@sdetweil life has been busy. Hopefully I can do it this weekend. I’ll report afterward.

jms3700

I had to change the node_helper.js to call the right api moet in node_helper.js (3.0 instead of 2.5)
sudo nano node_helper.js

    //make request to OpenWeather One Call API

// var url = “https://api.openweathermap.org/data/2.5/onecall?” +
var url = “https://api.openweathermap.org/data/3.0/onecall?” +

This solution works for me

sdetweil

@jms3700 never use sudo for MagicMirror things

jms3700

@sdetweil

Hello Sam,

Indeed, I was wrong to use sudo. Thanks for the reminder!

Jean-Marie