mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-05-06 02:58:57 +00:00
f2b0604715
* Update define_custom_polling.md * Update source/_includes/common-tasks/define_custom_polling.md Co-authored-by: Franck Nijhof <git@frenck.dev> * Update source/_includes/common-tasks/define_custom_polling.md Co-authored-by: Franck Nijhof <git@frenck.dev> * tweaks * Move intro from reuse topic to common tasks - the rational does not need to be shown in every integration where the tasks is reused - slight rephrase of the intro section * Reduce redundancy * Tweak * Rephrase --------- Co-authored-by: Franck Nijhof <git@frenck.dev> Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Co-authored-by: c0ffeeca7 <k0ffeeka7@gmail.com>
1.0 KiB
1.0 KiB
title, description, installation_name
| title | description | installation_name |
|---|---|---|
| Common tasks - installation independent | Common tasks | Installation independent |
This section provides tasks that do not depend on a specific Home Assistant installation type or a specific integration. They may be referenced in other procedures.
{% include common-tasks/enable_entities.md %}
Defining a custom polling interval
Creating an automation for polling gives you more flexibility on when to poll.
Why use an automation instead of changing the integration's configuration for polling?
- Not all integrations have a configurable polling interval. The homassistant.update_entity service on the other hand works with most of the integrations, no code changes required.
- An automation allows you to poll whenever you want. For example, if you have a rate-limited solar panel provider with a maximum number of requests per day, you may want to lower/stop the polling at night but poll more frequently during the day.
{% include common-tasks/define_custom_polling.md %}