> 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-zh/gong-neng-tan-suo/matter-qiao-jie-lian-jie-ying-yong/smartthings.md).

# SmartThings

## 1. 全新设置

使用 SmartThings 应用扫描来自 CUBE Matter Bridge 的二维码。

{% hint style="info" %}
确保 SmartThings 已授予以下权限： **相机** 和 **本地网络**.
{% endhint %}

{% stepper %}
{% step %}

### 在 CUBE OS 中启用 Matter Bridge

在浏览器中打开 CUBE OS。

点击 **Matter** 侧边面板中的图标。

按照屏幕上的指南启用 **Matter Bridge**.

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

您应看到：

* 一个 **二维码** （用于配对）
* 一个 **数字设置代码** （如果扫描失败则有用）
  {% endstep %}

{% step %}

### 在 SmartThings 应用中扫描二维码

打开 **SmartThings** 应用。点按 **+** 以添加设备。选择 **合作伙伴设备** 选项，选择 **Matter** 然后扫描。在 CUBE OS Matter Bridge 页面上扫描显示的二维码。
{% endstep %}

{% step %}

### 完成设置并等待设备同步

按照 SmartThings 的流程完成配对。配对后，SmartThings 会同步 CUBE 网桥公开的设备。您可以在 SmartThings 中重命名设备并分配房间。
{% endstep %}
{% endstepper %}

{% embed url="<https://drive.google.com/file/d/1glVtVBvCVsLP-5apDcyfDqkENfrXHHeB/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-zh/gong-neng-tan-suo/matter-qiao-jie-lian-jie-ying-yong/smartthings.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.