// Configure device authorization credentials (UUID, AuthKey, PID) and network provisioning for TuyaOpen devices. Use when the user mentions device auth, authorization, UUID, AuthKey, tuya_config.h, provisioning, pairing, or cloud connection. 设备授权、授权码、配网、UUID、AuthKey、云连接。
>-
Automated build-flash-monitor-analyze development loop for TuyaOpen devices. Covers log analysis, error patterns, CLI testing, and iterative debugging. Use when the user mentions dev loop, automated testing, log analysis, debug cycle, iterative development, or CI loop. 开发闭环、自动化测试、日志分析、调试循环、迭代开发。
Set up and activate the TuyaOpen development environment, install system dependencies, and initialize tos.py. Use when the user mentions environment setup, activating the SDK, installing dependencies, export.sh, or when tos.py is not found. 环境搭建、环境初始化、激活开发环境、安装依赖。
Agent-friendly non-blocking serial log capture for TuyaOpen devices. Runs tos.py monitor in the background, writes logs to file, and lets the agent tail or stop it at any time. Use when the agent needs to capture device logs without blocking, run a debug session, or monitor UART output during a build-flash-analyze loop. 后台串口日志、非阻塞监控、设备日志捕获、agent日志分析。
Add new board (BSP) support to TuyaOpen, including board directory structure, Kconfig, drivers, and config files. Use when the user mentions adding a board, new board, BSP, board support, hardware adaptation, or tos.py new board. 添加开发板、板级适配、新增BSP、硬件适配。
Build and compile TuyaOpen projects, select build configurations, edit Kconfig options, clean artifacts, and run Linux ELF binaries. Use when the user mentions compiling, building, tos.py build, config choice, menuconfig, Kconfig, build error, or running a project. 项目编译、构建、编译配置、清理编译、编译错误、menuconfig、Kconfig。
| name | tuyaopen/device-auth |
| description | Configure device authorization credentials (UUID, AuthKey, PID) and network provisioning for TuyaOpen devices. Use when the user mentions device auth, authorization, UUID, AuthKey, tuya_config.h, provisioning, pairing, or cloud connection. 设备授权、授权码、配网、UUID、AuthKey、云连接。 |
| license | Apache-2.0 |
| compatibility | ["TuyaOpen environment activated (export.sh / export.ps1 / export.bat)","Tuya IoT Platform account (platform.tuya.com) for credentials"] |
Docs: https://tuyaopen.ai/docs/quick-start/equipment-authorization
TuyaOpen devices need three credentials to connect to the Tuya cloud:
| Credential | Macro | Purpose |
|---|---|---|
| Product ID (PID) | TUYA_PRODUCT_ID | Identifies the product type on the Tuya IoT platform |
| UUID | TUYA_OPENSDK_UUID | Unique device identifier |
| AuthKey | TUYA_OPENSDK_AUTHKEY | Device authentication key (paired with UUID) |
The SDK resolves credentials in this order (first success wins):
auth command (keys: UUID_TUYAOPEN / AUTHKEY_TUYAOPEN)tuya_iot_license_read() reads from hardware (pre-burned modules)TUYA_OPENSDK_UUID / TUYA_OPENSDK_AUTHKEY in tuya_config.hIf none succeed, the device cannot connect to the cloud.
Each application has a tuya_config.h (in include/ or src/). Edit it with your credentials:
#define TUYA_PRODUCT_ID "xxxxxxxxxxxxxxxx"
#define TUYA_OPENSDK_UUID "uuidxxxxxxxxxxxxxxxx"
#define TUYA_OPENSDK_AUTHKEY "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Optional for AP provisioning with QR code:
#define TUYA_NETCFG_PINCODE "12345678"
File locations (vary by project):
apps/tuya_cloud/switch_demo/src/tuya_config.happs/tuya.ai/your_chat_bot/include/tuya_config.happs/tuya_cloud/weather_get_demo/include/tuya_config.hNote: some README files reference
TUYA_DEVICE_UUID/TUYA_DEVICE_AUTHKEY— these are outdated names. The actual macros used in source code areTUYA_OPENSDK_UUID/TUYA_OPENSDK_AUTHKEY.
TuyaOpen-specific authorization codes come in three ways:
Important: only TuyaOpen-specific authorization codes work. Standard Tuya module authorization codes are not compatible.
For CLI-based serial authorization (port selection, baud rates, commands), provisioning modes (BLE / AP), and the full provisioning flow, see references/PROVISIONING.md.
Before writing auth credentials over UART, identify the correct port:
# Linux / macOS
ls /dev/ttyACM* /dev/ttyUSB* 2>/dev/null
# Windows PowerShell
[System.IO.Ports.SerialPort]::GetPortNames()
0x1a86 PID 0x55d2): the lower enumerated port is typically used for flash/auth; the higher port for monitor/log. This is not guaranteed — swap if the auth command fails.tuyaopen/debug-helper to capture device logs in the background during the auth flow:
$OPEN_SDK_PYTHON .agents/skills/tuyaopen/debug-helper/scripts/monitor_helper.py start -p <monitor-port>
# ... run auth on auth port ...
$OPEN_SDK_PYTHON .agents/skills/tuyaopen/debug-helper/scripts/monitor_helper.py tail -n 100
$OPEN_SDK_PYTHON .agents/skills/tuyaopen/debug-helper/scripts/monitor_helper.py stop
#define TUYA_PRODUCT_ID "your_product_id_here"
#define TUYA_OPENSDK_UUID "your_uuid_here"
#define TUYA_OPENSDK_AUTHKEY "your_authkey_here"
tuya_config.h and remind them not to commit the file with real values.Placeholder patterns to check: values containing your_, xxx, here, empty strings, or strings shorter than expected length (UUID ~20 chars, AuthKey ~32 chars).