Home Assistant Gateways
Read what Home Assistant already knows about your home, and change only allowlisted entities, only on explicit request.
- What
- Read what Home Assistant already knows about your home, and change only allowlisted entities, only on explicit request.
- Cost
- Free
- Needs
- a real Home Assistant installation you own and run on your home network (typically on a Raspberry Pi or home server), plus a long-lived access token you created yourself in Home Assistant (profile, Security, long-lived access tokens) and a Muse setup that can reach Home Assistant through Home Link. The token grants your full account's API rights, so it is a credential: never paste it into chat, a skill file, or a repo. Home Assistant must stay local: do not port-forward or publish it to the internet for this skill.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a gadget skill for homes that already run Home Assistant, typically on a Raspberry Pi or home server, where Home Assistant is the single gateway to everything else. Instead of re-integrating each ecosystem, it reads the one place where climate, lights, presence, covers, media, and sensor states already surface as entities. The discipline starts before any question: confirm the Home Assistant base URL answers on the home network, inventory the entity list, match friendly names and rooms with the user (they rarely match the user's words out of the box), and agree an allowlist, which entities Muse may read, and the much smaller set it may ever act on. Status questions report the value, the room and device it maps to, and when the state last changed, so freshness can be judged; history questions use the history endpoint filtered to the relevant entities instead of guessing trends from a single read. Changes are the exception, not the default: only on explicit request, only for allowlisted entities, one service call per requested change, never extra devices added while at it, and safety-relevant domains (locks, covers, alarm panels, whole-home climate) get a spoken pause restating exactly what will change before anything moves. It never edits the installation itself: no automations, scenes, integrations, dashboards, or configuration changes from a skill session. The token behind it is owner-created and owner-stored, Home Assistant stays local with no port-forwarding, and entity history is household data, reported only as asked, never as proof a home is empty or secure. By @amanthakkar, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Home Assistant Gateways is a free Muse skill that reads the one place where your home already surfaces in Home Assistant: climate, lights, presence, covers, media and sensors. It agrees an allowlist with you first, changes only allowlisted entities on explicit request, and follows your Home Link rules if you have them, otherwise its own stay-local rules.
Install
Copy the install package below, then paste it into MusePrerequisites: a real Home Assistant installation you own and run on your home network (typically on a Raspberry Pi or home server), plus a long-lived access token you created yourself in Home Assistant (profile, Security, long-lived access tokens) and a Muse setup that can reach Home Assistant through Home Link. The token grants your full account's API rights, so it is a credential: never paste it into chat, a skill file, or a repo. Home Assistant must stay local: do not port-forward or publish it to the internet for this skill. Install "Home Assistant Gateways" for me. A gadget skill that reads state from an existing Home Assistant installation through its local API, and calls services only for owner-allowlisted entities, only on explicit request. Repository: https://github.com/amanthakkar/musecases/tree/main/skills/gadget-home-assistant-gateways 1. Fetch the SKILL.md file from the repository into a temporary folder and summarize what it does in one or two sentences. Do not paste the full SKILL.md text into this chat. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, credential harvesting). The token must never be pasted into chat. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "gadget-home-assistant-gateways". 4. Verify with no network calls: frontmatter valid, file in place. 5. Report what was installed, where, and what I still need to do myself (for example confirming the base URL, matching entities to rooms, and writing down the read and action allowlist). If your setup has the Home Link networking and safety rules document (~/docs/devices/home_link.md), follow it; if not, apply the stay-local rules in this prompt. 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 is in the prerequisites above. Rules: do not touch anything outside the temp folder and the install target. Read-only by default: no service call without my explicit request for an allowlisted entity, no editing automations, scenes, integrations, dashboards, or configuration, and no exposing Home Assistant beyond the local network. 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?
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.