Hermes Agent Home Assistant connections come in four shapes, and the official plugin is the right pick for most people.

The other three exist for edge cases, mainly when Home Assistant needs to start the conversation.

Get Your Backlink Gameplan →Try Polar Rank Free for 3 Days →

If you are weighing tools for your business more broadly, get your Backlink Gameplan and we will help you pick the stack that brings in leads, or try Polar Rank free for 3 days.

Facts here come from the official docs and the plugin repo, read on 19 November 2026.

The options side by side

OptionWhat it doesWhat it needsBest for
Official homeassistant pluginGateway events plus four device toolsOne install command and HASS_TOKENAlmost everyone
API serverExposes Hermes as an OpenAI-compatible endpointAPI_SERVER_ENABLED and a keyApps that expect an OpenAI-style backend
Webhook routesRuns the agent when something POSTs an eventA route, a secret and port 8644HA automations that should trigger an agent run
Community custom integrationsLets HA call Hermes from its sideWhatever that project needsTesters happy with early builds

Pick the plugin when

  • You want to ask the agent about devices and have it act on them.
  • You want live events such as door sensors or thermostat changes pushed to the agent.
  • You want one token to switch on both directions.

That covers routines, security checks and reactive automations, all of which the docs show as examples.

Pick the API server when

  • You already run a chat frontend and want Hermes behind it.
  • You are comfortable treating Hermes as a model endpoint at http://localhost:8642/v1.

Note this route does not give you the ha_* device tools by itself.

Pick webhooks when

  • Home Assistant should fire the agent on its own schedule or trigger.
  • You want HMAC-signed requests and a prompt template per route.
  • You also want results delivered somewhere specific, which routes support through a deliver setting.

Pick a community integration when

  • You want Hermes to act as a voice or conversation agent inside Home Assistant itself.
  • You accept early-version risk; forum posts in this search describe alpha releases.

Check the project's own repo and recent activity before you install anything from it.

🔥 Want to see which agent setups members actually keep running? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members sharing what works. → Join the AI Profit Boardroom

Get Your Backlink Gameplan →Try Polar Rank Free for 3 Days →

What the official plugin includes

PieceDetail
Installhermes plugins install homeassistant, per profile
AuthLong-lived access token in HASS_TOKEN
AddressHASS_URL, default http://homeassistant.local:8123
Toolsha_list_entities, ha_get_state, ha_list_services, ha_call_service
EventsWebSocket state_changed, filtered by your watch lists
RepliesPersistent notifications titled Hermes Agent
SchedulingCron and webhook delivery to a notify target

The mistake that wastes the most time

People install the plugin, see it connect and then hear nothing.

That is by design: no events are forwarded until you add watch_domains, watch_entities or watch_all.

Add climate, binary_sensor and alarm_control_panel first, as the docs suggest.

Four more common mistakes

  1. Following an old guide that says to pip install hermes-agent[homeassistant]; that extra has been removed.
  2. Pasting a short-lived browser token instead of a long-lived one, which returns 401 errors.
  3. Installing the plugin in one profile and running another.
  4. Editing .env and forgetting that changes apply only after a gateway restart.

Safety defaults compared

The plugin blocks shell_command, command_line, python_script, pyscript, hassio and rest_command, and validates entity IDs.

The API server and webhook routes run the agent with whatever toolsets you allow, so their safety depends on your config.

Webhook routes at least require a secret for signature checks unless you deliberately set the test-only bypass.

📞 Comparing tools when you should be comparing results? Get your Backlink Gameplan and we will show you which search and AI visibility moves will move your numbers first, or try Polar Rank free for 3 days. Backlink Gameplan or try Polar Rank free for 3 days

Who each option suits

You areUse
A homeowner who wants voice-style control and alertsOfficial plugin
A business with a front-desk chat appAPI server behind that app
A tinkerer with complex HA automationsWebhook routes plus the plugin
An early adopter testing HA-side assistantsA community integration, in a test setup

Reliability notes

The plugin keeps a 30-second WebSocket heartbeat and reconnects with backoff from 5 to 60 seconds.

Outbound messages use a separate REST session so they do not clash with live events.

Each entity has a 30-second cooldown by default, which keeps chatty sensors under control.

Get Your Backlink Gameplan →Try Polar Rank Free for 3 Days →

Five questions that decide the option

  1. Should the agent start the conversation, or should Home Assistant? If the agent, take the plugin. If HA, add webhooks.
  2. Do you need device control from chat? Only the plugin's ha_* tools give you that directly.
  3. Do you already run an OpenAI-style chat app? Then the API server can put Hermes behind it.
  4. How much risk will you accept? Official code from Nous Research beats an alpha project for anything that touches locks or alarms.
  5. Who maintains it? A plugin from the official catalog updates with hermes update; a community add-on depends on its author.

Scenario: a flat with a few smart bulbs

The plugin alone covers it.

Watch the light domain only if you want on and off events; otherwise leave events off and use chat commands.

Scenario: a house with alarm, locks and sensors

Use the plugin with a focused watch list of binary_sensor and alarm_control_panel.

Schedule a nightly security check and let the agent report rather than act on locks.

Scenario: a busy automation setup

Keep your existing Home Assistant automations and add webhook routes for the moments an agent adds value, such as summarising a day of sensor data.

The route's prompt template can pull fields from the payload, and the deliver setting sends the result where you want it.

Scenario: a team building a front desk assistant

The API server makes Hermes reachable as an OpenAI-compatible backend on port 8642.

Pair it with the plugin in the same profile if the assistant should also answer questions about the building.

Signs you picked the wrong route

  • You keep writing glue scripts to fake device control: switch to the plugin.
  • Your agent fires every few seconds: your watch list is too wide, or watch_all is on.
  • You cannot tell which tool changed a device: route control through the plugin so every action is an ha_call_service call.
  • An add-on broke after an update: fall back to the official plugin while it is fixed.

Upgrade notes that change the choice

Older Hermes releases bundled Home Assistant support and used a pip extra called hermes-agent[homeassistant].

Get Your Backlink Gameplan →Try Polar Rank Free for 3 Days →

That extra is gone, and support now lives in the official plugin, so any comparison written before the change is out of date.

Existing setups move over during hermes update, keeping the same variables, platform name, toolset and cron syntax.

The one visible difference is that the ha_* tools now sit behind Tool Search when it is on, like every other plugin tool.

If a guide tells you to install an extra or edit core files, it predates the plugin and you can skip it.

Combining options without conflicts

You can run more than one route at once in the same Hermes profile.

A common pairing is the plugin for device control and live events, plus one webhook route for a Home Assistant automation that wants a summary.

The plugin handles the house; the route handles the one job HA should start.

Avoid running two gateways for the same profile, because the docs warn that duplicate instances send duplicate replies.

If you add the API server as well, give it its own key and keep it on localhost unless a frontend elsewhere needs it.

Keep a short note of which route does what, so a future you knows why each one exists.

What to read before you decide

The Home Assistant page in the Hermes docs is short and current, so read it end to end once.

Skim the plugin's own folder in the official repo to see exactly which files it adds.

Then decide, set up the one route you picked, and only add a second when the first is stable.

Who should skip all four

If you only want voice control of a few bulbs and never want alerts or reports, Home Assistant's own apps may be enough.

The agent earns its place when you want questions answered, checks run on a schedule, or events turned into plain messages.

Be clear on which of those you want before you set anything up, and the right option picks itself.

Setup time compared

The plugin is the quickest: one install, one token, one config block and a restart.

The API server adds two env lines and then whatever your frontend needs.

Get Your Backlink Gameplan →Try Polar Rank Free for 3 Days →

Webhook routes take longest, since you write the route, set the secret and build the automation that calls it.

Community integrations vary too much to estimate, so budget a test evening before trusting one.

What each option means for privacy

The plugin talks to your own Home Assistant over your own network, using a token you create and can revoke at any time.

The API server exposes the agent on a local port, with a key you set; only add CORS origins when a browser must call it directly.

Webhook routes open a port that accepts POSTs, so keep the secret set and the route list short.

Community add-ons vary, so read what each one sends and where before you trust it with your house.

How the event feed reads

State changes arrive as short sentences rather than raw JSON.

Climate shows the old and new HVAC mode with current and target values, sensors show the old and new reading, and door sensors read triggered or cleared.

That plain format is part of why the plugin beats a raw webhook for most event work.

Cost of each option in effort

  • Plugin: one command, one token, one config block.
  • API server: two env lines, then frontend setup.
  • Webhooks: route config, secret management and an HA automation to call it.
  • Community add-ons: unknown, depends on the project.

Bottom line on the choice

Start with the plugin, add webhook routes when HA needs to trigger work, and leave the rest for special cases.

The Hermes source code and the cron docs cover the extras once the basics work.

Members of the AI Profit Boardroom share their Home Assistant prompts and routines in the weekly calls.

Get Your Backlink Gameplan →Try Polar Rank Free for 3 Days →

FAQ: Hermes Agent Home Assistant

What is the best way to connect Hermes Agent to Home Assistant?

The official homeassistant plugin from the plugin catalog. It gives the agent device tools and live events from one token.

Is the old pip extra still needed?

No. The hermes-agent[homeassistant] extra was removed; the plugin declares its own dependency.

Can Home Assistant trigger Hermes instead?

Yes, by sending a signed POST to a Hermes webhook route, or through a community integration that calls Hermes from the HA side.

Does the API server include device control?

Not by itself. Device control comes from the ha_* tools that the plugin installs.

Why is nothing happening after setup?

Event filters are empty by default. Add watch_domains or watch_entities and restart the gateway.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

  • I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
  • I've grown a YouTube channel to 400,000+ subscribers.
  • I wrote "Link Building Mastery".
  • My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Choose the plugin, set your watch list, and only add the other routes when a real need shows up.

If you want help choosing the tools that grow the business itself, get your Backlink Gameplan, and bookmark this Hermes Agent Home Assistant comparison, or try Polar Rank free for 3 days.