jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update hue.markdown (#4231)

Browse Source 
- changed service name to align with breaking changes in .60
- removed link (no longer applies)
This commit is contained in:
NeLLyMerC 2017-12-18 02:50:50 -05:00 committed by Fabian Affolter
parent 2037605f6c
commit 764362e467
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_components/hue.markdown
View File

@ -106,7 +106,7 @@ More information can be found on the [Philips Hue API documentation](https://www
The Hue platform has it's own concept of scenes for setting the colors of a group of lights at once. 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, almost all very poorly named.
To avoid user interface overload we don't expose scenes directly. Instead there is a [light.hue_activate_scene](/components/light/#service-lighthue_activate_scene) service which can be used by `automation` or `script` components.
To avoid user interface overload we don't expose scenes directly. Instead there is a hue.hue_activate_scene service which can be used by `automation` or `script` components.
This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant.
For instance:
@ -115,7 +115,7 @@ For instance:
script:
porch_on:
sequence:
- service: light.hue_activate_scene
- service: hue.hue_activate_scene
data:
group_name: "Porch"
scene_name: "Porch Orange"