4.2 KiB
4.2 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-11-04 | 2026-11-04 | medium |
|
|
Home Assistant
Purpose
Home automation and device control; one of Hermes's messaging/integration platforms.
Location
- Verified 2026-11-04 (live HTTP): Home Assistant OS answers HTTP
200onhttp://100.68.139.5:8123/over Tailscale. The service is up and reachable on the tailnet. - Verified 2026-11-04 (live,
qm list/qm configon thepvehypervisor): VM 100 is namedhomeassistant, status running,memory: 5100MiB,cores: 2,agent: enabled=1,ostype: l26,net0: virtio=…:bridge=vmbr0.- ⚠ Corrected 2026-11-04. The old page said 13 GB RAM and attributed that figure to "homelab infra docs, not this host". The live hypervisor reports 5100 MiB — the RAM figure was wrong and is now sourced from the hypervisor rather than from docs.
- ⚠ Corrected 2026-11-04 — host attribution. The page placed VM 100 on "
pve", which is correct, but only becausepve=100.96.100.82(PVE-A); there is no VM 100 onm93p(qm liston100.104.51.98returns no VM 100 at all — it holdscachyos-m93pandopenmausbot-vmonly). The page should not be read as implying a second HA guest on PVE-B. - Still unverified: the guest's own hostname (
haos14.0in the docs) and its internal LAN IP (172.30.232.1) — neither is observable from the hypervisor or the tailnet, so those two values remain doc-derived.
- Exit-node status corrected 2026-11-04: the
homeassistantTailscale node hasExitNodeOption: true(it offers exit-node service) butExitNode: false(it is not currently serving as one). The old wording — "active offering an exit node" — read as though it were actively routing traffic. It is reachable as a tailnet peer only. - 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-11-04: HA itself is confirmed up (HTTP 200 on :8123, VM 100 running with 5100 MiB / 2 cores). 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-11-04: re-verified live. HTTP
200on tailnet:8123confirmed; VM 100homeassistantconfirmed running on thepvehost with 5100 MiB / 2 cores (the page's 13 GB was wrong); confirmed no VM 100 exists onm93p; exit-node claim corrected — the node offers exit-node service (ExitNodeOption: true) but is not serving it (ExitNode: false). The guest hostname and internal IP remain doc-derived and unverified. Confidence stays medium (service health is high-confidence; Hermes↔HA entity access remains unverified). - 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).