> 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/cube-os-es/comprobacion-de-compatibilidad/matter.md).

# Matter

En el estándar Matter, un **Clúster** representa un conjunto de capacidades y comportamientos del dispositivo, como encender/apagar una luz, ajustar el brillo, informar la temperatura o detectar ocupación.\
Cada dispositivo expone uno o más clústeres, que definen qué puede hacer el dispositivo y cómo se comunica con un controlador Matter o un Puente Matter.

Comprender los clústeres compatibles te ayuda a determinar qué tipos de dispositivos se pueden integrar y qué funciones estarán disponibles dentro de **CUBE OS**.

***

## Puente Matter

**Clústeres Matter compatibles:**&#x20;

1. Unidad de enchufe con encendido/apagado
2. Luz regulable
3. Luz de temperatura de color&#x20;
4. Sensor de ocupación
5. Sensor de contacto
6. Sensor de humedad
7. Sensor de temperatura
8. Interruptor genérico
9. Termostato
10. Cortina/cover de ventana
11. Sensor de luz
12. Alarma de humo y CO (cubriendo sensores de humo y monóxido de carbono)
13. Sensor de calidad del aire
14. Aire acondicionado de habitación
15. Ventilador

***

## **Hub Matter**

**Clústeres Matter compatibles:**

1. Interruptores y enchufes (Unidades de enchufe con encendido/apagado)
2. Luces, incluyendo:

* Luz regulable
* Luz con encendido/apagado
* Luz de color extendido

3. Dispositivos tipo puente

* Dispositivos conectados bajo un Puente Matter, incluyendo:
  * Interruptores
  * Enchufes
  * Tipos de luz (Luz regulable, Luz con encendido/apagado, Luz de temperatura, Luz de color extendido)


---

# 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/cube-os-es/comprobacion-de-compatibilidad/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.
