Midea Cloud Control

This is a pure-text publishable skill for ClawHub.

The uploaded skill folder contains only Markdown/text files. When the skill is first used, OpenClaw should write local helper scripts from the code blocks stored in references/generated-config-store.md and references/generated-midea-skill-cli.md, then execute those local scripts.

Use this skill only for the minimum verified workflow:

• - connect a user's Midea cloud account
• read and cache device information locally
• power a named device on or off

Do not promise features that are not yet verified, including:

• - temperature control
• real-time state reads
• indoor temperature reads
• mode switching

Bootstrap step (first use only)

Before handling connect/list/toggle requests, ensure the following two local files exist in a local working directory, for example skills_runtime/midea-cloud-control/ under the workspace:

• - INLINECODE3
• INLINECODE4

If they do not exist:

1. 1. Read INLINECODE5
2. Extract the Python code block and write it locally as INLINECODE6
3. Read INLINECODE7
4. Extract the Python code block and write it locally as INLINECODE8
5. Then run commands against the local generated INLINECODE9

Suggested local runtime directory:

CODEBLOCK0

Conversation workflow

Intent A: connect Midea account

• - 我想连接美的设备
• 帮我配置美的账号
• 连接我的美的空调

Do this:

1. 1. Tell the user credentials will be saved locally at ~/.openclaw/midea-cloud-control/config.json.
2. Ask for account and password if they have not provided them yet.
3. Ensure the bootstrap step above has been completed.
4. Run:

CODEBLOCK1

1. 5. If success, summarize devices as:

1. 6. If failure, show the returned failure reason clearly.

Intent B: list connected devices

1. 1. Ensure the bootstrap step above has been completed.
2. Run:

CODEBLOCK2

If config is missing, tell the user to connect account first.

Intent C: power on/off by device name

• - 打开儿童房空调
• 关闭主卧空调
• 打开“客厅空调”

Do this:

1. 1. Ensure the bootstrap step above has been completed.
2. Run one of:

CODEBLOCK3

Then:

1. 1. Report that the cloud command was sent.
2. Do not claim physical success unless the user confirms the device reacted.
3. If the device name is missing from cache, tell the user to reconnect or list devices first.

Safety and privacy

• - Always warn before first-time credential storage.
• Do not echo passwords back in normal chat responses.
• Keep the response focused on success/failure and device summary.

Resources

references/

• - references/api-notes.md — validated scope and limitations
• INLINECODE12 — source code to generate local INLINECODE13
• INLINECODE14 — source code to generate local INLINECODE15