> 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-pt-br/exploracao-de-recursos/ponte-matter-vincular-apps/google-home.md).

# Google Home

## 1. Configuração nova

Use o app Google Home para escanear o código QR do CUBE Matter Bridge.

{% hint style="info" %}
Certifique-se de que o Google Home tem permissões para **Câmera** e **Rede Local**.
{% endhint %}

{% stepper %}
{% step %}

### Ative o Matter Bridge no CUBE OS

Abra o CUBE OS em um navegador. Clique no **Matter** ícone no painel lateral. Siga o guia na tela para ativar **Matter Bridge**.

<figure><img src="https://1475877759-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>

Você deverá ver:

* Um **código QR** (para emparelhamento)
* Um **código de configuração numérico** (útil se a leitura falhar)
  {% endstep %}

{% step %}

### Escaneie o código QR no app Google Home

Abra o **app Google Home** Toque em **+** → **Configurar dispositivo**.

Escolha **Dispositivo com suporte a Matter**. Escaneie o código QR mostrado na página do Matter Bridge do CUBE OS.
{% endstep %}

{% step %}

### Finalize a configuração e aguarde a sincronização dos dispositivos

Siga o fluxo do Google Home para concluir o emparelhamento. Após o emparelhamento, o Google Home sincronizará os dispositivos expostos pela ponte CUBE. Você pode renomear dispositivos e atribuir cômodos no 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-pt-br/exploracao-de-recursos/ponte-matter-vincular-apps/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.