research(ubiquiti): the controller's own device database has 701 records and no UDW-PRO (refs #130) #2145

Merged
jaylouisw merged 1 commit from catalogue/1119-1152 into main 2026-11-19 12:11:59 +00:00
Owner

refs #130 (records evidence; does not close)

#130 asks for a Dream Wall Pro (UDW-PRO). Every earlier pass read surfaces a buyer sees (techspecs, store, datasheets, FCC, firmware index). This one reads the surface a device is matched against:

https://static.ui.com/fingerprint/ui/public.json — 200, application/json, 832,199 B, version 92e630d8…, Last-Modified: Tue, 17 Nov 2026 10:41:36 GMT — 701 device records.

  • UDW is one record: sysid ea2a, FCC SWX-UDW, shortnames UDW/UDW-BR/UDW-EU/UDW-EU-EA/UDW-R/UDW-US/UDW-US-EA.
  • UDW-PRO / UDWPRO occur 0 times in 832,199 bytes; all 18 udw hits are inside that one record.

Three calibrations make the empty result mean something: Pro tiers are separate rows in this line (UDM ea11 vs UDM-Pro ea15; UDR eccc vs UDR-5G-Max a6b9), 106 records carry a -PRO shortname, and the file keeps retired hardware (UAS-XG, no sysid) alongside 51 -EA records — UDW already lists its own -EA shortnames. An unreleased or retired Pro would still be visible here, so "the row was deleted" is not available as an explanation.

Limits recorded in the note: the record carries no PoE class or budget and only a 1000 Mbps ceiling, so this surface can prove absence but cannot model a device. No spec change — devices/ubiquiti/udw.json is untouched. Its 20 interfaces and 18 LAN / 2 WAN split agree with the record's own diagram; the note warns that the controller numbers every port eth0–eth19 while the spec names the two cages sfp1/sfp2, so eth18 is not a port the spec is missing.

Also cross-checked: all 34 console records resolve to a catalogue spec except UAS-XG (an application server) and UNKNOWN-CONSOLE (a placeholder) — the gateway line is fully covered, so #130 is not hiding behind an unmodelled sibling.

Gates: syntax-check 452 files OK; audit-port-types "No port contradicts its declared type"; check-control-bytes clean; hardware invariants 26 passed / 0 failed.

refs #130 (records evidence; does not close) #130 asks for a Dream Wall Pro (UDW-PRO). Every earlier pass read surfaces a *buyer* sees (techspecs, store, datasheets, FCC, firmware index). This one reads the surface a **device** is matched against: `https://static.ui.com/fingerprint/ui/public.json` — 200, `application/json`, 832,199 B, `version 92e630d8…`, `Last-Modified: Tue, 17 Nov 2026 10:41:36 GMT` — **701 device records**. - `UDW` is one record: sysid `ea2a`, FCC `SWX-UDW`, shortnames `UDW/UDW-BR/UDW-EU/UDW-EU-EA/UDW-R/UDW-US/UDW-US-EA`. - `UDW-PRO` / `UDWPRO` occur **0** times in 832,199 bytes; all 18 `udw` hits are inside that one record. Three calibrations make the empty result mean something: Pro tiers are separate rows in this line (`UDM` `ea11` vs `UDM-Pro` `ea15`; `UDR` `eccc` vs `UDR-5G-Max` `a6b9`), 106 records carry a `-PRO` shortname, and the file keeps retired hardware (`UAS-XG`, no sysid) alongside 51 `-EA` records — `UDW` already lists its own `-EA` shortnames. An unreleased or retired Pro would still be visible here, so "the row was deleted" is not available as an explanation. Limits recorded in the note: the record carries no PoE class or budget and only a 1000 Mbps ceiling, so this surface can prove absence but cannot model a device. **No spec change** — `devices/ubiquiti/udw.json` is untouched. Its 20 interfaces and 18 LAN / 2 WAN split agree with the record's own diagram; the note warns that the controller numbers every port `eth0`–`eth19` while the spec names the two cages `sfp1`/`sfp2`, so `eth18` is not a port the spec is missing. Also cross-checked: all 34 console records resolve to a catalogue spec except `UAS-XG` (an application server) and `UNKNOWN-CONSOLE` (a placeholder) — the gateway line is fully covered, so #130 is not hiding behind an unmodelled sibling. Gates: `syntax-check` 452 files OK; `audit-port-types` "No port contradicts its declared type"; `check-control-bytes` clean; hardware invariants 26 passed / 0 failed.
research(ubiquiti): the controller's own device database has 701 records and no UDW-PRO (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 3s
599ce3e35c
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 11:56:42 +00:00
jaylouisw deleted branch catalogue/1119-1152 2026-11-19 12:12:01 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2145
No description provided.