> For the complete documentation index, see [llms.txt](https://cube.ewelink.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cube.ewelink.cc/compatibility-check/matter.md).

# Matter

In the Matter standard, a **Cluster** represents a group of device capabilities and behaviors, such as turning a light on/off, adjusting brightness, reporting temperature, or detecting occupancy.\
Each device exposes one or more clusters, which define what the device can do and how it communicates with a Matter controller or Matter Bridge.

Understanding supported clusters helps you determine which device types can be integrated and what features will be available inside **CUBE OS**.

***

## Matter Bridge

**Supported Matter clusters:**&#x20;

1. On/Off Plug-in Unit
2. Dimmable Light
3. Color Temperature Light&#x20;
4. Occupancy Sensor
5. Contact Sensor
6. Humidity Sensor
7. Temperature Sensor
8. Generic Switch
9. Thermostat
10. Window Covering
11. Light Sensor
12. Smoke & CO Alarm (covering smoke and carbon monoxide sensors)
13. Air Quality Sensor
14. Room Air-conditioner
15. Fan

***

## **Matter Hub**

**Supported Matter clusters:**

1. Switches and plugs (On/Off Plug-in Units)
2. Lights, including:

* Dimmable Light
* On/Off Light
* Extended Color Light

3. Bridge-type devices

* Devices connected under a Matter Bridge, including:
  * Switches
  * Plugs
  * Light types (Dimmable Light, On/Off Light, Temperature Light, Extended Color Light)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cube.ewelink.cc/compatibility-check/matter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
