devices(ubiquiti): one UDM-Pro row with two 10G cages, not a 10G copper port (#130) #2093

Merged
jaylouisw merged 1 commit from catalogue/1119-0452 into main 2026-11-19 05:09:07 +00:00
Owner

Refs #130 - this does not close it.

The catalogue bug, one device. devices/ubiquiti/ described the UDM-Pro twice and both copies were wrong about the 10G side. UDM-Pro.json (the file holding the model string) modelled the second cage as a bare ethernet 10G port with no connector: one cage, plus a 10G port nothing can seat in - a guessed port of exactly the kind the evidence rule forbids. unifi-dream-machine-pro.json had the right count but under model "UniFi Dream Machine Pro" (a product name), category host, and the engine's host capability, which means an end device that terminates packets (engine/device.js) rather than a console that hosts apps, on a gateway.

Vendor census (read today, text layer + rendered table).

  • https://dl.ui.com/ds/udm-pro.pdf - HTTP 200, 353,553 B, application/pdf, 2 pages: Networking interface (8) LAN: GbE RJ45 ports / (1) WAN: GbE RJ45 port; SFP+ interface (1) LAN: 10G SFP+ / (1) WAN: 10G SFP+; IDS/IPS 3.5 Gbps; max power consumption 33 W; internal 50 W PSU.
  • https://techspecs.ui.com/unifi/cloud-gateways/udm-pro - HTTP 200, 676,527 B: same count as a table, 1 GbE RJ45 = 9 (1G/100M/10M) and 10G SFP+ = 2 (10G/1G); its Datasheet button points at the same PDF.

Result: 9x 1G RJ45 (1 WAN + 8 LAN, speedCaps 10/100/1000), 2x 10G SFP+ cages (connector sfp+, speedCaps 1000/10000), no PoE. devices/ubiquiti/UDM-Pro.json now models that once, with aliases for both spellings so search does not lose the deleted name, and scripts/merge-research.js's inline entry is corrected so regeneration cannot reintroduce the connector-less port.

Naming trap recorded for the next pass: dl.ui.com/ds/udm-pro.pdf is the real datasheet, while dl.ui.com/ds/udm-pro_ds.pdf - the suffix many other Ubiquiti datasheets use - answers 302 to the techspecs front page. A 302 on a _ds path therefore never proved a datasheet was missing. The same control was applied to the UDW-PRO slugs in research/ubiquiti-udw-pro-doc-slug-controls.md (added here, re-measured today: qig/udw/ 200/6,310 B and qig/udm-pro/ 200/6,185 B against qig/udw-pro/ 302/313 B; udw-pro.pdf 302/285 B under five spellings).

Gates. syntax-check.js 440 files OK; audit-port-types.js 2,356 models / 29,715 ports / 0 offending ports; test/hardware-invariants.test.js 26/26; test/device-aliases.test.js 13/13; test/faceplate-catalogue.test.js 14/14; test/apply-research.test.js 10/10; npm test 361 suites, 12,381 assertions, 0 failed. Registry regenerated (2,357 -> 2,356 models; Ubiquiti 369 -> 368).

Issue 130 stays open and blocked. Nothing in this pull request names a UDW-PRO port, PoE wattage or part number; the Pro remains absent from Ubiquiti's techspecs index, both dl.ui.com document trees, the storefront commerce API and its own firmware platform list. Modelling it from the non-Pro UDW's numbers is the family-sibling error this catalogue has corrected three times.

Refs #130 - this does not close it. **The catalogue bug, one device.** `devices/ubiquiti/` described the UDM-Pro twice and both copies were wrong about the 10G side. `UDM-Pro.json` (the file holding the model string) modelled the second cage as a bare `ethernet 10G` port with **no connector**: one cage, plus a 10G port nothing can seat in - a guessed port of exactly the kind the evidence rule forbids. `unifi-dream-machine-pro.json` had the right count but under model `"UniFi Dream Machine Pro"` (a product name), category `host`, and the engine's `host` capability, which means an end device that terminates packets (`engine/device.js`) rather than a console that hosts apps, on a gateway. **Vendor census (read today, text layer + rendered table).** - `https://dl.ui.com/ds/udm-pro.pdf` - HTTP 200, 353,553 B, `application/pdf`, 2 pages: `Networking interface (8) LAN: GbE RJ45 ports` / `(1) WAN: GbE RJ45 port`; `SFP+ interface (1) LAN: 10G SFP+` / `(1) WAN: 10G SFP+`; IDS/IPS 3.5 Gbps; max power consumption 33 W; internal 50 W PSU. - `https://techspecs.ui.com/unifi/cloud-gateways/udm-pro` - HTTP 200, 676,527 B: same count as a table, `1 GbE RJ45 = 9 (1G/100M/10M)` and `10G SFP+ = 2 (10G/1G)`; its Datasheet button points at the same PDF. Result: 9x 1G RJ45 (1 WAN + 8 LAN, speedCaps 10/100/1000), **2x 10G SFP+ cages** (connector `sfp+`, speedCaps 1000/10000), no PoE. `devices/ubiquiti/UDM-Pro.json` now models that once, with `aliases` for both spellings so search does not lose the deleted name, and `scripts/merge-research.js`'s inline entry is corrected so regeneration cannot reintroduce the connector-less port. **Naming trap recorded for the next pass:** `dl.ui.com/ds/udm-pro.pdf` is the real datasheet, while `dl.ui.com/ds/udm-pro_ds.pdf` - the suffix many other Ubiquiti datasheets use - answers 302 to the techspecs front page. A 302 on a `_ds` path therefore never proved a datasheet was missing. The same control was applied to the UDW-PRO slugs in `research/ubiquiti-udw-pro-doc-slug-controls.md` (added here, re-measured today: `qig/udw/` 200/6,310 B and `qig/udm-pro/` 200/6,185 B against `qig/udw-pro/` 302/313 B; `udw-pro.pdf` 302/285 B under five spellings). **Gates.** `syntax-check.js` 440 files OK; `audit-port-types.js` 2,356 models / 29,715 ports / 0 offending ports; `test/hardware-invariants.test.js` 26/26; `test/device-aliases.test.js` 13/13; `test/faceplate-catalogue.test.js` 14/14; `test/apply-research.test.js` 10/10; `npm test` 361 suites, 12,381 assertions, 0 failed. Registry regenerated (2,357 -> 2,356 models; Ubiquiti 369 -> 368). **Issue 130 stays open and blocked.** Nothing in this pull request names a UDW-PRO port, PoE wattage or part number; the Pro remains absent from Ubiquiti's techspecs index, both `dl.ui.com` document trees, the storefront commerce API and its own firmware platform list. Modelling it from the non-Pro UDW's numbers is the family-sibling error this catalogue has corrected three times.
devices(ubiquiti): one UDM-Pro row with two 10G cages, not a 10G copper port
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 15s
CI / Arm auto-merge (pull_request) Successful in 3s
22a4f465e0
UDM-Pro.json modelled the second 10G cage as a bare `ethernet 10G` port with
no connector: one cage, plus a 10G port nothing can seat in. A second file,
unifi-dream-machine-pro.json, described the same box again under a product
name, category `host` and the engine's `host` capability - an end device that
terminates packets, on a gateway.

Vendor census, read today: dl.ui.com/ds/udm-pro.pdf (200, 353,553 B, 2 pp)
prints "(8) LAN: GbE RJ45 ports / (1) WAN: GbE RJ45 port" and "SFP+ interface
(1) LAN: 10G SFP+ / (1) WAN: 10G SFP+"; techspecs.ui.com .../udm-pro (200,
676,527 B) prints the same count as a table, 1 GbE RJ45 = 9, 10G SFP+ = 2.
So 9x 1G copper and 2x 10G SFP+ cages, no PoE. One model, one file, both
spellings kept as aliases; scripts/merge-research.js corrected so the
connector-less port cannot be regenerated.

Refs #130 (no close: nothing here names a UDW-PRO port or PoE wattage).
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 05:06:12 +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!2093
No description provided.