Read the statement by Michael Teeuw here.
MMM-OpenWeatherMapForecast stuck on Loading....
-
@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
-
@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.
