Midea Cloud Control
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill’s behavior matches its Midea cloud-control purpose, but it stores Midea credentials locally and runs generated Python helpers to send device commands.
Use this skill only if you are comfortable storing your Midea account credentials on this computer. Review the generated Python helpers, protect or remove ~/.openclaw/midea-cloud-control/config.json when needed, and use clear device names before issuing on/off commands.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone who can read the local config file may gain access to the Midea account credentials and cached device information.
The generated helper persists the Midea account password and device cache so later commands can log in and control devices. This is expected for the integration, but it is sensitive delegated account access.
path = save_config({ "account": account, "password": password, "cloud_name": cloud_name, "devices": devices })Install only if local credential storage is acceptable; protect the config file, avoid sharing logs or files from that directory, and delete the config when no longer needed.
The skill will create and run local Python scripts on the user’s machine when used.
The skill converts Markdown code blocks into local Python files and executes them. The included code is visible and purpose-aligned, but users should recognize this is local code execution.
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.
Review the generated helper scripts before first use and keep the runtime directory under user control.
A mistaken device name or stale cache could send an on/off command to the wrong Midea device.
The helper sends a direct Midea cloud power-toggle request for the cached device ID. This is scoped to the advertised on/off workflow, but it can change the state of a physical appliance.
await cloud._api_request(f"/v1/appliance/operation/togglePower/{device['id']}", {"power": power == "on"})List devices after connecting, use exact device names, and verify appliance behavior after a command is sent.