fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files

15
home/doris-dashboard/docs/unifi-readonly-recon-2026-05-22.md
View File

@@ -1,5 +1,10 @@
# UniFi Read-Only Recon Notes
Historical snapshot note:
- this file records the 2026-05-22 read-only discovery pass
- preserve it as evidence, but do not use it as the current next-step checklist without checking later outcome docs
- 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 only
Auth status: verified working with upgraded Doris admin login
@@ -79,9 +84,9 @@ Likely quarantine until identified better:
### 6. Camera lane live state
- `front-doorbell` is already on Camera network at `10.5.20.217`
Interpretation:
- the doorbell is already where it belongs logically
- tomorrow’s security cleanup work is mainly about chimes and future policy tightening
Interpretation at the time:
- the doorbell was already in the expected camera lane during this snapshot
- later follow-up changed the chime guidance, so do not treat this paragraph as the final remaining-work instruction set
### 7. Trusted lane still carrying infrastructure-class hosts
Trusted currently includes:
@@ -131,8 +136,8 @@ Interpretation:
- Rocinante needs a quick extra look because the client is live on port 2 but that port did not show an explicit profile name in the returned record
## Recommended next actions for tomorrow
1. identify the two Management `espressif` devices before or during the window
1. historical note: the two Management `espressif` devices were later identified as Protect WiFi chimes; do not treat this as an open rediscovery task
2. move/changeprofile for server ports on the USW Pro HD 24 one at a time
3. treat Google devices as late-batch or defer
4. treat unknown Old IoT clients as quarantine by default, not migration by default
5. keep Camera cleanup focused on chimes and policy, because the doorbell is already in the correct lane
5. keep Camera cleanup focused on validated policy and documented exceptions; the doorbell was already in the correct lane during this snapshot, but later chime guidance changed