> 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/english-it/verifica-di-compatibilita/zigbee.md).

# Zigbee

CUBE OS funziona come un **gateway Zigbee locale**, permettendoti di connettere, gestire e collegare un'ampia gamma di sottodispositivi Zigbee, inclusi interruttori, sensori, luci e monitor ambientali.

Per ottenere prestazioni stabili della rete Zigbee, CUBE OS si basa su **dongle Zigbee compatibili** che fungono da coordinatori radio. Una volta collegato un dongle supportato, CUBE OS può associare e gestire dispositivi Zigbee multi-marca attraverso gli standardizzati Zigbee **cluster**, che definiscono le capacità e le funzioni di ogni tipo di dispositivo.

Le tabelle sottostanti elencano i dongle Zigbee supportati e i cluster Zigbee attualmente compatibili con CUBE OS.

***

## Dongle Zigbee supportati

* SONOFF ZBDongle-MAX
* SONOFF ZBDongle-PMG24
* SONOFF ZBDongle-LMG21
* SONOFF ZBDongle-E
* SONOFF ZBDongle-P
* [Altri adattatori supportati ](https://darkxst.github.io/silabs-firmware-builder/)contribuiti dallo sviluppatore **@darkxst**

***

## Cluster Zigbee supportati

Per l'elenco completo dei cluster e i dettagli di compatibilità, fai clic qui:\
[**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/english-it/verifica-di-compatibilita/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.