devices(ubiquiti): the UXG-Pro row cites its own datasheet and stops drawing phantom PoE (refs #130) #2118

Merged
jaylouisw merged 2 commits from catalogue/1119-0752 into main 2026-11-19 08:12:52 +00:00
Owner

refs #130 - still blocked on the Pro itself; no UDW-PRO source was found, so #130 stays open.

The row a Dream-series requester is handed instead is devices/ubiquiti/uxg-pro.json, and it had no sourceUrl at all: its four ports came from a sentence in notes that named no URL. Verifying it turned up the vendor datasheet that nobody had cited, and the census it prints is exactly the row already modelled:

  • https://dl.ui.com/ds/uxg-pro_ds.pdf - HTTP 200, application/pdf, 433,832 B, two pages, text layer read: Networking interface - LAN: (1) 1 GbE RJ45 port / (1) 10G SFP+ port; WAN: (1) 1 GbE RJ45 port / (1) 10G SFP+ port. Also Power supply AC/DC internal 50W, Max. power consumption 30W, RPS DC input 11.5V DC 2.87A.
  • https://techspecs.ui.com/unifi/cloud-gateways/uxg-pro - 200, 649,578 B: Max. WAN Port Count 3, Default WAN Ports (1) 10G SFP+ / (1) GbE RJ45, Port Layout 10G SFP+ = 2 (10G/1G), IDS/IPS 3.5 Gbps, 1U. Its Port Layout group enumerates only the cages, so it is not cited for the copper count.
  • https://store.ui.com/us/en/products/uxg-pro - 200, 504,342 B, displaySku UXG-Pro: "(1) 10G SFP+* and (1) GbE WAN port" / "(1) 10G SFP+* and (1) GbE LAN port", and PoE Budget, the four per-port PSE wattages and Voltage Range PoE Mode all Empty.

So: sourceUrl added, notes rewritten to cite all three, and the two copper ports now carry poeIn: false. Without it isPoePd() in engine/media.js matches unifi and infers 12.95 W of draw per copper socket - 25.9 W a lab would spend against a switch budget on a box with a 50 W internal AC supply and no published PoE input. Same correction as udm-pro-max.json (#2111). research/incoming/devices-ubnt-gateways.json carries the same fix, and an importer round-trip preserves sourceUrl, notes, poeIn and every capability.

Two traps recorded: dl.ui.com/ds/uxg_pro_ds.pdf answers 302 to techspecs.ui.com/ (288 B), so the datasheet key is hyphenated per SKU; techspecs.ui.com/unifi/cloud-gateways/uxg answers 307 with 1 byte.

Gates: scripts/syntax-check.js 445 files OK; scripts/audit-port-types.js no contradiction (exit 0); import-devices.js --dry-run same verdict as main (exit 1 from two pre-existing peplink/zte duplicate rejects, untouched here); hardware-invariants 26/26, catalogue-hygiene 25/25, spec-survives-load 32/32, spec-vs-description 3/3, doc-catalog-counts 43/43, poe 18/18; regen:registry-doc reports the catalogue unchanged at 2,356 models.

refs #130 - still blocked on the Pro itself; no UDW-PRO source was found, so #130 stays open. The row a Dream-series requester is handed instead is `devices/ubiquiti/uxg-pro.json`, and it had **no `sourceUrl` at all**: its four ports came from a sentence in `notes` that named no URL. Verifying it turned up the vendor datasheet that nobody had cited, and the census it prints is exactly the row already modelled: - `https://dl.ui.com/ds/uxg-pro_ds.pdf` - HTTP 200, `application/pdf`, 433,832 B, two pages, text layer read: **Networking interface - LAN: (1) 1 GbE RJ45 port / (1) 10G SFP+ port; WAN: (1) 1 GbE RJ45 port / (1) 10G SFP+ port**. Also Power supply AC/DC internal 50W, Max. power consumption 30W, RPS DC input 11.5V DC 2.87A. - `https://techspecs.ui.com/unifi/cloud-gateways/uxg-pro` - 200, 649,578 B: Max. WAN Port Count 3, Default WAN Ports (1) 10G SFP+ / (1) GbE RJ45, Port Layout 10G SFP+ = 2 (10G/1G), IDS/IPS 3.5 Gbps, 1U. Its Port Layout group enumerates **only** the cages, so it is not cited for the copper count. - `https://store.ui.com/us/en/products/uxg-pro` - 200, 504,342 B, `displaySku` `UXG-Pro`: "(1) 10G SFP+* and (1) GbE WAN port" / "(1) 10G SFP+* and (1) GbE LAN port", and PoE Budget, the four per-port PSE wattages and Voltage Range PoE Mode all Empty. So: `sourceUrl` added, `notes` rewritten to cite all three, and the two copper ports now carry `poeIn: false`. Without it `isPoePd()` in `engine/media.js` matches `unifi` and infers 12.95 W of draw per copper socket - 25.9 W a lab would spend against a switch budget on a box with a 50 W internal AC supply and no published PoE input. Same correction as `udm-pro-max.json` (#2111). `research/incoming/devices-ubnt-gateways.json` carries the same fix, and an importer round-trip preserves `sourceUrl`, `notes`, `poeIn` and every capability. Two traps recorded: `dl.ui.com/ds/uxg_pro_ds.pdf` answers 302 to `techspecs.ui.com/` (288 B), so the datasheet key is hyphenated per SKU; `techspecs.ui.com/unifi/cloud-gateways/uxg` answers 307 with 1 byte. Gates: `scripts/syntax-check.js` 445 files OK; `scripts/audit-port-types.js` no contradiction (exit 0); `import-devices.js --dry-run` same verdict as main (exit 1 from two pre-existing peplink/zte duplicate rejects, untouched here); `hardware-invariants` 26/26, `catalogue-hygiene` 25/25, `spec-survives-load` 32/32, `spec-vs-description` 3/3, `doc-catalog-counts` 43/43, `poe` 18/18; `regen:registry-doc` reports the catalogue unchanged at 2,356 models.
devices(ubiquiti): the UXG-Pro row cites its own datasheet and stops drawing phantom PoE (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 8s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Arm auto-merge (pull_request) Successful in 3s
ea2afeea53
The row carried no sourceUrl at all: its four ports traced to a sentence in
notes with no URL. They now trace to dl.ui.com/ds/uxg-pro_ds.pdf (200,
433,832 B, two pages, text layer read), whose Networking interface line is
LAN: (1) 1 GbE RJ45 + (1) 10G SFP+ / WAN: (1) 1 GbE RJ45 + (1) 10G SFP+ -
the same four sockets, two of them cages.

The tech-spec page's Port Layout group enumerates only the two 10G cages, so
it is cited for Max. WAN Port Count 3, 10G SFP+ = 2 (10G/1G), 3.5 Gbps
IDS/IPS and 1U, not for the copper count.

No PoE on this box: the datasheet lists no PoE port or budget, and the store
table carries PoE Budget, the four per-port PSE wattages and Voltage Range
PoE Mode all Empty. The two copper ports now say poeIn:false, because
isPoePd() matches 'unifi' and was inferring 12.95 W of draw on each - 25.9 W
against a switch budget for a box powered by a 50 W internal AC/DC supply.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 07:58:33 +00:00
research: record the UniFi Design Center as read and empty for 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 8s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 3s
e12063874f
design.ui.com answers 200 with the same 8,107-byte SPA shell for every
path tried, and its loader/Main chunks name no model endpoint, so the device
library behind it is not reachable anonymously and its silence is not a
negative. DEVICE_REGISTRY.md regenerated.
jaylouisw deleted branch catalogue/1119-0752 2026-11-19 08:12:53 +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!2118
No description provided.