Franck Nijhof c464056402
Making our website faster, cleaner and prettier (#9853)
* 🔥 Removes octopress.js

* 🔥 Removes use of root_url var

* 🔥 Removes Octopress generator reference from feed

* 🔥 Removes delicious support

* 🔥 Removes support for Pinboard

* 🔥 Removes support for Disqus

* 🔥 Removes support for Google Plus

* ↩️ Migrate custom after_footer to default template

* ↩️ Migrate custom footer to default template

* ↩️ Migrate custom header to default template

* 🔥 Removes unused template files

* 🚀 Places time to read directly in post template

* 🚀 Removes unneeded capture from archive_post.html template

* 🔥 🚀 Removes unused, but heaving sorting call in component page

* 🚀 Merged javascripts into a single file

* 🔥 Removes more uses of root_url

* 🚀 Removal of unneeded captures from head

* 🔥 🚀 Removal of expensive liquid HTML compressor

* 🔥 Removes unneeded templates

* 🚀 Replaces kramdown with GitHub's CommonMark 🚀

* 💄 Adds Prism code syntax highlighting

*  Adds support for redirect in Netlify

* ↩️ 🔥 Let Netlify handle all developer doc redirects

* ✏️ Fixes typo in redirects file: Netify -> Netlify

* 🔥 Removes unused .themes folder

* 🔥 Removes unused aside.html template

* 🔥 Removes Disqus config leftover

* 🔥 Removes rouge highlighter config

* 🔥 Removes Octopress 🎉

* 💄 Adjust code block font size and adds soft wraps

* 💄 Adds styling for inline code blocks

* 💄 Improve styling of note/warning/info boxes + div support

* 🔨 Rewrites all note/warning/info boxes
2019-07-15 22:17:54 +02:00

2.1 KiB

title, description, logo, ha_category, ha_qa_scale, ha_release
title description logo ha_category ha_qa_scale ha_release
Scenes Instructions on how to setup scenes within Home Assistant. home-assistant.png
Organization
internal 0.15

You can create scenes that capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red.

# Example configuration.yaml entry
scene:
  - name: Romantic
    entities:
      light.tv_back_light: true
      light.ceiling:
        state: true
        xy_color: [0.33, 0.66]
        brightness: 200
  - name: Movies
    entities:
      light.tv_back_light:
        state: true
        brightness: 100
      light.ceiling: false
      media_player.sony_bravia_tv:
        source: HDMI 1

{% configuration %} name: description: Friendly name of scene. required: true type: string entities: description: Entities to control. required: true type: list {% endconfiguration %}

As you can see, there are two ways to define the states of each entity_id:

  • Define the state directly with the entity.
  • Define a complex state with its attributes.

The mapping from states to services is done with the state helper. So, please have a look there for available states for your scenes.

Scenes can be activated using the service scene.turn_on (there is no 'scene.turn_off' service).

# Example automation
...
automation:
  trigger:
    platform: state
    entity_id: device_tracker.sweetheart
    from: 'not_home'
    to: 'home'
  action:
    service: scene.turn_on
    entity_id: scene.romantic
Please note that the scene integration for the most part only supports one service call per entity to achieve the state. Due to this limitation, you cannot set states belonging to different services. A workaround for this limitation is to write a script, which you then turn on in your scene. A few integrations have direct support for multiple service calls per state, Currently this is the media_player and climate components.