Aqara Smart Home Connector for Muse
Control Aqara smart home devices (locks, scenes, sensors) via the Aqara Cloud API — an honest draft with some endpoints unconfirmed.
- What
- Control Aqara smart home devices (locks, scenes, sensors) via the Aqara Cloud API — an honest draft with some endpoints unconfirmed.
- Cost
- Free
- Needs
- An Aqara developer app with OAuth credentials (Aqara developer console — the OAuth code flow is fiddly; start in read-only mode to validate credentials before touching anything), kept in your Muse's secure vault (never paste secrets here). Honest caveat: some API paths/signatures in this connector are not confirmed against Aqara's public docs — expect trial and error. Always confirm before any lock, scene, or automation change that physically affects the home.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that reads Aqara device status and sends commands through the Aqara Cloud API (device lists, scenes, and device actions). Honest caveat from its own SKILL.md: some API paths and signatures are NOT confirmed against Aqara's public docs, so expect trial and error — and always confirm with the user before any lock, scene, or automation change that physically affects the home. Aqara authentication is fiddly (a developer app with an OAuth code flow); start in read-only mode to validate credentials before touching anything that moves or locks. Uses Aqara API credentials, kept in Muse's secure vault. Draft: written from Aqara's public API docs, not yet live-tested end-to-end — Skill Harbor never reviews the code, review it yourself before use. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Quick answer
Aqara Smart Home Connector is a free, open-source Muse skill that reads Aqara device status and sends commands through the Aqara Cloud API, covering device lists, scenes and device actions. Some API paths and signatures are unconfirmed against public docs, so expect trial and error, and always confirm before any lock, scene or automation change affecting the home.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 6e31fd4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: An Aqara developer app with OAuth credentials (Aqara developer console — the OAuth code flow is fiddly; start in read-only mode to validate credentials before touching anything), kept in your Muse's secure vault (never paste secrets here). Honest caveat: some API paths/signatures in this connector are not confirmed against Aqara's public docs — expect trial and error. Always confirm before any lock, scene, or automation change that physically affects the home. No GitHub account needed unless listed here. Install "Aqara Smart Home Connector for Muse" for me. A Muse agent skill that reads Aqara device status and sends commands through the Aqara Cloud API — with some endpoints unconfirmed, so start read-only. Repository: https://github.com/bluman1/muse-connectors/tree/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/aqara Pinned version: install the code at commit 6e31fd44a71f9f28377a1460e64cd7483c3cce22 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "aqara". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Aqara OAuth credentials in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 6e31fd4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.