sam-4screen-desktop 2026-9-14:8:3:7

300 areas/360 Dev-Ops Network Computers/Error Tracking.md

@@ -96,3 +96,24 @@ Two things misled the diagnosis:
 - `[s3_web]` present; web server confirmed running (log line + port 3902 bound) → the earlier "no s3_web / not running" diagnosis was wrong.
 - Port map: 3900 S3 API · 3902 S3 web · 3903 admin API · 3909 garage-webui. No port conflict.
 - Documented in the Garage section of [[Backup System — Borg, Kopia & Restic]] and the kontra.day site handoff.
+
+## 2026-09-14 — Voice: ESP32 green, never blue; then no response
+
+### Symptom
+The ESP32 LED turned green but never blue. The bridge, whisper, and broker were up.
+
+### Root cause
+Three failures in one chain.
+
+- The voice_bridge OpenWakeWord process was wedged. It used 0.01% CPU and ignored audio.
+- The ESP32 MQTT client was in a stale state. The broker dropped it for keepalive timeouts. It published no audio.
+- The voice-agent process ran for 7 days without the MQTT reconnect patch. Journald restarted and lost the agent stdout socket, so the agent logs vanished. The agent never re-subscribed to the .30 topic.
+
+### Fix
+- Restart the bridge container: `docker restart voice_bridge`
+- Power-cycle the ESP32
+- Restart the agent service: `sudo systemctl restart voice-agent`
+- Verify: journal shows `[mqtt] listening on 192.168.20.30:1883 homeassistant/voice/text`
+
+### Note
+The agent MQTT intake now retries and reconnects. A future broker flap heals itself. Report the LED state to exercise the chain end to end. Keepalive timeouts on ESP32 suggest a weak WiFi link; consider a stable keepalive or fixed install if it recurs.