Home Assistant Connector for Muse
Read entity states and call services on your Home Assistant instance. Service calls are confirmed first.
- What
- Read entity states and call services on your Home Assistant instance. Service calls are confirmed first.
- Cost
- Free
- Needs
- Your Home Assistant instance URL plus a long-lived access token (Home Assistant > your profile > Security > Long-Lived Access Tokens), kept in your Muse's secure vault (never paste secrets here). Note: service calls act on the physical home — confirm the exact domain, service, entity, and parameters first; reading needs no confirmation. Treat the instance URL as secret-adjacent. Home Assistant is free and self-hosted.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that talks to your own Home Assistant instance: list entity states (optionally filtered by domain), read one entity, and call services (e.g. `light.turn_on`). Service calls act on the physical home (lights, locks, climate) — confirm the exact domain, service, entity, and parameters first, unless standing permission exists; reading needs no confirmation. Uses a Home Assistant long-lived access token (your profile > Security > Long-Lived Access Tokens), kept in Muse's secure vault. Note: the instance URL is passed with every command — treat it as secret-adjacent and never post it publicly. Home Assistant is free and self-hosted. Draft: written from Home Assistant's public REST API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Quick answer
Home Assistant Connector for Muse is a free Muse skill that talks to your own Home Assistant instance: list entity states, optionally filtered by domain, read one entity, and call services like light.turn_on. It uses a Home Assistant long-lived access token from your profile.
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: Your Home Assistant instance URL plus a long-lived access token (Home Assistant > your profile > Security > Long-Lived Access Tokens), kept in your Muse's secure vault (never paste secrets here). Note: service calls act on the physical home — confirm the exact domain, service, entity, and parameters first; reading needs no confirmation. Treat the instance URL as secret-adjacent. Home Assistant is free and self-hosted. No GitHub account needed unless listed here. Install "Home Assistant Connector for Muse" for me. A Muse agent skill that talks to your Home Assistant instance: read entity states and call services, with service calls confirmed first. Repository: https://github.com/bluman1/muse-connectors/tree/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/home-assistant 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 "home-assistant". 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 Home Assistant instance URL and long-lived token 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
- It works with an API key or a token that you provide.
What the scan found — excerpts from the install prompt
- uses API keys or tokens — Prerequisites: Your Home Assistant instance URL plus a long-lived access token (Home Assistant > your profile
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 : uses API keys or tokens
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.