Read the statement by Michael Teeuw here.
MMM-OpenWeatherMapForecast stuck on Loading....
-
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)?
-
@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. -
@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?
-
@anhanyoung try my version. I fixed a loading bug a while back
-
@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
-
@elorand
This worked for me. Great work! -
@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!
-
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.”
-
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.
-
@postb8822 I have updated my fork
https://github.com/sdetweil/MMM-OpenWeatherMapForecast
actually in node_helper.js
