OpenWeather v2.5 discontinued - not strictly true

[LordLinhey]

The problem

The new Openweather policy is ONLY to migrate all the ONE CALL versions to v3.0, however this does NOT appear to affect the 'FREEMIUM' api key, which is still availble, maybe not as comprehensive but still adequate for most users. So how do I get rid of that annoying Openweather deprecated sign, or is there no support for the freemium api.

One Call API 3.0 works in exactly the same way as the One Call API 2.5, but includes several useful upgrades. For seamless transfer from One Call API 2.5 to the One Call API 3.0 please carefully read the following sections:

and here is the important bit

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

What version of Home Assistant Core has the issue?

2024.6.2

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

[LordLinhey]

The free version uses a cut down v2.5 api not to be confused with the OneCallv2.5. The OneCall is moving to v3, the free version is available to anyone as a new user, even now. Why there is no support for the Freemium version in the integration is the question???? The way around it is to use Node-red to collect the data and send it to HA and forget the integration

[k8gg]

See my attempts trying to clarify the situation, starting # 51 in this thread. https://community.home-assistant.io/t/openweathermap-migration-from-2-5-to-3-0/736609/51?u=k8gg

[k8gg]

And I have opened a feature request, per the mod, petro, in HA forum. https://community.home-assistant.io/t/openweathermap-integration-to-support-the-free-tier-of-the-professional-api/740624

[LordLinhey]

Thank you for taking the time to attempt getting the Free tier professional to be continued. As you quite rightly point out it is working with the present coding, so there is NO development work required, just to continue using it.

My main concern is that I do NOT want yet another Company to hold my credit card details on their systems. There have been so many successful hacks recently that has ended in lost data vital to financial security, which includes even the big players and has personally affected me in the recent past.

However I can see that it is a futile struggle to persuade the developers against the decision that has been made, so my advice is if you don't want to place your credit card data at the disposal others, you can do what I have done, which is to use node-red and with a few simple nodes you will get the data you need into HA. If you need any help with that I can assist you.

On Tue, 18 Jun 2024 at 05:27, k8gg @.***> wrote:

See my attempts trying to clarify the situation, starting #51 https://github.com/home-assistant/core/pull/51 in this thread.

https://community.home-assistant.io/t/openweathermap-migration-from-2-5-to-3-0/736609/51?u=k8gg

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/119615#issuecomment-2174964806, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASL32WF4IZLS5NMZ2RWLRQDZH6ZL5AVCNFSM6AAAAABJILENSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZUHE3DIOBQGY . You are receiving this because you authored the thread.Message ID: @.***>