2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill mijia-home- _meta.json288 B
- SKILL.md3.8 KB
Overview
This skill controls Xiaomi / Mi Home smart devices via the MCP Server xiaomi-home toolset. It handles device discovery, property queries, property changes, and action invocations for lights, purifiers, heaters, AC, fans, robot vacuums, curtains, and more. It triggers whenever the user expresses a home automation intent, even without explicitly naming Xiaomi or Mi Home.
How this skill works
The skill extracts device keywords from user commands and searches devices with xiaomi_find_device or lists all devices with xiaomi_list_devices to obtain the device did. It inspects the model's supported siid/piid by reading properties with xiaomi_get_properties and then issues changes with xiaomi_set_property or xiaomi_call_action. For status queries it reads sensor properties (PM2.5, temperature, humidity, etc.) and reports human-friendly results; on failure it reports reasons and troubleshooting tips.
When to use it
- Turning devices on or off (lights, heaters, plugs, fans, purifiers).
- Adjusting device attributes (brightness, color temperature, wind level, target temperature).
- Invoking device actions (start/stop vacuum, open/close curtains).
- Querying device status (air quality, room temperature, device online state).
- Triggering scene-like commands (sleep mode, leave-home sequence).
Best practices
- Always confirm the target device when names are ambiguous; use xiaomi_list_devices if needed.
- Check device is_online before attempting control; offline devices cannot be operated.
- When a control fails, probe by reading siid=2 piids 1–10 to discover supported properties.
- Use boolean true/false for on/off properties and do not assume numeric 0/1 mapping.
- Report concise, actionable feedback and include sensor readings when relevant (e.g., PM2.5).
Example use cases
- User: "Turn off the living room light" → find device by name, set siid=2 piid=1 to false, confirm result.
- User: "Air quality is bad" → query purifier PM2.5 and switch purifier to sleep or auto mode based on reading.
- User: "I'm going to bed" → run a scene: turn off lights, set purifier to sleep, lower heater target temp.
- User: "Start vacuum" → call vacuum start action (aiid) after verifying device model and online status.
- User: "How many degrees is it inside?" → read temperature property and report current value and device name.
FAQ
Probe supported properties with xiaomi_get_properties (try siid=2 piid 1–10) to discover the correct IDs and then retry the control call.
Why did a command fail even though the device exists?
Common causes: device is offline, not on the same LAN, incorrect did, or unsupported property for that model. The skill will report the likely cause and suggest checking online state or listing devices.
How are scene commands handled?
Scene commands are decomposed into multiple device operations executed sequentially; the skill reports each device outcome and an overall summary.