Open weather Api 3.0

Peter

@sdetweil ok, I will see what happens when 2.5 stops working.
Have a nice day.
Peter

nkc

Hi Just to clarify - I just need to change the api version number from 2.5 to 3.0 or Do I need to subscribe again for api version 3.0. ?
Thanks,
Neel.

sdetweil

@nkc as I understand it yes. 3.0 requires a payment if you exceed the free limit so you must provide a credit card up front.

aaronaxvig

I found this thread when my usage of the openweathermap.org API stopped working a few days ago. I guess they actually did cut off the API 2.5 users now? Anyways, I have it working using the 3.0 API now. A few comments to help anyone:

I did add my credit card info on my account but I am not 100% sure this was necessary.
I am using the same API key as before.
The locationID value does not appear to work any more. So I have replaced the locationID config lines with lat and lon lines.
The timezone was getting appended to the header so I had to start setting appendLocationNameToHeader to false.

Before example:

{
    module: "weather",
    position: "top_right",
    header: "Hollywood, FL",
    config: {
        weatherProvider: "openweathermap",
        type: "current",
        location: "Hollywood, FL",
        locationID: "4158928",
        apiKey: "xxxxxxxxxxxxxxxxxxxxxx",
        roundTemp: true
    }
},

After example:

{
    module: "weather",
    position: "top_left",
    header: "Mandan, ND",
    config: {
        weatherProvider: "openweathermap",
        type: "current",
        lat: "46.8258",
        lon: "-100.88875",
        apiKey: "xxxxxxxxxxxxxxxxxxxxxx",
        apiVersion: "3.0",
        appendLocationNameToHeader: false,
        weatherEndpoint: "/onecall",
        roundTemp: true
    }
},

sdetweil

@aaronaxvig yes, thanks for articulating that all in one post.

aaronaxvig

@sdetweil You’re welcome! I saw afterwards that there is another thread with similar info but this is the one the search engine led me to.

After a few days of use I can see on the OpenWeatherMap.org website Billing section that I am running somewhere around 600 API calls per day. This is with four weather modules in place (for four different locations). So about 150 calls per day per module. The default updateInterval value is 10 minutes which would be 144 per day in theory. I’m going to bump my non-local ones to a 30 minute setting (careful to specify milliseconds i.e. 1,800,000 but without commas of course).