> 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/esplorazione-delle-funzionalita/bridge-matter-collega-app/google-home.md).

# Google Home

## 1. Nuova configurazione

Usa l'app Google Home per scansionare il codice QR del CUBE Matter Bridge.

{% hint style="info" %}
Assicurati che Google Home abbia i permessi per **Fotocamera** e **Rete locale**.
{% endhint %}

{% stepper %}
{% step %}

### Abilita Matter Bridge in CUBE OS

Apri CUBE OS in un browser. Clicca sull' **icona Matter** nel pannello laterale. Segui la guida a schermo per abilitare **Matter Bridge**.

<figure><img src="https://2847557189-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnF8kmk9yw3yiy2mRerq%2Fuploads%2F9lN5GFqDwLTmKVR83iSR%2FScreenshot%202024-12-17%20at%2016.37.55.png?alt=media&amp;token=aa80f174-43be-4230-8a73-2d9f1005ffa6" alt=""><figcaption></figcaption></figure>

Dovresti vedere:

* Un **codice QR** (per l'associazione)
* Un **codice numerico di configurazione** (utile se la scansione fallisce)
  {% endstep %}

{% step %}

### Scansiona il codice QR nell'app Google Home

Apri l' **app Google Home** Tocca **+** → **Configura dispositivo**.

Scegli **Dispositivo compatibile con Matter**. Scansiona il codice QR mostrato nella pagina Matter Bridge di CUBE OS.
{% endstep %}

{% step %}

### Completa la configurazione e attendi la sincronizzazione dei dispositivi

Segui il flusso di Google Home per completare l'associazione. Dopo l'associazione, Google Home sincronizzerà i dispositivi esposti dal bridge CUBE. Puoi rinominare i dispositivi e assegnare le stanze in Google Home.
{% endstep %}
{% endstepper %}

{% embed url="<https://drive.google.com/file/d/1yooV0Yy3vsMT8Ni6fAcrBAgDSEUUsaLV/view?usp=drive_link>" %}


---

# 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/esplorazione-delle-funzionalita/bridge-matter-collega-app/google-home.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.