v2.29.0 weather module issue

[MarcLandis]

@kent79 from openweathermap.com:

"Dear OpenWeather user,

We would like to inform you about our plans to complete the migration from One Call 2.5 to One Call 3.0 that started 2 years ago. In line with this, access to One Call 2.5 will be finally closed in June 2024.

One Call 3.0 provides you with significantly advanced business-demanded features such as a minute forecast for 1 hour, 4 days forecast for any timestamp, a daily forecast for 8 days, including a human-readable summary, historical data (45-year archive) for timestamps, and with daily aggregation, 1.5-year long-term forecast with daily aggregation, and others."

So V2.5 is only working because openwaethermap didn’t fully shut it down even the deadline is over. It can happen any day.

[kent79]

@MarcLandis

I see. Thank you for your quick reply. Any free API is available now? I will move

[MarcLandis]

@kent79 V3 is free for 1000 calls a day and unless you update the weather every minute you probably won’t reach that limit.

[kent79]

@MarcLandis

Thank you for information

[dawookie1979]

Hi,

i have same issue. I have signed up for the v3 api. Does anyone have a config for me to copy my api into?

my code:
{
module: “weather”,
position: “top_left”,
header: “Weather Forecast”,
config: {
weatherProvider: “openweathermap”,
type: “forecast”,
location: “Haverhill”,
locationID: “2647310”, //
apiKey: “LEFT BLANK”
}

[reilley]

@dawookie1979 - Be sure to add apiVersion: ‘3.0’ to your config

[dawookie1979]

@reilley Hello, where do i add it? can you help me edit my script?

Thanks

[sdetweil]

@dawookie1979 see the documentation. its a property in the config section of the weather module configuration

documentation is linked from the top menu here

[Andreas1956]

@MarcLandis
i only added

apiVersion: “2.5”,

to my config, now its all fine again.

[sdetweil]

@Andreas1956 tgat means you gave the old apikey, which will fail ‘soon’