Field	Type	Required	Description
enabled	boolean	+	enable or disable scene
group_id	string	–	group identifier, Scenes could be unite to the group for enabling/disabling
name	string	+	scene name. Maximum name length is 25 characters.
meta	JsonObject	–	Scene metadata information. Intended to save data needed for user interfaces.
parent_id	string	–	room identifier for that it was created. If parent_id is not set then it should have empty value for both hub.scenes.list and hub.scenes.get
then	JsonArray	+	An array of then blocks
else	JsonArray	–	An array of else blocks
thenGroups	JsonObject	–	A dictionary of then action groups
elseGroups	JsonObject	+	A dictionary of else action groups
when	JsonArray	+	Array of the conditions blocks defining when the scene should be executed
exceptions	JsonArray	–	Array of the conditions blocks for exceptions in actions
user_notifications	JsonArray	–	Array of the user IDs for notification broadcasts making. This is array of strings.
house_modes	StringArray	–	Array of house mode IDs. If this array is added then it makes new condition along with when block and this condition is connected with when block by logical AND operator. So if one of conditions arises and one of these house modes is set then actions will be executed.
exec_policy	string	–	It is execution policy of scene. There is policy of block ( see description of then blocks ). The block policy can have next states: check_result – result of execution each block should checked and scene should be failed in case if block is failed; ignore_result – result of execution each block should be ignored and checked only in the end of scene execution. If any action was failed than partially_finished status. If all blocks have this status and all of them are failed than failed status.
icon	string	–	icon of scene

• Note: The scene could previously be created as not valid when loading a non-valid or non-matching event item type and the expression types contained inside, or it could be changed to non-valid values/types in the expression, this led to the fact that the scene data became invalid when subsequently loaded from the database and did not succumb change/delete and, accordingly, were in an unmanaged state in the database, since advanced_scenes/1.33 this behavior has been fixed. When creating, loading, or editing scenes containing expressions in events, the following is checked: the existence of items and expressions, the correctness of item values and expressions, and the matching of item types with expressions. In the case of loading a scene with incorrect events from the database, a scene with empty events and actions is created, which can later be modified or deleted. In case of creation or incorrect scene, an error will be returned.