home-assistant[bot]
commented
4 weeks ago 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)
The problem
With #120178 the API 2.5 can be selected after this whole deprecation topic came in (and caused obviously some confusion like in #119615)... It seems not be true in general that the 2.5 API is deprecated since June 2024...
So, is it intended that the repair still appears when using 2.5? This does not make sense to me if it is an option in the config flow as it is super-confusing to users. I would expect this repair vanishes with the above mentioned PR...
What version of Home Assistant Core has the issue?
2024.8.1
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?
No response
Additional information
No response