OpenWeatherMap 3.0 / already_in_progress

[Kaaremi]

The problem

I subscribed to the Free service plan and set the maximum number of calls = 999. I received the confirmation e-mail over 18 hours ago, but the OpenWeatherMap integration keeps giving the message "already_in_progress".

Have I missed something?

What version of Home Assistant Core has the issue?

System Information version | core-2024.1.2 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.6 os_name | Linux os_version | 6.1.71-haos arch | aarch64 timezone | Europe/Helsinki config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.33.0 Stage | running Available Repositories | 1377 Downloaded Repositories | 4 HACS Data | ok

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 11.4 -- | -- update_channel | stable supervisor_version | supervisor-2023.12.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 28.0 GB disk_used | 7.7 GB healthy | true supported | true board

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

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

I contacted OpenWeatherMap on this and they replied as follows:

"While third-party applications may indeed be built upon our products, it's important to note that we do not oversee or control the development process of these applications. Therefore, for any inquiries or issues related to the integration of our API key into a third-party application, we recommend reaching out to their support team or directly contacting the developer of the application you are using."

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

[r0bb10]

also here, same error.

subscribed for the 3.0 free calls, created a new api, after half a day removed the old deprecated entity and added the a new one with the new api, gives this error.

[ElVasco]

Same issue here.

[r0bb10]

fixed by removing the integration -> restarting ha core -> readding integration.

[digiconnz]

I find that when I delete the integration, restart core that the api is now invalid. Any advice?