菜单
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、云连接。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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。
Create new TuyaOpen projects and platforms, manage build configurations, update platform dependencies, and use tos.py subcommands. Use when the user mentions creating a project, tos.py new, saving or choosing a config, tos.py update, or general tos.py usage. 创建项目、新建工程、配置管理、保存配置、选择配置、更新依赖。
Send commands to the TuyaOpen device serial CLI (tal_cli) over UART and capture responses. Use when the user wants to run CLI commands on a connected T5AI, ESP32, T2, T3, or LN882H board — such as sys_reset, kv_dump, fs_ls, or custom registered commands — without opening a foreground monitor. Auto-discovers the USB serial port and platform baud rate. 设备CLI命令、串口命令、tal_cli、kv_dump、sys_reset、串口调试。
Decode a TuyaOpen firmware crash dump (PC, LR, stack pointers) to source file:line by invoking the right per-platform `addr2line` against the debug ELF. Use when the user pastes a panic log / hard-fault dump containing raw hex code addresses (e.g. "PC: 0x021d8e96"). Covers T5AI (BK7258, ARM Cortex-M), ESP32/S3 (Xtensa), T2, T3, LN882H — each ships its own toolchain inside the TuyaOpen tree. 固件崩溃解码、panic、hard fault、PC/LR地址解析、addr2line。
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日志分析。
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. 开发闭环、自动化测试、日志分析、调试循环、迭代开发。
| 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).