feat(ha): websocket driver tool; Govee integration live end-to-end [#620]

💘 Generated with Crush

Assisted-by: Crush:glm-5.2

HomeAssistant/needfromcharles.md

@@ -18,10 +18,15 @@ Cloud API sees zero devices (suspect BLE-only sensors).
 - [ ] Model numbers of your Govee temp sensors / lights:
 - [x] Govee app account email + password (thermometer readings require it):
 
-  **Agent (2026-09-02):** both accounts received, stored 0600 in
-  `~/.creds/govee.env`. But us.govee.com is a JS app the agent can't drive.
-  One human click needed: log in at us.govee.com → "Apply for API Key" →
-  paste the key here (or append `GOVEE_API_KEY=` to `~/.creds/govee.env`).
+  **Agent (2026-09-02, later):** DONE — integration configured end-to-end
+  via REST config flow: your API key accepted, account
+  `coo@reachableceo.com` verified (2FA `2937`), MQTT connected. Result:
+  **zero devices** — the cloud account simply has none exposed. Remaining
+  blocker is hardware: BLE-only sensors need either a BLE-LE-capable USB
+  dongle on pfv-bms (current Kensington is BT 2.0, no LE) or a Govee hub.
+  - [ ] Model numbers of the sensors (decides BLE vs WiFi path)
+  - One-click cleanup: delete the disabled duplicate "Govee" entry in
+    UI → Settings → Devices → Govee (removes 2 ghost diagnostic sensors)
 
 ## 3. HomeKit codes — blocks #619 (ecobee + front-door lock)
 - [ ] ecobee HomeKit setup code (8-digit, on paperwork/box if not the unit):
@@ -86,3 +91,6 @@ path. Temp + power monitoring for tsys6/tsys7 needs one of:
   - flip it in the iDRAC6 web UI (needs a TLS1.0-capable browser), or
   - upgrade iDRAC6 firmware (1.41 → 2.9x) then racadm set, or
   - accept `public` on the isolated OOB LAN for now
+
+  **Founder decision (2026-09-02): `public` accepted for tsys6.** Both
+  DRACs now answering SNMP; creds live in `~/.creds/idrac.env`.