OpenWeatherMap Current Weather API broken/removed

[JohnathonMohr]

The problem

First, I'm aware of the deprecation of OneCall API v2.5. However, the OneCall API is a separate subscription from their "Current Weather" subscription (and separate API). This subscription has a truly free tier (which is sufficient for my needs) and doesn't appear to be included in their One Call 2.5 deprecation.

My API key, tied to a Current Weather subscription (free tier) was working just fine in Home Assistant until I updated to 2024.6. The updated integration forces use of the OneCall API. I want to instead use the Current Weather API, which used to work until 2024.6.

My API key continues to work just fine in Hubitat, so I know it's not an issue of "OpenWeather just stopped accepting v2.5 traffic".

Please add the Current Weather API back. I'm sure many others would prefer not to have to give their credit card information to OpenWeather (even if they can configure their subscription to never charge them) when a truly free tier meets their needs.

What version of Home Assistant Core has the issue?

2024.6

What was the last working version of Home Assistant Core?

2024.5

What type of installation are you running?

Home Assistant Container

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?

No response

Additional information

No response

[home-assistant[bot]]

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

[Masterz69]

See nothing in GUI to change API key, Options dialog have only option to switch v2.5/v3.0, but not to enter new key...

[barrelltitor]

I'd also like this functionality re-implemented, I do not want to give them my credit card information.

From their site: Please note that no other products are affected by this change, including other APIs that have ‘/2.5/’ section in their URL.

I also reached out to them via e-mail and they confirmed the freemium API is not being discontinued.

[jeffh2os]

Agreed with above I've verified my api keys still work fine but the integration with home assistant is broken due to the forced change to 3.0 without 2.5 being allowed to still function.

[freekode]

I see, old current and forecast methods are still working. I think I can restore support of it.

[barrelltitor]

Thank you! Yeah it's just the One call API specifically. Other APIs that incidentally shared the 2.5 api version were not deprecated and will still continue to function, including the freemium api which requires just an account and no payment details whatsoever

[JohnathonMohr]

I see, old current and forecast methods are still working. I think I can restore support of it.

That would be greatly appreciated @freekode - thank you!

[k8gg]

So the intension here from 2024.6 really would be to move users away from One Call API v2.5... not necessarily to force everyone to One Call API v3.0...

... after all, there is still this free tier of the Professional API collections that does "Current Weather" and "3-hour 5 days"... which would/should still be sufficient, for the purpose of this OWM integration.

[k8gg]

I hope this helps. I was asking the Customer Support and see whether there is any plan to change the professional products to V3.0 in any way.