From 65b578c231f58940735cfc3317ae97101ac0923d Mon Sep 17 00:00:00 2001 From: "M.J. Wydra (Jay)" Date: Tue, 3 Nov 2020 04:59:23 -0600 Subject: [PATCH] Remove opinionated wording (#15520) Remove opinionated wording and replace it with a more neutral explanation. --- source/_integrations/hue.markdown | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown index 72815d94569..787d6ca685c 100644 --- a/source/_integrations/hue.markdown +++ b/source/_integrations/hue.markdown @@ -67,9 +67,7 @@ More information can be found on the [Philips Hue API documentation](https://www ## Using Hue Scenes in Home Assistant -The Hue platform has its own concept of scenes for setting the colors of a group of lights simultaneously. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them—many that you've never used, and almost all very poorly named. - -To avoid user interface overload, we don't expose scenes directly. Instead there is a `hue.hue_activate_scene` service which can be used in an automation or script. +The Hue platform has its own concept of scenes for setting the colors of a group of lights simultaneously. A Hue bridge could potentially have dozens of scenes stored on it, and many scenes across different rooms might share the same name (the default scenes, for example). To avoid user interface overload, we don't expose scenes directly. Instead there is a `hue.hue_activate_scene` service which can be used in an automation or script. This will have all the bulbs transitioned at once, instead of one at a time like when using standard scenes in Home Assistant. For instance: