MMM-OpenWeatherMapForecast stuck on Loading....

elorand

Hey @ally, I recently ran into the same problem like you.
I followed all instructions given to you from @sdetweil and finally figured out, what the problem was: openweathermap updated its api to version 3.0!
Even if you have a free subscription (limiting to 1000 api-calls a day, which is fine unless you stay above a refreshrate of every 3 minutes), you need to edit the link in node_helper.js from

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

to

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

For the free subscription on API-Version 3.0, you need to provide your credit card information, but you can set the maximum of possible API-calls to 1000, so that you will never ever ran into any costs.

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