From 57946b7140c878aff48cad616b9e3a46881fd8b2 Mon Sep 17 00:00:00 2001 From: reachableceo Date: Wed, 2 Sep 2026 12:08:40 -0500 Subject: [PATCH] =?UTF-8?q?docs(ha):=20DHCP-table=20lock=20verdict=20?= =?UTF-8?q?=E2=80=94=20no=20lock=20OUIs,=20BLE-only=20likely=20[#619]?= 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 | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/HomeAssistant/needfromcharles.md b/HomeAssistant/needfromcharles.md index ef7c024..a8e7634 100644 --- a/HomeAssistant/needfromcharles.md +++ b/HomeAssistant/needfromcharles.md @@ -24,6 +24,13 @@ Cloud API sees zero devices (suspect BLE-only sensors). - [ ] 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)