Hermes HA Integration

What Hermes HA Integration does

Hermes HA Integration connects a running Hermes Agent to Home Assistant as a conversation agent for voice assistants and the conversation panel. Replies stream, so the first token arrives quickly in voice pipelines. The integration reuses Hermes sessions through the X-Hermes-Session-Id header so short voice turns keep their context, and it can key that continuity from device_id or satellite_id and pass room context into the prompt.

Exposed Home Assistant entities, with their names, aliases, domains, areas and states, can be included in the system prompt. Follow-up listening can stay off, stay always on, or open only when Hermes asks a question. Each config entry creates a device showing API connectivity, latency and the last successful connection. Several instances can point at the root API, Home Assistant add-on profile routes or native Hermes multiplexer routes, which suits setups with more than one Hermes profile.

Key features

• Hermes Agent as a Home Assistant conversation agent for voice and the conversation panel
• Streaming replies for low-latency voice pipelines
• Hermes session reuse across short voice turns with a configurable timeout
• Optional inclusion of exposed entities and device or satellite context in the prompt
• Follow-up listening modes: off, always on, or only when Hermes asks a question
• Support for multiple instances and Hermes profile routes

When to use it

• Talking to Hermes Agent through a Home Assistant voice satellite
• Letting Hermes answer questions about the current state of smart home devices
• Pointing different Home Assistant assistants at different Hermes profiles

Who it is for: Home Assistant users who run Hermes Agent and want it to answer as their voice assistant.

How it fits with Hermes Agent

Built for Hermes Agent. It talks to the Hermes API server and works with the Hermes Agent add-on for Home Assistant or a standalone Hermes instance.

Requirements: Home Assistant 2024.12 or newer, and a running Hermes Agent instance with the API server enabled

FAQ