stocktake 2026-10-12: skills-index 346 skills/70 cats; freshness 54 stale/32 fresh/7 no-date; nanobot + home-assistant re-verified live (nanobot web UI back up on :8766, OmniRoute :8900 still closed -> stays degraded; HA HTTP 200 on :8123

This commit is contained in:
hermes
2026-10-12 03:17:10 +08:00
parent 6fc109e546
commit 0eee5f101e
7 changed files with 161 additions and 14 deletions
+10 -6
View File
@@ -3,9 +3,9 @@ title: Home Assistant
type: system
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
confidence: low
updated: 2026-10-12
verified_on: 2026-10-12
confidence: medium
tags: [system, automation]
sources: [raw/configs/hermes-config-sanitized.txt]
---
@@ -16,12 +16,13 @@ sources: [raw/configs/hermes-config-sanitized.txt]
Home automation and device control; one of Hermes's messaging/integration platforms.
## Location
- **Verified (homelab infra docs, not this host):** VM 100 on `pve`, hostname `haos14.0` (Home Assistant OS), internal IP `172.30.232.1`.
- **Verified 2026-10-12 (live HTTP):** Home Assistant OS answers HTTP `200` on `http://100.68.139.5:8123/` over Tailscale, and the Tailscale node `homeassistant` (`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`, hostname `haos14.0` (Home Assistant OS), internal IP `172.30.232.1`. `qm list` confirms VMID 100 `homeassistant` is **running** (13 GB RAM).
- **Verified (Hermes config):** `homeassistant` and `hermes-homeassistant` appear in Hermes's platform/display integration lists (`~/.hermes/config.yaml`), alongside `qqbot`, `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.
**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]]
@@ -30,7 +31,10 @@ Not verified beyond the platform being listed as available/connected in `current
- [[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.
- **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 node `homeassistant` active/exit-node, VMID 100 running per `qm 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`).
+6 -5
View File
@@ -3,8 +3,8 @@ title: Nanobot
type: system
status: degraded
created: 2026-07-22
updated: 2026-08-07
verified_on: 2026-08-07
updated: 2026-10-12
verified_on: 2026-10-12
confidence: high
tags: [system, nanobot, network]
sources: [live-probe, omniroute-investigation]
@@ -16,9 +16,9 @@ Role in Anthony's setup.
## Location
- **Verified 2026-07-22:** LXC 333, hostname `clawtest`, Tailscale IP `100.122.189.81`.
## Current state
- **Status: DOWN (as of 2026-08-07).** Connection refused on port 8900 — the OmniRoute provider connection to nanobot (`58debd59`, prefix `nanobot`) was causing event-loop stalls because every model sync + credential health check retried it. Connection disabled in OmniRoute. Nanobot on CT333 is not responding.
- **Prior state:** `nanobot` process listening on port `8766` (verified via `ss -tlnp` on ct333, 2026-07-22).
- `whatsapp-bridge.service` (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status unknown as of 2026-08-07.
- **Status: DEGRADED (re-verified 2026-10-12).** The Nanobot web UI on CT333 is **UP again**: HTTP `200` on `http://100.122.189.81:8766/` serving the nanobot web UI (verified this audit). However port `8900` — the endpoint the OmniRoute `nanobot` provider connection (`58debd59`, prefix `nanobot`) uses — is still **closed**, so the OmniRoute integration remains disabled. Contrast with 2026-08-07, when connection was refused on 8900 and no service was confirmed listening anywhere.
- **Prior state:** `nanobot` process listening on port `8766` (verified via `ss -tlnp` on ct333, 2026-07-22); DOWN 2026-08-07 (connection refused on 8900 — OmniRoute event-loop stalls from model sync + credential health-check retries; provider connection disabled in OmniRoute).
- `whatsapp-bridge.service` (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status not re-verified on 2026-10-12 (SSH to CT333 not reachable from CT460: connection timed out on 22/tcp; verification above is TCP/HTTP probing only).
- Publicly reachable via the same Cloudflare Tunnel as Hermes: `nanobot.martinwa.org` → `100.122.189.81:8766`, `nano-ssh.martinwa.org` → SSH on the same host. See [[infrastructure/domains-and-tunnels]].
## Current state as of 2026-07-22 (superseded — see below)
@@ -45,6 +45,7 @@ Role in Anthony's setup.
## Change history
- 2026-07-22: audit corrected "not running" claim after direct verification on ct333.
- 2026-08-07: status changed to DEGRADED — nanobot confirmed DOWN (connection refused on 8900). OmniRoute provider connection disabled. CT333 service status unknown.
- 2026-10-12: web UI confirmed back up (HTTP 200 on `100.122.189.81:8766`, tailnet IP `100.122.189.81` = tailscale node `clawtest`). Status stays DEGRADED because the OmniRoute port 8900 endpoint is still closed. `whatsapp-bridge.service` not re-verified (SSH to CT333 unreachable from CT460).
## Relevant runbooks
- [[runbooks/restart-hermes]]
+2 -2
View File
@@ -3,8 +3,8 @@ title: Installed Skills
type: system
status: active
created: 2026-07-22
updated: 2026-10-11
verified_on: 2026-10-11
updated: 2026-10-12
verified_on: 2026-10-12
confidence: high
tags: [skills, hermes]
sources: []