AdministratorCommissioning Cluster

Cluster ID: 0x003C  |  Endpoint: Fixed on Endpoint 0 (Root Endpoint)

AdministratorCommissioning controls the opening and closing of the device's Commissioning Window. When a device has already joined a Fabric (been commissioned), and you want new administrators to also commission this device, you need to open a commissioning window through this Cluster. It does not handle the commissioning flow itself (that is GeneralCommissioning's job), but rather controls the "whether the device accepts new commissioning requests" switch.

Feature Map

Commands

The AdministratorCommissioning Cluster has 3 commands for opening an enhanced commissioning window, opening a basic commissioning window, and closing a commissioning window. None of these commands have dedicated response structures; they return results through the standard Status response. Click a command ID in the table below to jump to its detailed description.

OpenCommissioningWindow — Enhanced Commissioning Window (0x00)

Opens an Enhanced Commissioning Window. The caller must provide a brand-new PAKE verifier, and the new Commissioner will use this verifier instead of the device's factory passcode to establish a PASE secure channel. This is the most secure window-opening method — each window uses a one-time password, so even if intercepted, it cannot be used for the next commissioning.

↑ Back to Commands

OpenBasicCommissioningWindow — Basic Commissioning Window (0x01)

Opens a Basic Commissioning Window. Unlike the enhanced method, basic commissioning uses the device's factory passcode (the pairing code printed on the device label) to establish a PASE secure channel. Simpler to operate, but less secure.

↑ Back to Commands

RevokeCommissioning — Close Commissioning Window(0x02)

Closes the currently open commissioning window. This command has no parameters. After a successful call, the device immediately stops accepting new commissioning requests, WindowStatus returns to WindowNotOpen (0), and AdminFabricIndex and AdminVendorId reset to null.

↑ Back to Commands

Attributes

The AdministratorCommissioning Cluster has 3 attributes describing the current commissioning window state and operator information.

Window Status (0x0000)

↑ Back to Attributes

Administrator Info (0x0001, 0x0002)

Records who opened the current commissioning window. Both attributes are null when the window is closed or not opened.

↑ Back to Attributes

Enum Definitions

CommissioningWindowStatusEnum

Indicates the device's current commissioning window status, used for the WindowStatus attribute.

Cluster Status Codes (StatusCode)

AdministratorCommissioning commands return results through the standard Status response. In addition to standard status codes, the following Cluster-specific status codes are defined:

Example Data

Attribute Data Example (Window Not Open)

Device in normal state with no active commissioning window:

{
  // --- Commissioning Window Status ---
  "0x0000": 0,                // WindowStatus = WindowNotOpen (no commissioning window open)

  // --- Administrator Info ---
  "0x0001": null,             // AdminFabricIndex = null (no administrator opened window)
  "0x0002": null              // AdminVendorId = null (no administrator opened window)
}

Attribute Data Example (Window Open)

An administrator has opened a commissioning window using the enhanced method:

{
  // --- Commissioning Window Status ---
  "0x0000": 1,                // WindowStatus = EnhancedWindowOpen (enhanced commissioning window open)

  // --- Administrator Info ---
  "0x0001": 1,                // AdminFabricIndex = 1 (administrator from Fabric index 1 opened the window)
  "0x0002": 4996              // AdminVendorId = 0x1384（Vendor ID of the administrator who opened the window）
}

OpenCommissioningWindow Interaction Example

Opening a commissioning window using the enhanced method:

// Commissioner → Device: Open enhanced commissioning window
{
  "invokeRequests": [{
    "commandPath": {
      "endpointId": 0,
      "clusterId": "0x003C",
      "commandId": "0x00"              // OpenCommissioningWindow
    },
    "commandFields": {
      "commissioningTimeout": 180,     // Auto-close after 180 seconds
      "PAKEPasscodeVerifier": "base64...",  // New PAKE verifier
      "discriminator": 3840,           // 12-bit device discriminator
      "iterations": 1000,             // PBKDF2 iteration count
      "salt": "base64..."             // PBKDF2 salt
    }
  }]
}

// Device → Commissioner: Successfully opened (Status = SUCCESS)
// This command has no dedicated response structure; results are returned via standard Status

OpenBasicCommissioningWindow Interaction Example

Opening a commissioning window using the basic method (requires BC Feature):

// Commissioner → Device: Open basic commissioning window
{
  "invokeRequests": [{
    "commandPath": {
      "endpointId": 0,
      "clusterId": "0x003C",
      "commandId": "0x01"              // OpenBasicCommissioningWindow
    },
    "commandFields": {
      "commissioningTimeout": 180      // Auto-close after 180 seconds
    }
  }]
}

// Device → Commissioner: Successfully opened (Status = SUCCESS)

RevokeCommissioning Interaction Example

Close the currently open commissioning window：

// Commissioner → Device: Close commissioning window
{
  "invokeRequests": [{
    "commandPath": {
      "endpointId": 0,
      "clusterId": "0x003C",
      "commandId": "0x02"              // RevokeCommissioning
    },
    "commandFields": {}                // No parameters
  }]
}

// Device → Commissioner: Successfully closed (Status = SUCCESS)

Common Scenarios