New API keys for OpenWeatherMap OneCall do not work with API 2.5

[mvdnes]

The problem

Currently, the OpenWeatherMap integration uses version 2.5 of the OneCall API.

I started using OpenWeatherMap today, and created an account with a subscription to the OneCall API. The tokens I get seem to be limited to version 3.0 of the API, for version 2.5 I get a 401 response.

Please not that this only goes for the OneCall API, my token does support version 2.5 of the regular API.

Examples:

$ curl -I "https://api.openweathermap.org/data/3.0/onecall?lat=33.44&lon=-94.04&appid=$APIKEY"
HTTP/1.1 200 OK
[...]
$ curl -I "https://api.openweathermap.org/data/2.5/onecall?lat=33.44&lon=-94.04&appid=$APIKEY"
HTTP/1.1 401 Unauthorized
[...]
$ curl -I "https://api.openweathermap.org/data/2.5/weather?q=London,uk&APPID=$APIKEY"
HTTP/1.1 200 OK
[...]

As such, I cannot use the OpenWeatherMap integration when set to OneCall mode.

What version of Home Assistant Core has the issue?

core-2024.3.0

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

OpenWeatherMap

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?

2024-03-10 17:12:19.833 DEBUG (MainThread) [homeassistant.components.openweathermap.weather_update_coordinator] Finished fetching openweathermap data in 0.181 seconds (success: False)

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)}}

[jaamulberry]

Just as an addition. The One Call API 2.5 will be deprecated April 15,2024. This is unfortunately a very recent change as far as I can tell. On March 14th there was no news of deprecation based on the Wayback Machine.
Source: https://openweathermap.org/api/one-call-api
Wayback: http://web.archive.org/web/diff/20240314071002/20240325011731/https://openweathermap.org/api/one-call-api

Reference for transition: https://openweathermap.org/one-call-transfer

[Tom-Heitbrink]

According to mail from openweathermap
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.

Migration info:
https://openweathermap.org/one-call-transfer

[oxc]

Please note, the One Call API 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.

This is probably something that should be noted in the documentation for this integration.

[momoz]

Same, just signed up and new accounts, integration does not work. Says invalid API key