Read the statement by Michael Teeuw here.
one call api open weather
-
@KristjanESPERANTO awesome. thank you for that
-
@KristjanESPERANTO - am I misreading or does MMM-OpenWeatherMapForecast appear on both the first and last list? THANKS for the thorough review!
-
@JohnGalt Thanks for pointing this out. I have corrected it (it’s only in the first list now) :-)
-
@KristjanESPERANTO - FWIW, openweathermap are not being very helpful in this transition.
I see in my notes the API key I am using is from 2023, but I have no record of what version it is, so I went on their site to see… They don’t specify, either.
I sent them an email requesting how to determine whether the key I have is already compliant, or i I need to start working on applications. The response email just repeated the warnings around them deprecating the old and people’s need to replace ver 2.5 keys with ver 3.0 keys.
I did send a follow-up email asking for a response to my specific question o how to know whether a particular key will work into the future, but received no response.
As such, I am beginning to experiment with my development instance to see what I need to do…
-
@JohnGalt well, from their perspective it is very clear
use the new api… if it fails with access denied (or whatever error) then its the wrong key version…
and u can output a message to that effect for users to discover in the log.I am sure that they would tell you , you have to use it in some request, and it will fail if its wrong.
-
@sdetweil – Hi Sam. I guess maybe my central point got lost in transit - which is I just want[ed] to know from openweathermap.org whether they can tell me if the API key they issued last year (around the time it became apparent ver 2 would be deprecated) is a ver 3 or ver 2 key. FWIW, I did try one final time and explicitly asked only whether they can tell me the version of key I have. They did respond to the email, but did not address the question.
Yes, I’m sure you are correct and it probably is simple from their point of view. However, the issue is that they are [apparently] currently servicing both the old and the new APIs, so from the user’s side it is not possible to do what they and you are suggesting and just see if calling with the old key generates an error.
If I run my MagicMirror and the API that openweathermap.org issued me last year is the old API the module will still work, so there is no diagnostic value there. Yes, I do see that when the point in future time comes that they shut down responding to calls using the ver 2 API and only respond to ver 3 - then all our modules that are calling with ver 2 APis and modules using old endpoints will fail.
My goal was to get ahead of this and avoid having the modules fail, or in the alternative having to replace the API keys in every module in every MagicMIrror where it is used - just in case they issued me a ver 2 API key last year.
Thanks again to you and Krisjan for all the help and support!
-
@JohnGalt not lost… we don’t have the answer either.
I have an app I need to change too . and I just edited the source to change the api version from 2.5 to 3.0 and it worked just like before with the
api key that failed on MagicMirror… SO…"https://api.openweathermap.org/data/3.0/onecall?..."note that this is using the onecall interface already
-
@sdetweil - Sam, I know you don’t have the answer either. I guess I was partly venting, and partly trying to be complete so that others who are having issues or questions can see that various of you and us have tried to work this through.
-
I’m trying to convert from MMM-OpenWeatherForecast to something else, but Openweather is confusing me with the API subscription.
at one point, it’s saying 1000 free, then others, it says every call is $.15 – what’s really going on and how to sign up the right way to get the free?
-
@BKeyport 1000 calls per day, no faster than 1.44 minutes between , then something extra over that.
I think the onecall api and key is the only thing. requires a credit card.
