Read the statement by Michael Teeuw here.
MMM-OpenWeatherForecast
-
@Ray yes, many of the apis we use have gone to pay for models. i would plan for more doing the same
there are still some free. Piratesky has a clone of the older Darksky api. check the module list, shown in the header above for the modules using that
-
@sdetweil that’s sad everybody wants money these days
thank you for your help I will certainly try Piratesky -
@Ray to be fair, it costs money to provide the api. especially as the amount of traffic increases.
we were notified by calendarlabs (holiday calendar used as default), that a lot of MagicMirror systems were requesting the calendar every 5 minutes. we changed our rate to once a week, maybe still too fast.
-
@sdetweil I am always want to pay for really good service I’ve even been known to donate to the cause which in something like this I think would be more beneficial
-
I had the same problem . Solved it by adding
apiVersion: “2.5”,Since the default changed from 2.5 to 3.0
-
@Rakutsi the 2.5 api is dead, for a couple months now
-
@sdetweil just wanted to say that it worked for me to do that.
I am new with posting here.
-
I am also struggling with the new api call. I have set the apiBaseURL string and tried a new api key, but still not loading. The openweather site is a bit confusing, how do i make an V3 api key? i only see option for new key. Thanks
-
@megagprime you have to
provide a credit card in case you go over the 1000 requests per day limit -
@sdetweil i did that and have it subscribed, my old key doesnt work and neither does my new key
-
This post is deleted! -
@megagprime comment out the apibase, let the module set it
-
@sdetweil MMM-OpenWeatherForecast has V2.5 as default.
-
@MarcLandis yes we need 3.0
-
-
@MarcLandis shocking, Tom is usually not behind like that
i haven’t checked, is the url unchanged except for the version number?
-
@sdetweil tom has new url in readme apiBaseURL for opencall3
-
@sdetweil yes - all that is needed is …/2.5/… -> …/3.0/…
-
@MarcLandis ok. i have seen some other users post that it had taken some time before the new key worked.
without debugging hard to tell. i expect the fetch would fail 401. authentication failed
-
It seems the default API was changed from 2.5 to 3.0 with the recent update. Even it is (not yet) in the documentation.
Here is what I did:
I inserted in the config.jsapiVersion: "2.5",Since the problem occurred after the recent MM2 Update (and worked fine until then) it was clear, that the update has some doing in that.
Even if the 2.5 API should be down, it is working just fine.
After this change, it works (again) like charm.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login