docs: clarify current unifi protect chime state
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
secret-guardrails / gitleaks (push) Has been cancelled

This commit is contained in:
Fizzlepoof
2026-05-26 20:10:45 +00:00
parent a282fe43bd
commit 77da65e64a
16 changed files with 193 additions and 43 deletions

View File

@@ -1,5 +1,10 @@
# UniFi Live Preflight Snapshot
Historical snapshot note:
- this file is a dated preflight capture from 2026-05-22
- preserve it as evidence, but do not treat it as the current source of truth for remaining work or final device placement
- later results and reversals are documented in `network-migration-remaining-checklist-2026-05-22.md` and `unifi-protect-doorbell-chime-current-state-2026-05-26.md`
Date: 2026-05-22
Mode: read-only live pull from PD using the Doris UniFi operator account
Controller: `https://10.5.0.1`
@@ -82,7 +87,7 @@ Interpretation:
- `58:d6:1f:54:e5:6d` -> `10.5.0.123`
- `58:d6:1f:54:e5:af` -> `10.5.0.189`
These are still the two management-lane ESP-class offenders to identify or evict.
Historical interpretation only: these were later identified as the two Protect WiFi chimes, so this section is evidence of the pre-identification state, not an open rediscovery task.
## Fresh anomalies vs the earlier planning assumptions