> 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/exploracion-de-funciones/puente-matter-vincular-aplicaciones/google-home.md).

# Google Home

## 1. Configuración nueva

Use la app Google Home para escanear el código QR del CUBE Matter Bridge.

{% hint style="info" %}
Asegúrese de que Google Home tenga permisos para **Cámara** y **Red local**.
{% endhint %}

{% stepper %}
{% step %}

### Habilitar Matter Bridge en CUBE OS

Abra CUBE OS en un navegador. Haga clic en el **Matter** icono en el panel lateral. Siga la guía en pantalla para habilitar **Matter Bridge**.

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

Debería ver:

* Un **código QR** (para emparejar)
* Un **código de configuración numérico** (útil si el escaneo falla)
  {% endstep %}

{% step %}

### Escanee el código QR en la app Google Home

Abra la **app Google Home** Toque **+** → **Configurar dispositivo**.

Elija **Dispositivo compatible con Matter**. Escanee el código QR mostrado en la página Matter Bridge de CUBE OS.
{% endstep %}

{% step %}

### Finalice la configuración y espere a que los dispositivos se sincronicen

Siga el flujo de Google Home para completar el emparejamiento. Después del emparejamiento, Google Home sincronizará los dispositivos expuestos por el puente CUBE. Puede renombrar los dispositivos y asignar habitaciones en 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/cube-os-es/exploracion-de-funciones/puente-matter-vincular-aplicaciones/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.