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

Please mention the openweathermap integration default polling interval #36749

Open
chwilk opened this issue Jan 6, 2025 · 3 comments
Open

Please mention the openweathermap integration default polling interval #36749

chwilk opened this issue Jan 6, 2025 · 3 comments

Comments

@chwilk
Copy link

chwilk commented Jan 6, 2025

Feedback

I had to go to the code in github and dig around to find the polling interval timeout default for the openweathermap integration. For anybody else who would like to know if the defaults threaten to overflow the 1000/day max API calls, it is useful to know this is set to ten minutes, so no more than 144 calls per day.

URL

https://www.home-assistant.io/integrations/openweathermap/

Version

2025.1.0

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jan 6, 2025

Hey there @fabaff, @freekode, @nzapponi, mind taking a look at this feedback 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 feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign openweathermap Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@fabaff
Copy link
Member

fabaff commented Jan 9, 2025

From my point of view, technical details about the implementation should not be mentioned in the end-user documentation ( General details about the polling interval are located in the Developer documentation). If one wants a deep-dive then the source for the integration is only a mouse click away.

Reported issues about hitting API limitations are usually very quickly resolved. Thus the end-user don't need to worry about that.

@chwilk
Copy link
Author

chwilk commented Jan 9, 2025

I understand and agree with the general idea here, but would urge reconsideration in this particular case.

The end user is expected to subscribe to a service with a free tier that expects below a certain number of calls per day. (1000) For the end user's reassurance, it would be nice to include that the default settings will not overflow that cap. This is really all I'm asking to be added to the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants