1.8 KiB
1.8 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-07-22 | 2026-07-22 | low |
|
|
Home Assistant
Purpose
Home automation and device control; one of Hermes's messaging/integration platforms.
Location
- Verified (homelab infra docs, not this host): VM 100 on
pve, hostnamehaos14.0(Home Assistant OS), internal IP172.30.232.1. - 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
Not verified beyond the platform being listed as available/connected in current-state.md's "WebUI connected platforms" line. No automations, entity lists, or voice-assistant config confirmed from this host.
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
- Genuine gap, not a "known issue" per se: this page cannot confirm HA is actively used by Hermes vs. merely enabled — worth verifying directly (e.g. a live call to a known HA entity) next time someone is in this area.
Relevant runbooks
None yet — would be a good candidate once the connection is verified (e.g. runbooks/restart-home-assistant-bridge).