SceneManagement Cluster

Cluster ID: 0x0062  |  Endpoint: Typically on Endpoint 1 (application endpoint)

SceneManagement is the scene management Cluster in Matter — it bundles attribute values from multiple Clusters into a single "snapshot" and restores the entire set of states with one command. For example, a "Movie Mode" scene can simultaneously dim the lights, set a warm color temperature, and close the curtains — all in one scene.

Each scene is uniquely identified by GroupID + SceneID and belongs to a Group, which can contain multiple scenes. The core data structure of a scene is ExtensionFieldSets — a set of "Cluster ID + attribute value list" snapshots that define which attributes of which Clusters are set to what values.

Commands

The SceneManagement Cluster has 8 commands covering scene CRUD operations, one-tap recall, and cross-group copying. AddScene and RecallScene are the two most commonly used in daily development. Click a command ID in the table below to jump to its detailed description.

AddScene — Add Scene (0x00)

Adds a new scene to the device's scene table, or updates an existing one. The core scene data is passed via ExtensionFieldSets — it defines which attributes of which Clusters this scene controls. If the specified GroupID + SceneID already exists, it will be overwritten.

AddSceneResponse Fields

↑ Back to Commands

ViewScene — View Scene (0x01)

Reads the full data of a specified scene, including transition time, scene name, and ExtensionFieldSets. Used to display scene details in the app UI or to retrieve the current configuration before editing.

ViewSceneResponse Fields

↑ Back to Commands

RemoveScene — Remove Scene (0x02)

Removes a specified scene from the device's scene table. After removal, the SceneID can be reused.

RemoveSceneResponse Fields

↑ Back to Commands

RemoveAllScenes — Remove All Scenes in Group (0x03)

Removes all scenes in a specified Group at once. Suitable for resetting or clearing all scene configurations in an area.

RemoveAllScenesResponse Fields

↑ Back to Commands

StoreScene — Capture Current State (0x04)

Takes a "snapshot" of the device's current actual state and saves it as a scene. The device automatically reads the current attribute values from its own Clusters and packages them into ExtensionFieldSets stored in the scene table. Unlike AddScene, which requires manually specifying each attribute value, StoreScene is more like a "save current state" shortcut.

StoreSceneResponse Fields

↑ Back to Commands

RecallScene — Recall Scene (0x05)

Recalls a specified scene in one step. The device reads the ExtensionFieldSets saved in the scene and sets each Cluster's attribute values to the target values recorded in the scene. If TransitionTime is specified, the device transitions smoothly within the given duration (e.g., gradual dimming).

↑ Back to Commands

GetSceneMembership — Query Scene List (0x06)

Queries which scenes exist in a specified Group. Returns the list of all stored SceneIDs under that Group and the remaining capacity. Used to display the scene list in the app UI or to determine how many more scenes can be created.

GetSceneMembershipResponse Fields

↑ Back to Commands

CopyScene — Copy Scene (0x40)

Copies scenes between Groups. Can copy a single scene or all scenes from a source Group to a target Group at once. Ideal for sharing the same scene configuration across different rooms.

CopySceneResponse Fields

↑ Back to Commands

Attributes

The SceneManagement Cluster has 3 attributes. Scene data itself is not exposed through attributes but is read via the ViewScene / GetSceneMembership commands. The attributes provide metadata such as scene table capacity and current state information.

LastConfiguredBy(0x0000) Removed in newer versions

Records the Node ID that last modified the scene table. Useful for troubleshooting "who changed the scene configuration" issues. A value of null means the scene table has never been modified, or the device does not support tracking this information.

↑ Back to Attributes

SceneTableSize(0x0001)

The maximum capacity of the device's scene table, i.e., the maximum number of scenes it can store. This is the total capacity shared across all Fabrics. Typical device values range from 8 to 16.

↑ Back to Attributes

FabricSceneInfo(0x0002)

Scene state information independently maintained by each Fabric. This is a list where each element corresponds to one Fabric. Through it, you can determine how many scenes the current Fabric has, which scene is currently active, and how many more can be stored.

↑ Back to Attributes

Core Data Structures

ExtensionFieldSets (Extension Field Sets)

ExtensionFieldSets is the core data of a scene — it records "which attributes of which Clusters this scene sets to what values." The structure is a list where each element contains a Cluster ID and the list of attribute values to set for that Cluster.

For example, a "Movie Mode" scene's ExtensionFieldSets might contain:

• OnOff (0x0006): On/Off = On
• LevelControl (0x0008): Brightness = 25 (approx. 10%)
• ColorControl (0x0300): Color X = 370, Color Y = 300 (warm white)

When the device executes RecallScene, it reads these attribute pairs one by one and invokes the corresponding Cluster's logic to set the attribute values. Each Cluster needs to implement the ScenesManagement callback interface to support scene storage and recall.

Feature Bitmap

The SceneManagement Cluster declares the device's advanced capabilities via FeatureMap (0xFFFC):

Example Data

Attribute Read Example

Return data when reading SceneManagement Cluster attributes:

{
  // --- Scene table info ---
  "0x0001": 16,            // SceneTableSize = 16 (max 16 scenes)

  // --- Fabric scene info ---
  "0x0002": [              // FabricSceneInfo (current Fabric's scene summary)
    {
      "SceneCount": 3,           // Current Fabric has 3 stored scenes
      "CurrentScene": 1,         // Currently active Scene ID
      "CurrentGroup": 0,         // Group ID of the currently active scene
      "SceneValid": true,        // Current scene state is valid
      "RemainingCapacity": 13,   // Can store 13 more scenes
      "FabricIndex": 1           // Fabric index
    }
  ]
}

AddScene Command Example

Create a "Movie Mode" scene containing attribute snapshots from three Clusters: OnOff, LevelControl, and ColorControl:

{
  "invokeRequests": [{
    "commandPath": {
      "endpointId": 1,
      "clusterId": "0x0062",
      "commandId": "0x00"       // AddScene
    },
    "commandFields": {
      "GroupID": 0,              // Group ID (0 = not in any Group)
      "SceneID": 1,              // Scene ID
      "TransitionTime": 10,      // Transition time = 1.0 second (unit: 0.1 second)
      "SceneName": "Movie",      // Scene name (requires SN feature)
      "ExtensionFieldSets": [    // Attribute snapshots per Cluster
        {
          "ClusterID": "0x0006", // OnOff Cluster
          "AttributeValueList": [
            { "AttributeID": "0x0000", "ValueUnsigned8": 1 }
          ]
        },
        {
          "ClusterID": "0x0008", // LevelControl Cluster
          "AttributeValueList": [
            { "AttributeID": "0x0000", "ValueUnsigned8": 25 }
          ]
        },
        {
          "ClusterID": "0x0300", // ColorControl Cluster
          "AttributeValueList": [
            { "AttributeID": "0x0003", "ValueUnsigned16": 370 },
            { "AttributeID": "0x0004", "ValueUnsigned16": 300 }
          ]
        }
      ]
    }
  }]
}

Common Scenarios