fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
a6b268def5326550cc29cf9ef978552655d2ee9b
truenas-stacks/home/doris-dashboard/docs/old-iot-tomorrow-disposition-list.md
Fizzlepoof 77da65e64a
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details
secret-guardrails / gitleaks (push) Has been cancelled
Details
docs: clarify current unifi protect chime state
2026-05-26 20:10:45 +00:00

6.3 KiB
Raw Blame History

Old IoT Tomorrow Disposition List

For Doris: this is the concrete disposition call for every current live Old IoT client seen during read-only recon. This is the list to use tomorrow unless live validation proves otherwise.

Historical status note:

  • this is a 2026-05-22 planning artifact
  • several "tomorrow" items here were completed later; do not use this file as the current backlog without checking network-migration-remaining-checklist-2026-05-22.md

Source basis:

  • live UniFi read-only recon on 2026-05-22
  • all devices listed were active on SSID CIA Via through the U7 Pro
  • /home/fizzlepoof/repos/truenas-stacks/home/doris-dashboard/docs/unifi-readonly-recon-2026-05-22.md
  • /home/fizzlepoof/repos/truenas-stacks/home/doris-dashboard/docs/legacy-cia-triage-worksheet.md

Disposition labels:

  • migrate-now
  • migrate-later
  • quarantine
  • kill-candidate

1. Move tomorrow if practical (migrate-now)

MyQ-29B

  • IP: 192.168.1.130
  • Vendor: The Chamberlain Group, Inc
  • Tomorrow disposition: migrate-now
  • Target: IoT
  • Why:
    • known device
    • clear owner/function
    • easy-value migration win
  • Validation:
    • MyQ app still works
    • garage status/control behaves normally

Main-Floor

  • IP: 192.168.1.102
  • Vendor: ecobee inc
  • Tomorrow disposition: migrate-now
  • Target: IoT
  • Why:
    • known thermostat
    • clear function
    • deserves proper IoT placement
  • Validation:
    • thermostat visible in app
    • control/update works

Upstairs

  • IP: 192.168.1.131
  • Vendor: ecobee inc
  • Tomorrow disposition: migrate-now
  • Target: IoT
  • Why:
    • same reasoning as Main-Floor
  • Validation:
    • thermostat visible in app
    • control/update works

LG_Smart_Dryer2_open

  • IP: 192.168.1.186
  • Vendor: LG Innotek
  • Tomorrow disposition: migrate-now
  • Target: IoT
  • Why:
    • named appliance
    • low emotional/operational complexity
    • good early migration candidate
  • Validation:
    • LG app/device connectivity still works

Samsung-FamilyHub

  • IP: 192.168.1.149
  • Vendor: Samsung Electronics Co., Ltd
  • Tomorrow disposition: migrate-now
  • Target: IoT
  • Why:
    • known appliance
    • obvious long-term home
  • Validation:
    • Samsung app/features still work at the acceptable level

2. Move only if time/energy remains, otherwise defer (migrate-later)

Google-Home-Mini

  • IP: 192.168.1.185
  • Vendor: Google, Inc.
  • Tomorrow disposition: migrate-later
  • Target: IoT
  • Why:
    • discovery/cast pain risk
    • likely to provoke panic-rule temptation
  • Tomorrow handling:
    • move only if the rest of the window is already stable
    • if ugly, revert or leave on Legacy CIA quarantine
  • Validation:
    • app sees device
    • casting/discovery from Trusted behaves acceptably

3c:8d:20:f3:92:36

  • IP: 192.168.1.192
  • Vendor: Google, Inc.
  • Tomorrow disposition: migrate-later
  • Target: likely IoT
  • Why:
    • Google-class unknown-by-name device
    • same discovery/cast risk profile
  • Tomorrow handling:
    • identify what it is before moving if possible
    • otherwise defer
  • Validation:
    • whatever its expected Google behavior is still works

90:ca:fa:b6:7f:6e

  • IP: 192.168.1.129
  • Vendor: Google, Inc.
  • Tomorrow disposition: migrate-later
  • Target: likely IoT
  • Why:
    • likely another Google/cast/discovery problem child
  • Tomorrow handling:
    • identify first if possible
    • otherwise defer
  • Validation:
    • expected Google behavior survives move

3. Leave on Legacy CIA quarantine tomorrow unless identified better (quarantine)

5c:61:99:41:73:40

  • IP: 192.168.1.172
  • Vendor: Cloud Network Technology Singapore Pte. Ltd.
  • Tomorrow disposition: quarantine
  • Why:
    • unnamed
    • unclear function
    • not enough evidence to grant clean-IoT membership
  • Tomorrow handling:
    • leave on Legacy CIA with harsh restrictions
    • identify later

60:74:f4:54:fd:ec

  • IP: 192.168.1.136
  • Vendor: Private
  • Tomorrow disposition: quarantine
  • Why:
    • private/randomized identity
    • no useful name
    • function unclear
  • Tomorrow handling:
    • quarantine first, not migration first

60:74:f4:7b:6a:11

  • IP: 192.168.1.117
  • Vendor: Private
  • Tomorrow disposition: quarantine
  • Why:
    • same reasoning as above

c0:f5:35:20:5d:94

  • IP: 192.168.1.183
  • Vendor: AMPAK Technology,Inc.
  • Tomorrow disposition: quarantine
  • Why:
    • could be all sorts of embedded junk
    • no positive identification

d4:ad:fc:60:90:6a

  • IP: 192.168.1.100
  • Vendor: Shenzhen Intellirocks Tech co., ltd
  • Tomorrow disposition: quarantine
  • Why:
    • unclear function
    • likely disposable/low-trust smart junk unless proven otherwise

d4:ad:fc:ea:7f:65

  • IP: 192.168.1.101
  • Vendor: Shenzhen Intellirocks Tech co., ltd
  • Tomorrow disposition: quarantine
  • Why:
    • same reasoning as sister device above

4. Kill-candidate logic

No current Old IoT client is marked kill-candidate immediately from inventory alone because we still saw them as active.

But these become kill-candidate fast if:

  • nobody can identify them
  • nobody can say what they do
  • blocking/quarantining them produces no complaints
  • they are duplicate Google/embedded junk with no actual value

Most likely future kill-candidate pool:

  • the unnamed Private devices
  • the unknown Cloud Network / AMPAK devices
  • the two unnamed Intellirocks devices
  • any Google MAC-only device nobody can identify once mapped physically

5. Suggested tomorrow move order inside Old IoT

Use this order:

  1. MyQ-29B
  2. LG_Smart_Dryer2_open
  3. Samsung-FamilyHub
  4. Main-Floor ecobee
  5. Upstairs ecobee
  6. stop and assess
  7. only then test one Google device if the window is still calm

Everything else:

  • stays on Legacy CIA quarantine
  • gets documented
  • gets revisited later with actual identification work

6. Explicit anti-mistakes

Do not do these tomorrow:

  • do not migrate unknown MAC-only devices just because they are online
  • do not broaden IoT trust to appease Google discovery quickly
  • do not move quarantine-worthy junk into Management or Trusted
  • do not try to fully empty Old IoT if the window starts getting noisy

7. Success condition for tomorrow

A successful tomorrow outcome is:

  • easy-value named devices are moved into IoT
  • Google/discovery weirdness is either handled narrowly or deferred
  • all unknown junk remains contained on Legacy CIA
  • every remaining Old IoT device has an explicit reason it is still there
Reference in New Issue View Git Blame Copy Permalink