2.5 KiB
2.5 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Home Assistant | system | active | 2026-07-22 | 2026-10-12 | 2026-10-12 | medium |
|
|
Home Assistant
Purpose
Home automation and device control; one of Hermes's messaging/integration platforms.
Location
- Verified 2026-10-12 (live HTTP): Home Assistant OS answers HTTP
200onhttp://100.68.139.5:8123/over Tailscale, and the Tailscale nodehomeassistant(100.68.139.5) is active offering an exit node. The service is up and reachable on the tailnet. - Verified (homelab infra docs, not this host): VM 100 on
pve, hostnamehaos14.0(Home Assistant OS), internal IP172.30.232.1.qm listconfirms VMID 100homeassistantis running (13 GB RAM). - Verified (Hermes config):
homeassistantandhermes-homeassistantappear in Hermes's platform/display integration lists (~/.hermes/config.yaml), alongsideqqbot,signal,slack,teams,telegram. - Unknown: the actual connection details (HA base URL, long-lived access token, which entities/automations Hermes can reach) are not present in the sanitized config snapshot — likely held in a plugin-specific credentials file not captured there, or not yet wired up beyond being enabled as a platform.
Current configuration
2026-10-12: HA itself is confirmed up (HTTP 200 on :8123, VM running). Still not verified: that Hermes can actually reach an entity — no automation, entity list, or voice-assistant config has been confirmed from this host, and no HA credentials were found on CT460.
Connected systems
- systems/hermes-agent
- infrastructure/proxmox — Runs as VM 100 on PVE
- systems/messaging-integrations — Integration platform
- systems/homepage-dashboard — Shown in dashboard More tab
Known issues
- Partially closed 2026-10-12: HA itself is confirmed running and reachable (HTTP 200 on
100.68.139.5:8123). Still open: whether Hermes can actually use it — a live call to a known HA entity would settle it, and requires the HA credentials, which are not on CT460.
Change history
- 2026-10-12: HA service confirmed UP — HTTP 200 on tailnet
:8123, Tailscale nodehomeassistantactive/exit-node, VMID 100 running perqm list. Confidence raised low → medium. Hermes↔HA entity access remains unverified.
Relevant runbooks
None yet — would be a good candidate once the connection is verified (e.g. runbooks/restart-home-assistant-bridge).