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

@@ -2,6 +2,11 @@
> For Doris: this worksheet exists so tomorrow does not devolve into vibes and guessing. Every device on Legacy CIA gets one label: migrate, quarantine, or kill.
Historical status note:
- this is a 2026-05-22 migration worksheet, not the current remaining-work checklist
- do not treat its "tomorrow" language as active backlog without checking later result docs
- current truth for Protect accessories lives in `unifi-protect-doorbell-chime-current-state-2026-05-26.md`
Goal: classify every remaining device on the legacy CIA Via VLAN/SSID so we can make deliberate decisions during and after the cutover.
Rules:
@@ -47,8 +52,8 @@ Use `kill` when all or most are true:
- MyQ -> IoT VLAN 40
- Samsung FamilyHub -> IoT VLAN 40
- LG dryer -> IoT VLAN 40
- doorbell -> Cameras VLAN 60
- Protect chimes -> Cameras VLAN 60
- doorbell -> Cameras VLAN 60 only if immediate validation is available
- Protect chimes -> Cameras VLAN 60 only after explicit Protect-path validation; current known-good live state keeps them on Management/default `UniFi Wireless`
### Migrate later / careful handling
- Google Home Mini -> IoT VLAN 40 after discovery testing
@@ -114,7 +119,7 @@ If answers are bad, it does not earn migration tomorrow.
### Protect chimes / doorbell
- These are not Legacy CIA end-state residents.
- Move to Cameras/Security as early cleanup.
- Treat Cameras/Security as the target design, not an automatic next action. The Wi-Fi chimes currently have a documented Management/default-SSID exception because the Camera override broke Protect health.
### old bulbs / old plugs
- If still useful but irrecoverable, quarantine.