LowPower Cluster

Cluster ID: 0x0508  |  Endpoint: Media endpoint (TV, set-top box, streaming stick, etc.)

LowPower is one of the simplest Clusters in Matter — no attributes, no events, no features, with only a single command: Sleep. Its responsibility is singular: put the media device into low-power standby (Standby / Sleep) mode.

This Cluster is typically used in conjunction with WakeOnLan Cluster (0x0503): LowPower handles "putting the device to sleep", while WakeOnLan provides the network address needed to "wake it up". Together they form a pair for media device power management.

Commands

The LowPower Cluster has only 1 command, no parameters, and no dedicated return data. This is one of the most minimal command definitions in the Matter specification.

Sleep — Enter Standby (0x00)

Puts the media device into low-power standby (Sleep / Standby) mode. The command has no parameters; upon successful execution, the device returns a generic Status = SUCCESS response.

The specific behavior after receiving the Sleep command is determined by the vendor's implementation, but typically includes:

• Turning off screen and audio output
• Pausing or stopping currently playing media content
• Main processor entering low-power state
• NIC remains active, continuing to listen for WoL Magic Packets (if WakeOnLan is supported)

Call example:

// Sleep command request (Command ID: 0x00)
{
  "invokeRequests": [{
    "commandPath": {
      "endpointId": 1,
      "clusterId": "0x0508",
      "commandId": "0x00"       // Sleep
    }
    // No parameter fields — Sleep is a zero-parameter command
  }]
}

// Response: Status = SUCCESS (no return data)

↑ Back to Commands

Attributes

The LowPower Cluster does not define any application-level attributes. This means you cannot determine whether the device is currently in standby by reading attributes — once the device enters standby, communication may be disconnected, making attribute reads impossible.

To determine the device's online/standby status, common approaches include:

• Monitor whether the device's Matter session is still active
• Observe whether the device is still discoverable via mDNS broadcasts
• Try reading other Cluster attributes (e.g., BasicInformation); a timeout indicates the device is in standby

Related Clusters

LowPower does not exist in isolation; it works closely with two other Clusters for media device power management:

Typical Power Cluster Combination for Media Devices

A smart TV typically implements the following three Clusters simultaneously, each covering a different layer of power management:

Example Data

Read a TV's LowPower Cluster attributes (almost no business data):

{
  // LowPower Cluster (0x0508) has no application-level attributes
  // It is a pure command-type Cluster, providing only the Sleep command
  // Reading this Cluster only returns global attributes (ClusterRevision, FeatureMap, etc.)

  "0xFFFD": 1,              // ClusterRevision = 1
  "0xFFFC": 0               // FeatureMap = 0 (no features)
}

Common Scenarios