KNEL/PFVCluster
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(ha): DHCP-table lock verdict — no lock OUIs, BLE-only likely [#619]

Browse Source 
💘 Generated with Crush

Assisted-by: Crush:glm-5.2
This commit is contained in:
mrcharles
2026-09-02 12:08:40 -05:00
parent 1f44a193a2
commit 57946b7140
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HomeAssistant/needfromcharles.md
+7
View File
@@ -24,6 +24,13 @@ Cloud API sees zero devices (suspect BLE-only sensors).
- [ ] Front-door lock brand/model: - [ ] Front-door lock brand/model:
cant you figure it out from dhcp table? 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): - [ ] Lock HomeKit code (if visible in its vendor app settings):
## 4. Emporia Vue 3 — blocks circuit-level power + BTU loop (#623/#614) ## 4. Emporia Vue 3 — blocks circuit-level power + BTU loop (#623/#614)