Hermes BibleUnofficial Docs
← All docs Docs / Messaging Platforms

Home Assistant Integration

Home Assistant Integration Hermes Agent integrates with Home Assistant in two ways: 1. Gateway platform — subscribes to real time state changes via WebSocket an

Messaging Platforms
Section
Messaging Platforms
Source
hermesbible.com/docs/user-guide/messaging/homeassistant

Home Assistant Integration Hermes Agent integrates with Home Assistant in two ways: 1. Gateway platform — subscribes to real time state changes via WebSocket an

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Setup
  2. 1. Create a Long-Lived Access Token
  3. 2. Configure Environment Variables
  4. 3. Start the Gateway
  5. Available Tools
  6. ha_list_entities
  7. ha_get_state
  8. ha_list_services
  9. ha_call_service
  10. Gateway Platform: Real-Time Events
  11. Event Filtering
  12. Event Formatting
  13. Agent Responses
  14. Connection Management

Section map

Setup

Maps setup to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

1. Create a Long-Lived Access Token

Maps 1. create a long-lived access token to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

2. Configure Environment Variables

Maps 2. configure environment variables to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

3. Start the Gateway

Maps 3. start the gateway to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Available Tools

Maps available tools to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

ha_list_entities

Maps ha_list_entities to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

ha_get_state

Maps ha_get_state to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

ha_list_services

Maps ha_list_services to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Messaging Platforms doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Setup, 1. Create a Long-Lived Access Token, 2. Configure Environment Variables, 3. Start the Gateway, Available Tools. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: assistant, integration, integrates, gateway, platform. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitMessaging Platforms documentation

Use when you need orientation for home assistant integration before applying exact upstream commands.

Verify firstSetup

Open the source anchor for Setup and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Messaging Platforms, then open the linked source page for exact current syntax.
  2. Start with the source section for Setup; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for 1. Create a Long-Lived Access Token if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page