techartdev 73646113ae Add OpenAI API integration and update translations
- Introduced `enable_openai_api` option in config.yaml to enable OpenAI-compatible Chat Completions endpoint.
- Updated `apply_gateway_settings` function to handle OpenAI API settings.
- Enhanced documentation in DOCS.md for integrating OpenClaw with Home Assistant Assist pipeline.
- Added translations for `enable_openai_api` in English, Bulgarian, German, Spanish, and Polish.
- Bumped version to 0.5.37 in config.yaml.
2026-02-09 20:13:40 +02:00
2026-02-01 02:28:53 +02:00
2026-02-06 12:48:19 +02:00

OpenClaw Assistant Home Assistant Add-on

OpenClaw Assistant

This repository contains a Home Assistant add-on that runs OpenClaw inside Home Assistant OS (HAOS).

Upstream rename history (FYI): clawdbot → moltbot → openclaw (final).

What you get

  • An always-on OpenClaw gateway running as a Supervisor-managed add-on.
  • A reliable Ingress landing page inside Home Assistant that includes:
    • an embedded web terminal (ttyd)
    • a button to open the Gateway Web UI in a separate browser tab (not embedded)
  • Persistent state under the add-on config directory (in-container: /config).

Why the Gateway UI is not embedded in Ingress

The Gateway Web UI requires WebSockets that can be flaky through HA Ingress depending on proxying/mixed-content. So we dont embed it. Instead, the Ingress page gives you a button that opens the Gateway UI directly using gateway_public_url.

Security model (high level)

  • The add-on does not manage or overwrite OpenClaws full config.
  • OpenClaw is configured via its own interactive tools (openclaw setup, openclaw onboard, openclaw configure) using the terminal.
  • On first boot only (when config is missing), the add-on bootstraps a minimal config to let the gateway start:
    • gateway.mode=local
    • gateway.auth.mode=token with a generated token

Install

  1. Home Assistant → Settings → Add-ons → Add-on store
  2. ⋮ → Repositories
  3. Add this repo:
    • https://github.com/techartdev/OpenClawHomeAssistant
  4. Install OpenClaw Assistant
  1. Open the add-on page (Ingress) and use the embedded terminal.
  2. Run one of:
    • openclaw onboard
    • openclaw configure
  3. (Optional, but recommended) Set gateway_public_url in add-on options.
    • Then the Ingress page will show an "Open Gateway Web UI" button.

See DOCS.md for a step-by-step first-time setup guide + troubleshooting.

Add-on options (kept intentionally small)

See openclaw_assistant/config.yaml for the authoritative schema.

  • enable_terminal (default: true) — enables the embedded web terminal.
  • gateway_public_url — only used to build the external Gateway UI link.
  • timezone
  • homeassistant_token (optional) — written to /config/secrets/homeassistant.token for local scripts.
  • router_ssh_* (optional) — SSH settings for a router/network device (custom automation).

Support / Donations

If you find this useful and you want to bring me a coffee to make more useful things, or support the project, use the link below:

S
Description
No description provided
Readme MIT 611 KiB
Languages
Shell 55.1%
Go Template 20.7%
Python 17.8%
Dockerfile 5.5%
JavaScript 0.9%