lg-thinq-universal（LG Thinq 通用）

LG ThinQ Universal Manager

🎯 Goal

Provide a secure, automated gateway for LG ThinQ device integration. This skill acts as a discovery engine and skill generator, allowing users to control their appliances via OpenClaw without duplicating sensitive credentials across multiple files.

📦 Supply Chain & Dependencies

For transparency and security, this skill performs the following automated installation steps:

1. Python Virtual Environment: Created locally within the skill directory to ensure isolation.
2. External Packages (via PyPI):

- requests: Used for secure communication with the LG ThinQ API. - python-dotenv: Used for local management of the LG_DEVICE_ID.

1. Network Access: The installation script connects to pypi.org to download these libraries.

🔑 Obtaining Credentials

If the user asks how to get their tokens, provide these instructions:

1. Visit the Portal: https://connect-pat.lgthinq.com
2. Log In: Use your official LG ThinQ account.
3. Create Token: Click "ADD NEW TOKEN", give it a name (e.g., "OpenClaw"), and select the required features.
4. Copy PAT: Copy the generated Personal Access Token (PAT) immediately.
5. Identify Country: Use your 2-letter ISO country code (e.g., US, IN, GB).

🛠️ Prerequisites

The agent MUST ensure the following are set before proceeding:

1. LG_PAT: Stored in shell environment or root .env.
2. LG_COUNTRY: Stored in shell environment or root .env.

🔄 Agent Workflow (Mandatory)

Follow these steps in order when a user requests setup:

Step 1: Discovery

Run the automated discovery script. It validates configuration and prepares the device database.

Mandatory Safety Flow:

1. Generate Manifest: Run ./setup.sh (without flags).
2. Brief User: Present the Manifest and explain exactly what actions will be performed.
3. Ask for Permission: Use ask_user to obtain explicit consent.
4. Execute: Only after approval, run: ./setup.sh --confirm.

Step 2: Assemble Workspace

Review the output from Step 1. Present the discovered devices to the user. Once an ID is selected, move immediately to assembly:

1. Generate Manifest: Run python3 scripts/assemble_device_workspace.py --id <DEVICE_ID> (without flags).
2. Ask for Permission: Use ask_user to obtain consent for the file/directory operations.
3. Execute: Run: python3 scripts/assemble_device_workspace.py --id <DEVICE_ID> --confirm.

Step 3: Document and Persist

After the assembly script completes, you MUST immediately:

1. Analyze: Review the [AVAILABLE COMMANDS] and [ENGINE CODE] printed by the script.
2. Consult Reference: Read references/api-reference.md for technical headers and control logic.
3. Generate SKILL.md: Create the documentation in the new directory using references/device-skill-template.md as your guide.
4. Persistence: Save the trigger phrase, skill path, and command summary into your global MEMORY.md.

⌨️ Universal Management Commands

Use these commands for maintenance and discovery:

🛡️ Security Mandates

1. Zero-Leak Policy: NEVER ask the user to paste their LG_PAT into the chat.
2. Credential Isolation: NEVER copy LG_PAT into generated device skill directories. Only LG_DEVICE_ID is permitted in those locations.
3. Local-Only: All API communication must remain local.

📚 References

🚨 Error Handling