From 07acbae2fb1c0d35efa598ff535a6a88984acee5 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 9 May 2018 09:24:31 +0200 Subject: [PATCH] Make it generic --- source/_docs/configuration/platform_options.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_docs/configuration/platform_options.markdown b/source/_docs/configuration/platform_options.markdown index 544c651e4b7..7823868022e 100644 --- a/source/_docs/configuration/platform_options.markdown +++ b/source/_docs/configuration/platform_options.markdown @@ -19,17 +19,17 @@ By setting an entity namespace, all entities will be prefixed with that namespac ```yaml # Example configuration.yaml entry light: - platform: hue - entity_namespace: holiday_house + - platform: your_lights + entity_namespace: holiday_house ``` ### {% linkable_title Scan Interval %} -Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` configuration key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds. +Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` configuration key. In the example below we set up the `your_lights` platform but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds. ```yaml -# Example configuration.yaml entry to poll Hue lights every 10 seconds. +# Example configuration.yaml entry to poll your_lights every 10 seconds. light: - platform: hue - scan_interval: 10 + - platform: your_lights + scan_interval: 10 ```