From b910b565d430ad29bbdfeef630e18594f10ce8e1 Mon Sep 17 00:00:00 2001 From: Elliott Plack Date: Thu, 8 Dec 2022 09:22:14 -0500 Subject: [PATCH] Updated optional status for lights in service While implementing `adaptive_lighting.**apply**` in automations, I've noticed that listing the lights isn't required. For instance, if I have an adaptive lighting entity called `adaptive_lighting.office`, I can condition a motion sensor trigger with the following action successfully: service: adaptive_lighting.apply data: entity_id: switch.adaptive_lighting_office turn_on_lights: true --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6eef09af..38718679 100644 --- a/README.md +++ b/README.md @@ -114,7 +114,7 @@ adaptive_lighting: | Service data attribute | Optional | Description | | ---------------------- | -------- | -------------------------------------------------------------------------------------------- | | `entity_id` | no | The `entity_id` of the switch with the settings to apply. | -| `lights` | no | A light (or list of lights) to apply the settings to. | +| `lights` | yes | A light (or list of lights) to apply the settings to. | | `transition` | yes | The number of seconds for the transition. | | `adapt_brightness` | yes | Whether to change the brightness of the light or not. | | `adapt_color` | yes | Whether to adapt the color on supporting lights. |