Use Case · infrastructure · home assistant add-on

OpenClaw Home Assistant Add-on: Run Gateway Inside Home Assistant OS

The Showcase lists a community Home Assistant Add-on that runs OpenClaw gateway on Home Assistant OS, including persistent state and SSH tunnel support.

Last updated: 2026-03-10 · Language: English

0) TL;DR (3-minute launch)

Many home labs already use Home Assistant as the always-on control hub.
Workflow in short: Install Home Assistant add-on → configure OpenClaw gateway options in add-on settings → start service and verify health logs → connect one channel (for example Telegram) → run daily commands through Home Assistant-hosted gateway
Start fast: Use the add-on repository README linked from Showcase as the source of truth.
Guardrail: Do not expose gateway endpoints publicly without authentication and network controls.

1) What problem this solves

Many home labs already use Home Assistant as the always-on control hub. Running OpenClaw separately can add extra host management overhead. This add-on path keeps gateway runtime close to existing home automation infrastructure and centralizes operational checks in one system.

2) Who this is for

Home Assistant OS users who prefer add-on based deployment
Makers running Raspberry Pi or similar home controllers
Operators who want persistent OpenClaw state inside current home stack

3) Workflow map

Install Home Assistant add-on
   -> configure OpenClaw gateway options in add-on settings
   -> start service and verify health logs
   -> connect one channel (for example Telegram)
   -> run daily commands through Home Assistant-hosted gateway

4) MVP setup

Use the add-on repository README linked from Showcase as the source of truth
Install the add-on and set persistent storage exactly as documented
Connect one low-risk channel and run smoke tests (status, help, simple tasks)
If remote access is needed, enable SSH tunneling only after local testing succeeds
Create a backup routine for add-on configuration and OpenClaw state files

5) Prompt template

You are my Home Assistant OpenClaw operator.

Before suggesting any gateway change:
1) state current runtime status
2) list intended config change
3) provide rollback step
4) require confirmation for network-exposed changes

After each change:
- run one health check
- report success/failure with logs to inspect next

6) Cost and payoff

Cost

Add-on setup and routine maintenance whenever Home Assistant or OpenClaw versions change.

Payoff

Single-host operations for smart home + agent workflows with fewer moving parts.

Scale

Add remote tunneling and multi-channel routing after baseline stability is proven.

7) Risk boundaries

Do not expose gateway endpoints publicly without authentication and network controls
Treat add-on updates like infra changes: backup first, then roll forward
Separate household automation credentials from chat-channel credentials