Home Assistant Control

Use Home Assistant REST API with a long-lived access token.

Requirements

For skill users (runtime)

• - INLINECODE0
• INLINECODE1
• INLINECODE2
• Home Assistant long-lived token (HA_TOKEN)
• Home Assistant public base URL (HA_URL_PUBLIC)

For skill maintainers (packaging/validation)

• - INLINECODE5
• INLINECODE6 (required by skill-creator validator/packager scripts)

Required environment variables

• - HA_TOKEN (required)
• INLINECODE9 (required; canonical target and fallback)
• Optional URL behavior:

Secrets handling (publish-safe)

• - Keep keys/URLs in an external file, not in the skill folder.
• Set HA_ENV_FILE=/absolute/path/to/file.env when you want file-based secret loading.
• If HA_ENV_FILE is not set, scripts only use environment variables already present in the shell.
• INLINECODE16 and scripts/self_check.sh load env file only when HA_ENV_FILE is provided.

Core workflow

1. 1. Parse the user request into target entity/service + desired action.
2. Check references/naming-context.md for manual alias mappings first.
3. Verify entity exists before changing state.
4. Execute service call.
5. Re-check state and report outcome clearly.

Useful endpoints

• - List states: INLINECODE20
• Single state: INLINECODE21
• Call service: INLINECODE22

Headers:

• - INLINECODE23
• INLINECODE24

Scripts

• - scripts/ha_env.sh — loads env file only when HA_ENV_FILE is explicitly set, using safe KEY=VALUE parsing (no source/eval).
• INLINECODE29 — generic API caller for Home Assistant.
• INLINECODE30 — generate references/entities.md from GET /api/states.

• - scripts/save_naming_context.sh — refresh references/naming-context.md for user-specific naming.

• - scripts/ha_entity_find.sh — search entities by partial entity id or friendly name.

• - scripts/ha_safe_action.sh — execute service actions with safety checks and risk confirmation.

• - scripts/self_check.sh — verify prerequisites and API connectivity/auth before running actions.

Safety

• - Confirm before high-impact actions (locks, alarms, garage/doors, heating shutdown).
• Do not print raw token values.
• If target entity is ambiguous, ask a follow-up question.
• Keep API paths scoped to Home Assistant endpoints only (/api/...).
• Use only HTTP(S) Home Assistant base URLs (HA_URL*), prefer HTTPS for public access.
• Avoid code execution when loading env files: parse key/value pairs, do not use source on untrusted paths.

Reference files

• - references/entities.md — entity inventory
• INLINECODE51 — user alias memory for natural names (e.g. "living room light")

Publishing notes

• - Keep examples generic (example_* IDs), no personal hostnames/tokens.
• Do not commit .env or any private env file with real tokens.
• Keep the skill focused: API workflow + reusable scripts + entity reference.