Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When setting up OpenWeatherMap, the link to get your API key is incorrect #110000

Closed
MMK21Hub opened this issue Feb 8, 2024 · 7 comments
Closed

Comments

@MMK21Hub
Copy link

MMK21Hub commented Feb 8, 2024

The problem

When you add a OpenWeatherMap integration entity, a hint at the top provides a link to find your API key. However, the linked page doesn't actually contain the user's API key, which creates confusion and slows the process of setting the integration up. A more helpful URL would be https://home.openweathermap.org/api_keys.

What version of Home Assistant Core has the issue?

core-2024.2.0

What was the last working version of Home Assistant Core?

No response

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

Screenshots

A screenshot of the Home Assistant mobile app. A new OpenWeatherMap config entry is being set up. The following URL is mentioned in text at the top of the form: https://openweathermap.org/appid

@home-assistant
Copy link

home-assistant bot commented Feb 8, 2024

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)

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@davidm-glitch
Copy link

this is still a thing

@xs2erwin
Copy link

xs2erwin commented Jun 8, 2024

did anyone resolve this issue? I have the same problem now. Can't get my api-key working.

@rustysponge
Copy link

rustysponge commented Jun 8, 2024

I ran into the same issue because I missed the instructions on the integration's page: https://www.home-assistant.io/integrations/openweathermap/#%EF%B8%8F-important-deprecation-notice - you need to change your subscription with OWM!

Quote from the integration's website:

To continue using the service:
- Visit the OpenWeatherMap website and activate the One Call subscription.
- During activation, you will be prompted for a credit card, but you will not be charged unless you exceed the free tier limits.
- Configure your OWM integration to select mode v3.0.
- Note: Subscription activation may take up to 2 hours.

After completing all steps it took around 20 minutes and everything worked again. To avoid any costs I set the call limit to 1.000 per day to stay within the free tier of OWM. I hope that helps.

@xs2erwin
Copy link

xs2erwin commented Jun 8, 2024

I ran into the same issue because I missed the instructions on the integration's page: https://www.home-assistant.io/integrations/openweathermap/#%EF%B8%8F-important-deprecation-notice - you need to change your subscription with OWM!

Quote from the integration's website:

To continue using the service: - Visit the OpenWeatherMap website and activate the One Call subscription. - During activation, you will be prompted for a credit card, but you will not be charged unless you exceed the free tier limits. - Configure your OWM integration to select mode v3.0. - Note: Subscription activation may take up to 2 hours.

After completing all steps it took around 20 minutes and everything worked again. To avoid any costs I set the call limit to 1.000 per day to stay within the free tier of OWM. I hope that helps.

Did work for me after 1 hour of waiting.
Thanks

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants