APi 2.5 to be closed in June 2024

[andyblac]

The problem

Just a heads up that OpenWeather One Call API 2.5 to be closed

here os a copy of the email I got.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

OpenWeather

Link to integration documentation on our website

https://www.home-assistant.io/integrations/openweathermap

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @fabaff, @freekode, @nzapponi, mind taking a look at this issue as it has been labeled with an integration (openweathermap) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of openweathermap can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign openweathermap Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

openweathermap documentation
openweathermap source
_{^{(message by IssueLinks)}}

[fabaff]

Also see csparpa/pyowm#426

[LeiChat]

Do we expect the HA integration to fail when they turn off 2.5 (if we have migrated to 3.0) ?

Are the end points different?

I have completed the migration to One Call 3.0 on openweathermap.org and, unless I am mistaken, it didn't change the API key I had previously generated for my Home Assistant integration.

[ronytomen]

Do we expect the HA integration to fail when they turn off 2.5 (if we have migrated to 3.0) ?

Are the end points different?

I have completed the migration to One Call 3.0 on openweathermap.org and, unless I am mistaken, it didn't change the API key I had previously generated for my Home Assistant integration.

Quoting the email:

One Call 3.0 is free 1,000 calls/day   One Call 3.0 offers a flexible monthly subscription with a ‘pay-as-you-call’ scheme. You have 1,000 calls/day for free and pay only £0.0012 for each additional call. Please note, the OneCall 3.0 subscription requires credit card details. We use your payment card details only for those calls that go beyond the free limit. If you do not want to exceed a free limit you can always set a daily threshold for your account. You don’t need to get new API keys, all your current API keys will work with One Call 3.0 after subscription.

Highlighting the part I think is important to note. :)

You migrated your account, the OneCall 2.5 still works because it hasn't been shutdown and that is what Home Assistant is currently using. I'm not sure if a new key will have to be generated once Home Assistant is using the OneCall 3.0 API, but worse case is you have to, best case is it just works. :)

[jeffgeorge]

Are the end points different?

There's a new versioned endpoint URI per their docs:

https://api.openweathermap.org/data/3.0/onecall?lat={lat}&lon={lon}&exclude={part}&appid={API key}

It looks like it should be a drop-in replacement. There's no change to API keys, no change to parameters, and no backwards compatibility breaking changes to the returned data. It looks like the only thing they added to the schema is that they added this field:

summary - Human-readable description of the weather conditions for the day

So . . this should just be a matter of changing out the endpoint URI. 🤞

[pkscout]

There is also this:

csparpa/pyowm#404

It's been open for like 18 months and mostly is just conversations about someone needing to make a change and then someone else saying it should wait until the 4.x version of the library. Rinse and repeat.