From 0816d5c88aa9334ec9e1d4efd49932eda6c7e613 Mon Sep 17 00:00:00 2001 From: DeepCoreSystem Date: Wed, 3 Mar 2021 11:36:56 +0100 Subject: [PATCH] Update documentation for the light integration (#16781) Co-authored-by: Franck Nijhof --- source/_integrations/light.markdown | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown index 70b225bb20f..2b492aeb88c 100644 --- a/source/_integrations/light.markdown +++ b/source/_integrations/light.markdown @@ -13,9 +13,17 @@ This integration allows you to track and control various light bulbs. Read the i ### Default turn-on values -To set the default color, brightness and transition values when the light is turned on, create a custom `light_profiles.csv` (as described below in the `profile` attribute of `light.turn_on`). +To set the default color, brightness and transition values when the light is turned on, create a custom `light_profiles.csv`, normally located in the default configuration folder where you find `configuration.yaml`. -The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g., for `light.ceiling_2` the `id` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supercede the `all_lights` default setting. +The `light_profiles.csv` has to have a header. The format of the header is: + +```txt +profile,color_x,color_y,brightness,transition +``` + +The field transition is optional and can be omitted. + +The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g., for `light.ceiling_2` the `profile` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supercede the `all_lights` default setting. ### Service `light.turn_on`