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-16 05:46:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add missing info for scene integration (#28262)

Browse Source 
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
This commit is contained in:
Jan Bouwhuis 2023-07-22 17:55:23 +02:00 committed by GitHub
parent 051e9bee15
commit 17ce11168a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
source/_integrations/scene.markdown
View File

@ -1,5 +1,5 @@
---
title: Scenes
title: Scene
description: Instructions on how to setup scenes within Home Assistant.
ha_category:
- Organization
@ -11,6 +11,24 @@ ha_domain: scene
ha_integration_type: entity
---
A scene entity is an entity that can restore the state of a group of entities.
Scenes can be user-defined or can be provided through an integration.
## The state of a scene
The scene entity is stateless, as in, it cannot have a state like the `on` or
`off` state that, for example, a normal switch entity has.
Every scene entity does keep track of the timestamp of when the last time
the scene entity was called via the Home Assistant UI or called via
a service call.
## Scenes created by integrations
Some integrations like [Philips Hue](/integrations/hue), [MQTT](/integrations/mqtt), and [KNX](/integrations/knx) provide scenes. You can activate them from the Home Assistant UI or via as service calls. In this case, the integration provides the preferred states to restore.
## Creating a scene
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.
Scenes can be created and managed via the user interface using the [Scene Editor](/docs/scene/editor/). They can also be manually configured via `configuration.yaml`. Note that the entity data is not service call parameters, it's a representation of the wanted state: