Scenes Editor

From the UI choose Settings which is located in the sidebar, then click on Automations & Scenes to go to the scene editor. Press the Add Scene button in the lower right corner to get started.

Choose a meaningful name for your scene.

Scene editor

Select all the devicesA device is a model representing a physical or logical unit that contains entities. (or entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service.
[Learn more]
when advanced mode is enabled on your user profile) you want to include in your scene. The state of your devices will be saved, so it can be restored when you are finished creating your scene. Set the state of the devices to how you want them to be in your scene, this can be done by clicking on it and edit the state from the popup, or any other method that changes the state. On the moment you save the scene, all the states of your devices are stored in the scene. When you leave the editor the states of the devices are restored to the state from before you started editing. The menu on the top-right has options to Duplicate scene and Delete scene.

A scene can be called in automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home.
[Learn more]
action and scriptsScripts are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on.
[Learn more]
using a turn on scene serviceA service carries out one specific task, for example: turn on the light in the living room. A service has targets and data and can be called by actions, a dashboard, or via voice command.
[Learn more]

service: scene.turn_on
  entity_id: scene.my_unique_id

Updating your configuration to use the editor

First, check that you have activated the configuration editor.

# Activate the configuration editor

The scene editor reads and writes to the file scenes.yaml in the root of your configuration folder. Currently, both the name of this file and its location are fixed. Make sure that you have set up the scene integration to read from it:

# Configuration.yaml example
scene: !include scenes.yaml

If you still want to use your old scene section, add a label to the old entry:

scene old:
  - name: ...

You can use the scene: and scene old: sections at the same time:

  • scene old: to keep your manual designed scenes
  • scene: to save the scene created by the online editor
scene: !include scenes.yaml
scene old: !include_dir_merge_list scenes

Migrating your scenes to scenes.yaml

If you want to migrate your old scenes to use the editor, you’ll have to copy them to scenes.yaml. Make sure that scenes.yaml remains a list! For each scene that you copy over, you’ll have to add an id. This can be any string as long as it’s unique.

For example:

# Example scenes.yaml entry
- id: my_unique_id # <-- Required for editor to work.
  name: Romantic
    light.tv_back_light: on
      state: on
      xy_color: [0.33, 0.66]
      brightness: 200
Any comments in the YAML file will be lost and templates will be reformatted when you update a scene via the editor.