62  Matter Device Types and Clusters

In 60 Seconds

Matter Device Types are standardized blueprints defining required and optional clusters (capabilities) for each device category, from simple On/Off Lights to complex EV Chargers. This ensures any Matter controller can automatically discover and interact with any certified device, with multi-endpoint support for multi-function devices and bridge patterns for legacy Zigbee/Z-Wave.

62.1 Matter Device Types and Cluster Library

15 min | Intermediate | P08.C47.U01

Minimum Viable Understanding

Matter Device Types are standardized blueprints that define what clusters (capabilities) a device must and may implement. Each device type – from simple On/Off Lights to complex EV Chargers – specifies required and optional clusters, ensuring any Matter controller can automatically discover and correctly interact with any certified device. Multi-function devices use multiple endpoints, and legacy Zigbee/Z-Wave devices can be exposed through a bridge pattern.

Learning Objectives

By the end of this section, you will be able to:

  • Classify Matter device types by their taxonomy and required cluster composition
  • Select appropriate clusters from the Matter cluster library for common device categories
  • Design device type compositions using required and optional clusters
  • Implement cluster-based feature discovery for multi-endpoint devices
  • Map legacy Zigbee/Z-Wave devices to Matter equivalents using the bridge pattern
  • Evaluate Matter’s device support roadmap for future product planning
How It Works: Matter Device Type System

Matter standardizes smart home devices through a two-level classification system:

  1. Device Types (Top Level) - Each device type (e.g., On/Off Light, Door Lock, Thermostat) is assigned a unique 16-bit ID and defines a specific blueprint for that device category. The Matter specification includes 60+ standardized device types covering lighting, HVAC, security, appliances, and more.

  2. Required and Optional Clusters (Implementation Layer) - Each device type specifies which clusters MUST be implemented (required) and which MAY be implemented (optional). For example:

    • On/Off Light (0x0100): Requires On/Off cluster (0x0006), optionally supports Level Control (0x0008) for dimming
    • Color Temperature Light (0x010C): Requires On/Off + Level Control + Color Control (0x0300) in color temperature mode
    • Extended Color Light (0x010D): Adds full RGB/HSV color support to color temperature requirements

This standardization enables automatic feature discovery: when a controller reads a device’s type ID, it instantly knows which clusters and capabilities are guaranteed to be present. Multi-function devices (like a ceiling fan with integrated light) use multiple endpoints – Endpoint 1 for the fan motor (Fan Control cluster), Endpoint 2 for the light (On/Off, Level Control). Legacy Zigbee/Z-Wave devices can be bridged into Matter by mapping their clusters to Matter equivalents.

62.2 Prerequisites

Before diving into this chapter, you should be familiar with:

Deep Dives:

Comparisons:

62.3 For Beginners: Understanding Device Types

Imagine you’re buying furniture for your home. You don’t just buy “wood” or “metal”—you buy specific things like: - A chair (for sitting) - A table (for eating/working) - A lamp (for lighting)

Each furniture type has expected features: - A chair has legs, a seat, and a back - A lamp has a power switch and light source

Matter Device Types work the same way:

Instead of just seeing a generic “smart device,” controllers know they’re communicating with: - A Dimmable Light (has on/off + brightness control) - A Door Lock (has lock/unlock + optional keypad) - A Thermostat (has temperature reading + heating/cooling control)

This means your smart home app can show the right controls automatically—a dimmer slider for lights, a lock icon for locks, a temperature dial for thermostats.

Matter Device Types are like special uniforms that tell everyone what job you do - just like how a firefighter’s uniform tells you they fight fires!

62.3.1 The Sensor Squad Adventure: Uniform Day at the Smart Home School

It was the first day of Smart Home School, and the Sensor Squad was excited but confused. There were SO many different gadgets running around - light bulbs, door locks, thermostats, sensors - and nobody knew who did what!

“This is chaos!” said Sammy the Temperature Sensor. “That light bulb just tried to unlock a door, and that motion detector is trying to change the room temperature!”

The headmaster, Mr. Matter, gathered everyone together. “Today, we’re assigning Device Types - special uniforms that tell everyone exactly what you can do!”

Sammy got the Temperature Sensor uniform (Device Type 0x0302). “Your uniform has a thermometer badge,” explained Mr. Matter. “Everyone who sees this badge knows you can tell them how hot or cold it is. That’s your Cluster - your special power!”

Lila the Light Sensor received the Occupancy Sensor uniform (Device Type 0x0107). Her badge showed an eye symbol. “Your job is to notice when people are in the room. When you see movement, you report it. That’s your Occupancy Sensing Cluster!”

Max the Motion Detector was special - he got an Extended Color Light uniform (Device Type 0x010D)! “You have THREE badges,” Mr. Matter showed him. “On/Off for turning on and off. Level Control for brightness. AND Color Control for picking any color in the rainbow!”

Bella the Button received a Generic Switch uniform (Device Type 0x000F). Her badge showed a finger pressing a button. “When someone presses you, you tell everyone ‘Hey! I was pressed!’ That’s your Switch Cluster.”

The BEST part was what happened next. A new student walked in - an Apple HomePod! Then a Google Nest! Then an Amazon Echo! In the old days, they would have spoken different languages. But now, the HomePod looked at Sammy’s Temperature Sensor badge and said, “Oh, I know exactly how to ask you for the temperature!” The Google Nest saw Lila’s Occupancy badge and knew exactly what questions to ask her.

“This is the magic of Device Types,” smiled Mr. Matter. “No matter who asks - Apple, Google, Amazon, or Samsung - they all understand what each uniform means. Everyone can work together!”

62.3.2 Key Words for Kids

Word What It Means
Device Type A special “uniform” that tells everyone what job a smart device does
Cluster A badge on the uniform that shows one specific skill, like measuring temperature or controlling brightness
Endpoint Like having multiple uniforms at once - a smart device can have several jobs!
Required Cluster A badge you MUST have for your job - a light MUST have an on/off badge
Optional Cluster An extra badge that’s nice to have - a light might also have a color badge

62.3.3 Try This at Home! 🏠

Create Your Own Matter Device Type Cards!

Design uniform badges for your family members to understand how device types work:

  1. Make ID badges: Cut rectangles from cardboard for each family member.

  2. Assign Device Types:

    • Give Mom a “Thermostat” badge with a temperature dial drawing
    • Give Dad a “Door Lock” badge with a key symbol
    • Give yourself a “Light Switch” badge with an on/off symbol
    • Give a sibling an “Occupancy Sensor” badge with an eye

  3. Add Cluster stickers: Each person adds their special power stickers:

    • Thermostat: “Read Temperature” + “Set Target Temperature” + “Choose Heat or Cool”
    • Door Lock: “Lock” + “Unlock” + “Check if Locked”
    • Light Switch: “On” + “Off” + “Tell Others to Turn On”
    • Occupancy Sensor: “Detect Movement” + “Report Occupancy”

  4. Play Smart Home:

    • Walk around the house. When you enter a room, the “Occupancy Sensor” person shouts “Movement detected!”
    • The “Light Switch” person can then say “Turning on lights!”
    • The “Thermostat” person checks if the room is comfortable.

  5. Try mixing! What happens if the Occupancy Sensor leaves the room? What should happen to the lights?

This game shows how Matter devices use their “uniforms” (Device Types) and “badges” (Clusters) to work together - and why any smart home app can understand any device with the same badge!

62.4 Device Type Architecture

62.4.1 Device Type Definition

A Device Type specifies: - Required Clusters: Must be implemented - Optional Clusters: May be implemented - Cluster Requirements: Which attributes/commands are mandatory - Conditions: Feature-dependent requirements

Dimmable Light device type structure showing Required Clusters (On/Off, Level Control, Identify, Groups, Scenes), Optional Clusters (Color Control, Occupancy Sensing), and Feature Flags (Lighting, Frequency)
Figure 62.1: Matter Dimmable Light Device Type with Required and Optional Clusters
Matter device type support timeline from version 1.0 with core lighting and locks through 1.2 appliances to future cameras and energy management
Figure 62.2: Matter device type support evolution from core lighting and locks in 1.0 to appliances in 1.2 and cameras/energy management in future releases. Device manufacturers should check current spec version for supported types.

62.4.2 Root Node Device Type

Every Matter device has a Root Node device type at Endpoint 0:

Cluster Purpose Required
Basic Information Device identity, vendor, model ✅
Access Control ACL management ✅
General Commissioning Commissioning state ✅
Network Commissioning Thread/Wi-Fi configuration ✅
Administrator Commissioning Commission window control ✅
Operational Credentials Certificate management ✅
Group Key Management Multicast key distribution ✅
General Diagnostics Health monitoring Optional
Software Diagnostics Software metrics Optional
Thread/Wi-Fi Diagnostics Network-specific diagnostics Optional

62.5 Lighting Device Types

62.5.1 Device Type Hierarchy

Lighting device type hierarchy: On/Off Light, Dimmable Light adding Level Control, Color Temperature Light, and Extended Color Light with full HSV/XY control
Figure 62.3: Matter Lighting Device Type Hierarchy from Basic to Full Color Control

62.5.2 On/Off Light (0x0100)

Simplest lighting device—binary on/off control

Cluster Requirement Key Attributes Key Commands
Identify Required IdentifyTime Identify, TriggerEffect
Groups Required NameSupport AddGroup, RemoveGroup
Scenes Required SceneCount AddScene, RecallScene
On/Off Required OnOff Off, On, Toggle

62.5.3 Dimmable Light (0x0101)

Adds brightness control to On/Off Light

Cluster Requirement Key Attributes Key Commands
All On/Off Light clusters Required — —
Level Control Required CurrentLevel, MinLevel, MaxLevel MoveToLevel, Move, Step

Level Control Attribute Details: | Attribute | Type | Range | Description | |———–|——|——-|————-| | CurrentLevel | uint8 | 1-254 | Current brightness (0=off, 254=max) | | MinLevel | uint8 | 1-254 | Minimum configurable level | | MaxLevel | uint8 | 1-254 | Maximum configurable level | | OnLevel | uint8 | 0-255 | Level when turned on (0xFF=previous) | | OnTransitionTime | uint16 | 0-65534 | Fade-on time (tenths of second) |

Matter’s Level Control cluster uses uint8 for brightness, providing 254 discrete levels (0 reserved for off, 255 reserved):

\[\text{Physical Brightness} = \frac{\text{CurrentLevel}}{254} \times 100\%\]

Worked example: CurrentLevel = 127 (midpoint):

\[\frac{127}{254} \times 100\% = 50\%\]

For a dimmable LED driven by PWM at 1 kHz, the duty cycle is:

\[\text{Duty Cycle} = \frac{127}{254} = 0.5 \rightarrow 500 \, \mu\text{s on, } 500 \, \mu\text{s off}\]

OnTransitionTime is in tenths of a second. A 2-second fade-on: \(2 \times 10 = 20\) (uint16 = 20). The driver must interpolate CurrentLevel from 0 to target over 2000 ms, typically with 100 ms steps: \(20\) brightness increments total.

62.5.4 Extended Color Light (0x010D)

Full color control with RGB/HSV/XY color spaces

Color Control cluster modes: Hue/Saturation, CIE XY, Color Temperature in Mireds, and Enhanced Hue/Saturation with 16-bit precision
Figure 62.4: Matter Color Control Cluster Modes: HSV, XY, Temperature, and Enhanced

62.6 HVAC Device Types

62.6.1 Thermostat (0x0301)

Climate control with heating/cooling modes

Cluster Requirement Purpose
Identify Required Device identification
Thermostat Required Temperature control
Thermostat UI Config Optional Display configuration
Fan Control Optional Fan speed control
Relative Humidity Optional Humidity sensing

Thermostat Cluster Key Attributes: | Attribute | Type | Description | |———–|——|————-| | LocalTemperature | int16 | Current temperature × 100 (°C) | | OccupiedCoolingSetpoint | int16 | Cooling target × 100 | | OccupiedHeatingSetpoint | int16 | Heating target × 100 | | SystemMode | enum8 | Off/Auto/Cool/Heat/EmergencyHeat/Precooling/FanOnly | | ThermostatRunningState | bitmap16 | Current running states (heat/cool/fan) | | ControlSequenceOfOperation | enum8 | Cooling Only/Heating Only/Both |

62.6.2 Room Air Conditioner (0x0072)

Dedicated AC unit control

Cluster Requirement Key Feature
Identify Required —
Thermostat Required Temperature control
Fan Control Required Fan speed
Thermostat UI Config Optional Display settings

62.6.3 Fan (0x002B)

Standalone fan device

Cluster Requirement Key Attributes
Identify Required —
Groups Required —
Fan Control Required FanMode, PercentCurrent, SpeedMax

62.7 Security Device Types

62.7.1 Door Lock (0x000A)

Electronic lock with optional keypad/PIN

Door Lock device type with Required Clusters (Door Lock, Identify) and feature-based requirements for PIN, RFID, and fingerprint credentials
Figure 62.5: Matter Door Lock Device Type with Credential Feature Options

Door Lock Cluster Key Elements: | Element | Type | Description | |———|——|————-| | LockState | enum8 | NotFullyLocked, Locked, Unlocked, Unlatched | | LockType | enum8 | DeadBolt, Magnetic, Other, Mortise, etc. | | ActuatorEnabled | bool | Whether lock can be actuated | | LockDoor | command | Lock the door | | UnlockDoor | command | Unlock the door | | SetCredential | command | Add PIN/RFID/Fingerprint |

62.7.2 Door Lock Controller (0x000B)

Device that controls door locks (keypad, app)

Cluster Requirement Role
Identify Required —
Groups Required —
Scenes Required Store lock/unlock scenes
Door Lock (Client) Required Send lock commands

62.7.3 Contact Sensor (0x0015)

Door/window open/close detection

Cluster Requirement Key Attribute
Identify Required —
Boolean State Required StateValue (open/closed)
Binding Optional Automation triggers

62.8 Sensor Device Types

62.8.1 Occupancy Sensor (0x0107)

Motion/presence detection

Cluster Requirement Key Attributes
Identify Required —
Occupancy Sensing Required Occupancy, OccupancySensorType
Binding Optional Automation targets

Sensor Types: | Type | Value | Technology | |——|——-|————| | PIR | 0 | Passive Infrared | | Ultrasonic | 1 | Ultrasonic waves | | PIR+Ultrasonic | 2 | Combination | | Physical Contact | 3 | Pressure plates, etc. |

62.8.2 Temperature Sensor (0x0302)

Environmental temperature measurement

Cluster Requirement Key Attributes
Identify Required —
Temperature Measurement Required MeasuredValue, MinMeasuredValue, MaxMeasuredValue

Temperature Units:

  • All temperatures in °C × 100 (int16)
  • Example: 21.5°C = 2150

62.8.3 Humidity Sensor (0x0307)

Relative humidity measurement

Cluster Requirement Key Attributes
Identify Required —
Relative Humidity Required MeasuredValue (0-10000 = 0-100%)

62.8.4 Light Sensor (0x0106)

Ambient light level measurement

Cluster Requirement Key Attributes
Identify Required —
Illuminance Measurement Required MeasuredValue (10000 × log10(lux) + 1)

62.8.5 Air Quality Sensor (0x002C)

Multi-parameter air quality measurement

Cluster Requirement Measures
Air Quality Required Overall air quality index
Carbon Monoxide Optional CO concentration (ppm)
Carbon Dioxide Optional CO2 concentration (ppm)
PM2.5 Optional Particulate matter (μg/m³)
PM10 Optional Coarse particulate matter
Formaldehyde Optional HCHO concentration
Total VOC Optional Volatile organic compounds

62.9 Closure Device Types

62.9.1 Window Covering (0x0202)

Motorized blinds, shades, curtains

Window Covering device type with Lift Feature for vertical position, Tilt Feature for slat angle, and Position Aware for precise percentage control
Figure 62.6: Matter Window Covering Device Type with Lift, Tilt, and Position Features

62.10 Switch Device Types

62.10.1 On/Off Light Switch (0x0103)

Physical wall switch binding to lights

Cluster Requirement Purpose
Identify Required —
Scenes (Client) Required Scene recall
On/Off (Client) Required Toggle bound lights
Level Control (Client) Optional Dim bound lights
Color Control (Client) Optional Color bound lights
Binding Required Target device configuration

62.10.2 Generic Switch (0x000F)

Multi-function button/switch

Cluster Requirement Key Events
Identify Required —
Switch Required InitialPress, LongPress, ShortRelease, LongRelease, MultiPressOngoing, MultiPressComplete

Switch Positions and Features:

  • Latching Switch: Stays in position (on/off)
  • Momentary Switch: Returns to neutral (button press)
  • Multi-position: Multiple discrete positions

62.11 Appliance Device Types (Matter 1.2+)

62.11.1 Refrigerator (0x0070)

Cluster Requirement Purpose
Refrigerator Alarm Required Door open, temperature
Temperature Control Required Target temperature
Refrigerator and TCC Mode Required Operating modes

62.11.2 Laundry Washer (0x0073)

Cluster Requirement Purpose
Laundry Washer Mode Required Wash cycles
Laundry Washer Controls Required Spin speed, rinse, temperature
Operational State Required Running, paused, complete

62.11.3 Robot Vacuum Cleaner (0x0074)

Cluster Requirement Purpose
RVC Run Mode Required Mapping, cleaning, idle
RVC Clean Mode Required Vacuum, mop, both
RVC Operational State Required Running, docked, error

62.12 Energy Management Device Types (Matter 1.3+)

62.12.1 EV Charger (0x050C)

EV Charger device type with Required Clusters (Energy EVSE, Electrical Measurement) and optional features for pricing, solar integration, and V2H
Figure 62.7: Matter EV Charger Device Type with Energy Management Clusters

62.12.2 Solar Power (0x050D)

Cluster Requirement Key Attributes
Electrical Power Measurement Required ActivePower, Voltage, Current
Electrical Energy Measurement Required CumulativeEnergyExported

62.13 Device Type Composition

62.13.1 Bridge Device Pattern

Bridges expose non-Matter devices as Matter endpoints:

Matter Bridge pattern showing Root endpoint, Bridge endpoint, and bridged endpoints translating between Matter and legacy Zigbee devices
Figure 62.8: Matter Bridge Pattern for Exposing Legacy Zigbee Devices

Bridged Device Considerations:

  • Each legacy device = one Matter endpoint
  • Bridge handles protocol translation
  • Bridged devices have limitations:
    • Delayed responses (protocol translation latency)
    • Feature subset (only common capabilities mapped)
    • Network dependency (legacy network must be operational)

62.13.2 Composed Device Pattern

Single physical device with multiple functions:

Matter composed device pattern: Smart Plug with Root Node, On/Off Plug-in Unit with energy monitoring clusters, and USB Power Source endpoint
Figure 62.9: Matter Composed Device Pattern: Smart Plug with Energy Monitoring showing multiple endpoints and their cluster compositions

62.14 Cluster Library Reference

62.14.1 Common Utility Clusters

Cluster ID Name Purpose
0x001D Descriptor List endpoints/device types
0x001E Binding Configure automation targets
0x001F Access Control ACL management
0x0028 Basic Information Vendor, product, serial
0x0030 General Commissioning Commission state
0x0031 Network Commissioning Thread/Wi-Fi config
0x003E Operational Credentials Certificate management

62.14.2 Application Clusters

Cluster ID Name Use Case
0x0003 Identify Locate device physically
0x0004 Groups Multicast control
0x0005 Scenes Store/recall device states
0x0006 On/Off Binary power control
0x0008 Level Control Dimming/volume
0x0101 Door Lock Lock control
0x0201 Thermostat HVAC control
0x0300 Color Control Lighting color
0x0400 Illuminance Light sensing
0x0402 Temperature Temperature sensing
0x0405 Relative Humidity Humidity sensing
0x0406 Occupancy Presence detection

62.15 Understanding Check

Knowledge Check

Scenario: You’re designing a multi-function smart device that includes: - A main ceiling light (dimmable, color temperature adjustable) - An integrated occupancy sensor - A nightlight (dim warm white only) - A Zigbee bridge for 5 legacy Zigbee bulbs

Questions:

  1. How many endpoints would this device have?
  2. What device type would Endpoint 1 be?
  3. What clusters are required for the occupancy sensor endpoint?
  4. How would the Zigbee bulbs appear in the Matter data model?

1. Total Endpoints: 10

Endpoint 0:   Root Node (mandatory)
Endpoint 1:   Main Light (Color Temperature Light)
Endpoint 2:   Occupancy Sensor
Endpoint 3:   Nightlight (Dimmable Light)
Endpoint 4:   Bridge (Aggregator device type)
Endpoints 5-9: Bridged Zigbee Bulbs (5 endpoints)

2. Endpoint 1 Device Type: Color Temperature Light (0x010C)

  • Includes On/Off, Level Control, Color Control (CT only)
  • Not Extended Color Light because no full RGB

3. Occupancy Sensor Endpoint (Endpoint 2) Required Clusters:

  • Identify Cluster (0x0003)
  • Occupancy Sensing Cluster (0x0406)
  • Optional: Binding Cluster for automation

4. Zigbee Bulbs in Matter Data Model: Each Zigbee bulb appears as a separate endpoint: - Endpoint 5: Bridged Node with Dimmable Light - Bridged Device Basic Information cluster indicates it’s bridged - Commands translated by Endpoint 4 (Bridge) - Reachable attribute indicates Zigbee network status

62.15.1 Knowledge Check: Matter Device Type Composition

62.15.2 Knowledge Check: Matter Bridge Pattern

62.15.3 Knowledge Check: Matter Lighting Hierarchy

62.16 Decision Framework: Choosing the Right Matter Device Type

When designing a Matter device, follow this decision tree to choose the correct device type:

Step 1: What is the primary function?

Primary Function Device Type Example Products
Binary on/off control On/Off Light (0x0100) Simple bulb, plug
Brightness control Dimmable Light (0x0101) Dimmable bulb, LED strip
Color temperature only Color Temperature Light (0x010C) Tunable white bulb
Full RGB color Extended Color Light (0x010D) RGB bulb, color strip
Entry security Door Lock (0x000A) Smart lock, deadbolt
Climate control Thermostat (0x0301) HVAC controller
Motion detection Occupancy Sensor (0x0107) PIR sensor
Access control Generic Switch (0x000F) Smart button, switch

Step 2: Does it have multiple functions?

If YES: Composed device with multiple endpoints - Example: Smart plug with energy monitoring = Endpoint 0 (Root) + Endpoint 1 (On/Off Plug) + Endpoint 2 (Power Measurement) - Each function gets its own endpoint with appropriate device type

If NO: Single endpoint (plus mandatory Root Node at Endpoint 0)

Step 3: What clusters are required vs optional?

Lighting hierarchy (cumulative requirements): - On/Off Light: Identify + Groups + Scenes + On/Off - Dimmable Light: ↑ all above + Level Control - Color Temperature Light: ↑ all above + Color Control (temperature mode only) - Extended Color Light: ↑ all above + Color Control (full HSV/XY)

Security hierarchy:

  • Contact Sensor: Boolean State (open/closed)
  • Door Lock: Door Lock cluster + User management (if PIN feature enabled)
  • Occupancy Sensor: Occupancy Sensing + Binding (for automation triggers)

Step 4: Do you need to bridge legacy devices?

If YES: Aggregator/Bridge pattern - Endpoint 0: Root Node - Endpoint 1: Aggregator device type - Endpoints 2+: One Bridged Node per legacy device - Each bridged endpoint has Bridged Device Basic Information cluster

Step 5: Does it require special features?

Check feature flags that trigger additional cluster requirements: - Door Lock with PIN: Requires User cluster for credential management - Window Covering with Lift + Tilt: Requires both position attributes - Thermostat with Humidity: Requires Relative Humidity cluster

Example Decision Path:

Product: Smart plug with energy monitoring and USB port 1. Primary function: On/off power control → On/Off Plug-in Unit (0x010A) 2. Multiple functions: YES (main outlet + USB + energy) 3. Endpoint structure: - Endpoint 0: Root Node (mandatory) - Endpoint 1: On/Off Plug-in Unit + Electrical Measurement cluster - Endpoint 2: USB Power Source (if separately controllable) 4. Legacy bridge: NO 5. Special features: Energy monitoring → Add Electrical Power Measurement cluster to Endpoint 1

Certification checklist:

  • ✅ All required clusters implemented
  • ✅ Correct cluster feature flags set
  • ✅ Descriptor cluster lists all server clusters
  • ✅ Device type ID matches implementation
  • ✅ Part List on Root Node references all endpoints

Objective: Use chip-tool to inspect Matter device types and discover required/optional clusters on real hardware.

Prerequisites:

  • Matter SDK installed
  • A commissioned Matter device (node ID 1 in examples)

Exercise Steps:

  1. Read Device Type on Endpoint 1:

    chip-tool descriptor read device-type-list 1 1

  2. List All Clusters:

    chip-tool descriptor read server-list 1 1
    • Compare to device type specification’s required clusters
    • Identify which optional clusters are implemented

  3. Check Feature Support:

    chip-tool levelcontrol read feature-map 1 1
    • FeatureMap bitmap shows which features are active
    • Example: Bit 0 = OnOff feature, Bit 1 = Lighting feature

  4. Inspect Multi-Endpoint Device:

    chip-tool descriptor read parts-list 1 0
    • For each endpoint in parts-list, read device-type-list
    • Map endpoint structure (e.g., EP1=Fan, EP2=Light for ceiling fan)

What to Observe:

  • Required clusters are always present (certification requirement)
  • Optional clusters add extra capabilities
  • Multi-function devices use separate endpoints for each function

Challenge: Find a Matter bridge and inspect its endpoints. How many legacy devices are exposed? What device types are they?

62.17 Concept Relationships

Concept Related To Relationship
Device Type Clusters Device Types define which clusters are required/optional
Required Cluster Certification Devices must implement all required clusters to pass certification
Endpoint Device Type Each endpoint has a device type ID; Endpoint 0 is always Root Node
Feature Map Optional Features Bitmap indicating which optional cluster features are implemented
Bridge Legacy Devices Bridges expose Zigbee/Z-Wave devices as Matter endpoints
Descriptor Cluster Discovery Every endpoint has Descriptor cluster listing all other clusters

62.18 See Also

:

62.19 Summary

  1. Device Types define blueprints with required and optional clusters for each device category

  2. Endpoint 0 is always Root Node—every other endpoint hosts application device types

  3. Clusters are reusable—the same On/Off cluster works on lights, plugs, and fans

  4. Features drive requirements—a Door Lock with PIN feature requires User cluster

  5. Bridges expose legacy devices as multiple Matter endpoints on a single bridge node

  6. Composed devices use multiple endpoints for multi-function products

  7. Matter 1.2+ added major categories: Appliances (1.2), energy management (1.3), water management

62.21 What’s Next

Chapter Focus
Matter Implementation SDKs, development workflows, and building Matter products
Matter Device Commissioning Implementing device types in code and commissioning flows
Matter Architecture and Fabric Protocol stack, fabric management, and security model
Matter Testing and Certification Testing device type compliance and CSA certification
Thread Network Architecture Thread as Matter’s primary mesh transport layer