> 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-fr/verification-de-compatibilite/zigbee.md).

# Zigbee

CUBE OS agit comme un **passerelle Zigbee locale**, vous permettant de connecter, gérer et relier un large éventail de sous-appareils Zigbee, y compris des interrupteurs, des capteurs, des luminaires et des moniteurs environnementaux.

Pour obtenir des performances stables du réseau Zigbee, CUBE OS s'appuie sur **dongles Zigbee compatibles** qui servent de coordinateurs radio. Une fois qu'un dongle pris en charge est connecté, CUBE OS peut appairer et gérer des appareils Zigbee multi-marques via des **clusters**, qui définissent les capacités et les fonctions de chaque type d'appareil.

Les tableaux ci-dessous répertorient les dongles Zigbee pris en charge et les clusters Zigbee actuellement compatibles avec CUBE OS.

***

## Dongles Zigbee pris en charge

* SONOFF ZBDongle-MAX
* SONOFF ZBDongle-PMG24
* SONOFF ZBDongle-LMG21
* SONOFF ZBDongle-E
* SONOFF ZBDongle-P
* [Autres adaptateurs pris en charge ](https://darkxst.github.io/silabs-firmware-builder/)contribués par le développeur **@darkxst**

***

## Clusters Zigbee pris en charge

Pour la liste complète des clusters et les détails de compatibilité, veuillez cliquer ici :\
[**https://cube-web.ewelink.cc**](https://cube-web.ewelink.cc)


---

# 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-fr/verification-de-compatibilite/zigbee.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.
