MMM-OpenWeatherMapForecast stuck on Loading....

sdetweil

@elorand the default weather module still uses 2.5 and it works

chief

Just following up on this thread - I also am on the “free tier” 2.5 API version and when I try to use MMM-OpenWeatherForecast, it is stuck on “Loading”.

Any advice?

elorand

@sdetweil I couldn’t choose the old 2.5 API when I registered as new user to OpenWeatherMap. Therefore I had no other chance than to go with the 3.0 API.

@chief depending on the API you are subscribed to, you need to edit the node_helper.js (as mentioned in my previous post). After editing you should restart your magicmirror.

karsten13

@sdetweil

the default weather module still uses 2.5 and it works

at the moment, yes.

I looked into their api stuff and onecall v2.5 is not mentioned anymore. The normal endpoints weather and forecast are still on v2.5.

Problem: For onecall 3.0 you need a special api key (as already mentioned here) with a subsciption where you have to give your payment data (1000 request free per day, limit is 2000 per day but you can set your limit to 1000 if you want it for free … ).

I think we will get problems/questions to this for the default weather module too.

So (for default weather module) if you use endpoints weather and forecast and old onecall v2.5 everthing works out of the box with old api keys, if someone use new onecall v3.0 he needs an api key for 3.0 and has to set apiVersion: "3.0", in the config …

LemonBrain

@ally
Hi!
There was an error “** ERROR ** Error: socket hang up”
This solution helped:
in the module node_helper.js

var url = "https://api.openweathermap.org/data/2.5/onecall" +

replace with

var url = "http://api.openweathermap.org/data/2.5/onecall" +

(https -> http)
and restart the MM2

yk

Was there an agreed solution to this one? Do we need to subscribe separately to the 3.0 API or does the free subscription doable (works with default weather module)?

LemonBrain

@yk
Hello!
I use a free subscription. This subscription apparently has a problem with https protocol. Found out by randomly studying the weather server’s response in the browser.

anhanyoung

@elorand Hey man, I know this was a little while ago but I’m struggling with this atm. I subscribed to 3.0 but when I look at my services tab, it’s still showing the free version. When I create an API, it doesn’t seem to work even with editing the node helper to the url you posted. Is there a specific way to generate an API from them with 3.0?

sdetweil

@anhanyoung try my version. I fixed a loading bug a while back

https://github.com/sdetweil/MMM-OpenWeatherMapForecast

sdetweil

@anhanyoung I see your key is 3.0, but the code uses 2.5.

module needs a new parameter to allow selecting which api group it’s in and use that when constructing the url

Latch

@elorand
This worked for me. Great work!

Tomcat1977

@LemonBrain This is the solution! Thanks! No API 3.0, no apiversions. THIS IS IT! Thank you very much! It took me a week to find this!

schris88

I just got it working after struggling with it myself for quite a while. Currently, only the 3.0 API is available for onecall, while forecast, etc., still uses version 2.5. That’s why the default weather with forecast is still functioning.

For the MMM-OpenWeatherMapForecast module, you need to subscribe to the onecall 3.0 API, which is now part of a paid subscription. However, 1000 per month remain free, and you can specify the number of API calls per day allowed in your subscription.

In the node_helper.js file of the modules, I updated the API endpoint to the specified 3.0 API from the OpenWeather API: “https://api.openweathermap.org/data/3.0/onecall”.

Hint: The activation of the API may take a few minutes. You can check its status by calling the API in a browser. If you haven’t subscribed yet, the error message will indicate “invalid API key.” While it’s getting activated, it will display “bla bla for onecall 3.0, there is a separate subscription… see prices.”

postb8822

I actually solved this pretty easily after reading all the posts, but not exactly what was posted worked for me.

in the MMM-OpenWeatherMapForecast module director, edit the MMM-OpenWeatherMapForecast.js file.

under defaults, change

Endpoint:

From

“https://api.openweathermap.org/data/2.5/onecall”

To

“https://api.openweathermap.org/data/3.0/onecall”

then use an api key created after you subscribed, this last step may or may not be needed, but coincidentally or not, the last api key I made after making the above change was what worked.

sdetweil

@postb8822 I have updated my fork

https://github.com/sdetweil/MMM-OpenWeatherMapForecast

actually in node_helper.js

postb8822

@sdetweil I appreciate your expertise, that is what got me there, your fork is now 18 publications behind so I think the node_helper.js file that comes with the main install must look a lot different. It contains a call back to the .js file I mentioned, and does not have the url that you can edit in that file any more. Later I also discovered there is a string you can add in the config file that will change that value to 3.0 as well, unfortunate that they made 3.0 incompatible for new users with 2.5, because now the choice is to break all the old installs, or break all the new ones without chasing down this post.

sdetweil

@postb8822 thanks for the heads up

I synched, changed and pushed pr back

KK-King

@sdetweil
I followed your https://github.com/sdetweil/MMM-OpenWeatherMapForecast
– Installation –
Navigate into your MagicMirror modules folder and execute:

git clone https://github.com/MarcLandis/MMM-OpenWeatherMapForecast.git

Enter the new MMM-OpenWeatherMapForecast directory and execute :
#npm install

After that updated the code and restarted service:

Mirror@raspberrypi:~/MagicMirror/modules/MMM-OpenWeatherMapForecast $ sudo vi …/…/config/config.js

…Code below with hiddne API…
{
module: “MMM-OpenWeatherMapForecast”,
header: “Weather”,
position: “top_right”,
classes: “default everyone”,
disabled: false,
config: {
apikey: “XXXXXXXXXXXXXXXXXXX”,
latitude: “47.690900”,
longitude: “43.587770”,
iconset: “4c”,
concise: false,
forecastLayout: “table”,
}
},

$ sudo systemctl restart pm2-Mirror.service

Getting below error:

0|mm | [2024-08-09 12:10:19.206] [LOG] [MMM-OpenWeatherMapForecast] 9-Aug-24 12:10 ** ERROR ** null
0|mm | [2024-08-09 12:15:19.663] [INFO] Newsfeed-Fetcher: Broadcasting 25 items.
0|mm | [2024-08-09 12:20:16.801] [LOG] [MMM-OpenWeatherMapForecast] 9-Aug-24 12:20 ** ERROR ** null

Richard238

Just changed OS to Bookworm and reinstalled MM, stuck with weather modules loading…
For me, @postb8822 's 29th April 2024 suggestion worked just fine, thank you :)