ワンクリックでManusで任意のスキルを実行

home-assistant-rest

スター8

フォーク2

更新日2026年6月23日 19:11

Control and query Home Assistant through the connector's call_service tool — REST API patterns, common domains, how to find entities before acting.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

IkarusMK

IkarusMK/AIcortex

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Home Assistant over REST (via call_service)

When to use

Reading state or controlling devices in Home Assistant through this connector.

Setup (once)

service_add(name="home-assistant",
            base_url="http://<ha-ip>:8123",
            token_env="HA_TOKEN")          # then secret_set("HA_TOKEN", <long-lived token>)

Patterns

Check it's alive: call_service(service="home-assistant", path="api/") → {"message":"API running."}
Read a state: GET api/states/<entity_id> (e.g. sensor.living_room_temp).
Call a service: POST api/services/<domain>/<service> with a JSON body, e.g. path="api/services/light/turn_on", json_body={"entity_id":"light.kitchen","brightness_pct":40}.

Common domains

light (turn_on/off, brightness_pct, rgb_color) · switch · climate (set_temperature) · cover (open/close) · media_player · scene (turn_on) · automation (trigger).

Discipline

Find the entity first (don't guess ids) — list api/states or search before acting.
Controlling a physical device is a state-changing action → confirm with the user first.
Use entity_id, never internal device ids, in service calls.

このリポジトリの他の Skills

同じリポジトリ

blameless-postmortem

IkarusMK/AIcortex

Write a blameless incident postmortem — timeline, impact, root cause, and concrete follow-ups, focused on systems not people.

2026-06-238

conventional-commits

IkarusMK/AIcortex

Write clear, conventional git commit messages — type(scope): summary, imperative mood, a body that explains the why.

2026-06-238

docker-image-hardening

IkarusMK/AIcortex

Build small, secure container images — pinned base, non-root user, multi-stage builds, no secrets in layers, minimal attack surface.

2026-06-238

rest-api-conventions

IkarusMK/AIcortex

Design predictable REST APIs — noun resources, correct status codes, pagination, consistent errors, and versioning.

2026-06-238

secret-handling

IkarusMK/AIcortex

Handle API keys, tokens and passwords safely — store them in the vault, reference by name, never in chat, repo, memory, or code.

2026-06-238

sql-index-review

IkarusMK/AIcortex

Diagnose slow queries and add the right indexes — read the query plan, index for filters/joins/sorts, avoid over-indexing.

2026-06-238

name	home-assistant-rest
description	Control and query Home Assistant through the connector's call_service tool — REST API patterns, common domains, how to find entities before acting.
category	Home Automation
tags	home-assistant, rest, call_service, smart-home

Home Assistant over REST (via call_service)

When to use

Reading state or controlling devices in Home Assistant through this connector.

Setup (once)

service_add(name="home-assistant",
            base_url="http://<ha-ip>:8123",
            token_env="HA_TOKEN")          # then secret_set("HA_TOKEN", <long-lived token>)

Patterns

Check it's alive: call_service(service="home-assistant", path="api/") → {"message":"API running."}
Read a state: GET api/states/<entity_id> (e.g. sensor.living_room_temp).
Call a service: POST api/services/<domain>/<service> with a JSON body, e.g. path="api/services/light/turn_on", json_body={"entity_id":"light.kitchen","brightness_pct":40}.

Common domains

light (turn_on/off, brightness_pct, rgb_color) · switch · climate (set_temperature) · cover (open/close) · media_player · scene (turn_on) · automation (trigger).

Discipline

Find the entity first (don't guess ids) — list api/states or search before acting.
Controlling a physical device is a state-changing action → confirm with the user first.
Use entity_id, never internal device ids, in service calls.