OpenClaw Assistant

__ACCESS_MODE__
⏳ Gateway: checking…
🔒 Secure context: checking…
📡 Access mode: __ACCESS_MODE__
💾 Disk: __DISK_USED__ / __DISK_TOTAL__ (__DISK_PCT__) — __DISK_AVAIL__ free
Open Gateway Web UI Open Terminal (full page)
Tips & token help
The gateway UI opens in a separate tab to avoid websocket/proxy issues with Ingress. Set gateway_public_url in add-on options if the button URL is wrong.
If the Gateway UI says Unauthorized, get your token from the terminal:
jq -r '.gateway.auth.token' /config/.openclaw/openclaw.json
(Since OpenClaw v2026.2.22+, openclaw config get redacts secrets — read the file directly instead.)
MCP setup (Home Assistant control)

MCP (Model Context Protocol) lets OpenClaw control Home Assistant entities, services, and automations directly.

Automatic (recommended)
  1. Create a Long-Lived Access Token in HA: click your profile avatar → scroll to Long-Lived Access Tokens → Create Token
  2. Paste it into add-on option homeassistant_token in Settings → Add-ons → Configuration
  3. Set auto_configure_mcp to ON in add-on Configuration
  4. Restart the add-on — MCP is configured automatically
Manual (terminal) 
mcporter config add HA "http://localhost:8123/api/mcp" \
  --header "Authorization=Bearer YOUR_LONG_LIVED_TOKEN" \
  --scope home
After upgrades — if OpenClaw has stale HA data: 
mcporter call home-assistant.GetLiveContext

Tip: The first MCP session needs a capable model (Gemini 3.1 Pro, Claude Sonnet 4, GPT-4.1). After setup, cheaper models work fine.

Reverse-proxy recipes (NPM / Caddy / Traefik / Tailscale)
Nginx Proxy Manager (NPM) 
Scheme:   https
Forward:  <HA-IP>:18789
WS:       ON
SSL tab:  Request a new SSL certificate (Let's Encrypt or custom)
Caddy 
openclaw.example.com {
    reverse_proxy <HA-IP>:18789
}
Traefik (docker labels) 
- "traefik.http.routers.openclaw.rule=Host(`openclaw.example.com`)"
- "traefik.http.routers.openclaw.tls.certresolver=le"
- "traefik.http.services.openclaw.loadbalancer.server.port=18789"
Tailscale HTTPS 
# 1. Set access_mode to tailnet_https in add-on configuration
# 2. Enable Tailscale HTTPS in your Tailnet admin: DNS → HTTPS Certificates
# 3. On the HA host:  tailscale cert <machine-name>.ts.net
# 4. Set gateway_public_url to https://<machine-name>.ts.net:18789