From aa8239b74af3062110be62508573d1a8ec0eef06 Mon Sep 17 00:00:00 2001 From: reachableceo Date: Wed, 2 Sep 2026 18:01:52 -0500 Subject: [PATCH] docs: consolidate open asks into questions-09022206.md [#344] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit πŸ’˜ Generated with Crush Assisted-by: Crush:glm-5.2 --- HomeAssistant/needfromcharles.md | 98 +------------------------------- questions-09022206.md | 58 +++++++++++++++++++ 2 files changed, 61 insertions(+), 95 deletions(-) create mode 100644 questions-09022206.md diff --git a/HomeAssistant/needfromcharles.md b/HomeAssistant/needfromcharles.md index cacdef9..34bf8d9 100644 --- a/HomeAssistant/needfromcharles.md +++ b/HomeAssistant/needfromcharles.md @@ -1,96 +1,4 @@ +# needfromcharles.md β€” SUPERSEDED 2026-09-02 -> Working ask-file; knowledge docs live on Discourse: https://community.turnsys.com/c/vp-techops (audit log: https://community.turnsys.com/t/298) - -# needfromcharles.md β€” open asks from the agent (2026-09-01 night session) - -Answer inline below each item; the agent checks this file before asking again. - -## 1. Minisplit (Midea/Carrier) β€” blocks #614 -Your login `charles@turnsys.com` was rejected by all three Midea cloud -backends (SmartHome / Midea Air / NetHome Plus). Likely a Carrier-specific -backend or a different account. -- [ ] Exact app name on your phone that controls the minisplit: -- [ ] Account email that app uses (if different): -- [ ] (If MSmartHome-family) password for that account: - -## 2. Govee β€” blocks #620 device data -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, 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): - -- [ ] Front-door lock brand/model: -cant you figure it out from dhcp table? - - **Agent (2026-09-02):** checked β€” active 192.168.1.x leases have no - lock-brand MAC OUIs (every lease accounted for: ecobee, TP-Link extender, - Amazons, iPhone, Cisco phone, Dell, sectestbed/preprod VMs). HA has zero - lock entities (of 273) and Z-Wave JS none. Lock is almost certainly - BLE-only (typical for HomeKit locks) β€” DHCP cannot name it. Need: brand, - or just the 8-digit HomeKit code from the vendor app. - -- [ ] Lock HomeKit code (if visible in its vendor app settings): - -## 4. Emporia Vue 3 β€” blocks circuit-level power + BTU loop (#623/#614) -- [ ] Ordered? ETA: - -## 5. Decisions (yes/no) -- [ ] UniFi mDNS/multicast setting change may briefly re-provision APs - (short WiFi blip) β€” OK to apply tonight? - -yes. apply to one ap at a time. - -- [ ] Re-enable HA core watchdog (was disabled to break the boot loop; - box has been stable since)? - -yes. - - -- [ ] Uninstall the crash-looping community SSH add-on (a0d7b954_ssh)? - (core_ssh on 22222 is the keeper) - -yes - -- [ ] k8s rebuild tonight or next session? - -i am doing in other session - -## 6. Friday onsite (#629 β€” unchanged) -Dongle manual/app check Β· minisplit nameplate photo Β· ecobee + lock codes -(if not provided above) Β· Tripp Lite USB reseat (#372) Β· Emporia CT install. - -## 7. Small hygiene -- [ ] Re-enroll Pi-hole TOTP in your authenticator (secret in - `~/.creds/pihole.env`) β€” password already rotated. - -## 8. UniFi controller API key (added 2026-09-02) β€” blocks proper mDNS fix [#619] -UniFi Network 9 removed the classic API. Please create an Integration API key: -UniFi UI β†’ Settings β†’ System β†’ Advanced β†’ Integrations β†’ API Keys β†’ Add. -- [ ] Paste the key here (or ~/.creds/unifi-api.env): - -## 9. iDRAC/IPMI credentials (added 2026-09-02) β€” blocks #625 -Both OOB ports are live but predate Redfish; IPMI (623/UDP) is the only data -path. Temp + power monitoring for tsys6/tsys7 needs one of: -- [x] iDRAC root password for both, or - - **Agent (2026-09-02):** creds worked β€” BOTH iDRAC SNMP agents now live. - tsys7: community set to kn3lmgmt (verified). tsys6: agent enabled, but fw - 1.41 refuses racadm community changes (stays `public`). Pick one: - - 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`. +Consolidated into `questions-09022206.md` (repo root). Do not add asks here. +Knowledge docs: https://community.turnsys.com/c/vp-techops diff --git a/questions-09022206.md b/questions-09022206.md new file mode 100644 index 0000000..14a2439 --- /dev/null +++ b/questions-09022206.md @@ -0,0 +1,58 @@ +> Working ask-file; knowledge docs live on Discourse: https://community.turnsys.com/c/vp-techops (audit log: https://community.turnsys.com/t/298) +# questions-09022206.md β€” consolidated open asks (2026-09-02) + +> Merged from `questions-v2.md` (repo root) + `HomeAssistant/needfromcharles.md` +> per founder request. That file is now a pointer; questions-v2.md stays as +> history. Answer inline; agent checks before asking again. + +## HA / monitoring (was needfromcharles) + +### 1. Minisplit (Midea/Carrier) β€” blocks #614 +Login `charles@turnsys.com` rejected by all three Midea cloud backends. +- [ ] Exact app name on your phone that controls the minisplit: +- [ ] Account email that app uses: + +### 2. Govee β€” blocked on hardware path (#620/#683) +Integration live (key+account+MQTT); account has ZERO cloud devices = BLE-only. +- [ ] Sensor model numbers (decides BLE dongle vs hub): +- [x] API key β€” received + configured (2026-09-02) + +### 3. HomeKit codes β€” blocks #619 pairing (ecobee multicast-reachable NOW) +- [ ] ecobee 8-digit code: +- [ ] Lock brand/model: (verdict 2026-09-02: BLE-only β€” DHCP can't name it) +- [ ] Lock HomeKit code: + +### 4. Emporia Vue 3 β€” blocks #623 (BTU loop) +- [ ] Ordered? ETA: + +### 8. UniFi Integration API key β€” LOW priority now (multicast fix works) +- [ ] (optional) Settings β†’ System β†’ Advanced β†’ Integrations β†’ API Keys + +### 9. iDRAC β€” RESOLVED 2026-09-02 +[x] Creds worked; both SNMP agents live; tsys6 `public` accepted by founder. + +### NEW (2026-09-02) +### 10. DVR β†’ MotionEye (#711) +- [ ] DVR login (any user): +- [ ] Channel count: +(Night Owl; RTSP format documented on #711) + +### 11. DIRIGERA Matter code (#712) β€” when you're back at the house +- [ ] IKEA app β†’ hub β†’ integrations β†’ share via Matter (11-digit code) + +### 12. WiZ bulbβ†’room mapping (#712) β€” Friday onsite +2 bulbs reserved (pfv-wiz-bulb-1/2 @ 192.168.1.150/.151); map MACsβ†’rooms, then +HA WiZ entries by host + we identify the other ~11 lights' integration. + +## General (was questions-v2) + +### Q7. Close #167 (old garage UPS rebuild, superseded)? β€” still open +### Q9. Session-start gate relaxation β€” superseded by scope-alignment gate +### Q10. Git flow: keep direct-push for PFVCluster? β€” still open (default: keep) +(Q8 Friday order β€” moot, that Friday passed) + +## Founder decisions pending +- #626 Cloudron HA access architecture (a/b/c on ticket β€” recommend proxy) +- #684 PBS session scheduling (+ drive-rotation target design) +- TasmoAdmin uninstall (stopped+disabled 2026-09-02 β€” full uninstall?) +- Govee disabled dup entry: one-click delete in HA UI