home-assistant / home-assistant.io

:blue_book: Home Assistant User documentation
https://www.home-assistant.io
Other
4.89k stars 7.25k forks source link

Documentation about the update interval on every integration which is using polling #27606

Open N1c093 opened 1 year ago

N1c093 commented 1 year ago

Feedback

It would be really helpful to have a documentation about the update interval on every integration, which using polling. This information is currently missing in the documentation of most integration.

For example on the Spotify integration https://www.home-assistant.io/integrations/spotify:

As an "enduser" you don't know how up to date these information are, which the integration is providing. Only when you have a look inside the code, you know that these information are updated every 30 seconds https://github.com/home-assistant/core/blob/dev/homeassistant/components/spotify/media_player.py#L38

It would also be possible to have this information at the home assistant frontend. In general it would be nice to have this information visible for every user, also if you can't read the sourcecode.

URL

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

Version

2023.5.4

Additional information

Maybe a good place for this information would be up here:

image

home-assistant[bot] commented 1 year ago

Hey there @frenck, mind taking a look at this feedback as it has been labeled with an integration (spotify) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `spotify` 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 spotify` Removes the current integration label and assignees on the feedback, add the integration domain after the command.
N1c093 commented 1 year ago

Additional this doesn't only affect the Spotify Integration. I just labeled it with Spotify, because it was a mandatory field

github-actions[bot] commented 1 year ago

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. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

N1c093 commented 1 year ago

This issue is still the same.

github-actions[bot] commented 1 year ago

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. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

N1c093 commented 1 year ago

Still relevant...

github-actions[bot] commented 11 months ago

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. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

N1c093 commented 10 months ago

Still relevant

github-actions[bot] commented 8 months ago

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. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

N1c093 commented 8 months ago

Still relevant