Aqara Open API Local for Openclaw

A sophisticated relationship-first router that manages Aqara Open Platform HTTP API requests across devices, spaces, and automations.

aqara
v1.0.3
Apr 17, 2026
1
849
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install aqara-open-api-local

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install aqara-open-api-local using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Aqara Open API Local?

The Aqara Open API Local skill is the primary entry point for orchestrating smart home environments via the Aqara Open Platform. It functions as an intelligent router that classifies user requests into three distinct domains: devices, spaces, and automations. By implementing a strict handoff contract and shared CLI execution patterns, this skill allows AI agents within the Openclaw Skills ecosystem to maintain high context awareness and reliable execution.

Designed with a relationship-first architecture, it ensures that spaces act as organizational containers while devices remain the core units of control. This skill provides a standardized runtime environment that leverages the aqara CLI to handle complex request envelopes, authentication, and state management without the need for manual API calls.

Aqara Open API Local Use Cases

  • Listing and controlling smart device states across specific rooms or entire home setups.
  • Managing space organizational structures, including creating rooms and moving devices between them.
  • Developing and deploying automation routines with sophisticated validation strategies.
  • Performing room-scoped device queries by resolving space identities and filtering local caches.

How Aqara Open API Local Works

  1. The router analyzes the incoming request to determine if the target entity is a device, a space, or an automation logic.
  2. It resolves credentials and endpoints using environment variables or the aqara CLI configuration file.
  3. The system builds a structured handoff contract that captures the final intent, resolved space/device IDs, and operation context.
  4. It selects the appropriate execution path, choosing between cache-first generation or strict capability validation.
  5. The command is dispatched through the aqara CLI, ensuring the request envelope matches the v1 API specification.
  6. Response data is processed, and the local device cache is updated if necessary to maintain state synchronization.

Aqara Open API Local Setup

To utilize this skill within Openclaw Skills, ensure Node.js is installed and the aqara CLI is available in your environment. Configure your credentials using one of the following methods:

Set environment variables directly:

export AQARA_ENDPOINT_URL="your_api_endpoint"
export AQARA_OPEN_API_TOKEN="your_access_token"

Or use the CLI configuration tool:

aqara config set-endpoint <url>
aqara config set-token <token>

Aqara Open API Local Data Schema & Taxonomy

The skill utilizes a structured data management approach to ensure reliability and speed across Openclaw Skills workflows:

Component Path / Type Purpose
Device Cache data/devices.json Stores the local snapshot of all devices and their room memberships.
Config File ~/.aqa/config.json Persists endpoint URLs and authentication tokens.
Request Envelope JSON Standardized structure containing type, version, msgId, and data.
Handoff Contract Internal JSON A semantic bridge between the router and child skills for device/space context.

Aqara Open API Local Advanced Features

  • Relationship-first routing that prioritizes logical entity hierarchy over simple keyword matching.
  • Structured handoff contracts that prevent loss of context during complex multi-step smart home operations.
  • Dual-mode validation (cache_first_generate vs. query_capabilities_required) for balancing speed and safety in automation.
  • Automated recovery protocols for handling expired tokens, network timeouts, and missing device identities.
  • Local-first query resolution using data/devices.json to minimize unnecessary API overhead.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*