devices(ubiquiti): the Pro XG 48 PoE declared 48 PoE+++ ports and no PoE budget (refs #130) #2235

Merged
jaylouisw merged 1 commit from catalogue/1120-0052 into main 2026-11-20 01:09:46 +00:00
Owner

Refs #130 (the UDW-PRO request stays blocked: this PR does not answer it, and is deliberately not worded as a closer - see the comment on the issue).

The Pro XG 48 PoE declared 48 PoE+++ ports and no budget, so the loader fell through to the model-name parser: poeBudget 0 W, poeBudgetSource "name". A 48-port PoE+++ switch that could light nothing, beside a description already claiming a 1080 W budget.

before after
poeBudget 0 W 1080 W
poeBudgetSource name research
ports / PSE ports 52 / 48 52 / 48 (unchanged)

Source (read this pass, one page): https://techspecs.ui.com/unifi/switching/usw-pro-xg-48-poe - HTTP 200, 663,473 B.

  • Port layout: 2.5 GbE RJ45 16 (All PoE+++), 10 GbE RJ45 32 (All PoE+++), 25G SFP28 4 - 52 sockets, matching the spec unchanged.
  • Total PoE Availability 200-240V AC: 1080W / 100-120V AC: 972W.
  • Max. PoE Wattage per Port by PSE: PoE 15.4W / PoE+ 30W / PoE++ 60W / PoE+++ 90W.
  • Switching Capacity 920 Gbps, Total Non-Blocking Throughput 460 Gbps - the description already said 920 and is confirmed, not changed.

1,080 W is modelled because it is the figure the vendor prints first and the one this spec quotes; the 100-120 V ceiling is recorded in poe.note rather than dropped, the way ecs-24-poe.json records a supply-dependent budget. No port, rate, class or capability changed.

Changes:

  • devices/ubiquiti/usw-pro-xg-48-poe.json: poe.budgetW + poe.sourceUrl + poe.note.

Gates: node scripts/syntax-check.js (474 files, all OK); node scripts/audit-port-types.js (2,355 models, 29,724 ports, 0 offending); node test/hardware-invariants.test.js (26 passed, 0 failed); node test/spec-vs-description.test.js (3 passed); node test/poe.test.js (21 passed); node test/request-queue.test.js (32 passed); node scripts/check-doc-citations.js (clean); scripts/regen-registry-doc.js (no change - the registry does not carry budgets).

Refs #130 (the UDW-PRO request stays blocked: this PR does not answer it, and is deliberately not worded as a closer - see the comment on the issue). The Pro XG 48 PoE declared 48 PoE+++ ports and no budget, so the loader fell through to the model-name parser: `poeBudget` 0 W, `poeBudgetSource` "name". A 48-port PoE+++ switch that could light nothing, beside a description already claiming a 1080 W budget. | | before | after | |--|--|--| | `poeBudget` | 0 W | 1080 W | | `poeBudgetSource` | `name` | `research` | | ports / PSE ports | 52 / 48 | 52 / 48 (unchanged) | **Source (read this pass, one page):** `https://techspecs.ui.com/unifi/switching/usw-pro-xg-48-poe` - HTTP 200, 663,473 B. - Port layout: `2.5 GbE RJ45 16 (All PoE+++)`, `10 GbE RJ45 32 (All PoE+++)`, `25G SFP28 4` - 52 sockets, matching the spec unchanged. - `Total PoE Availability 200-240V AC: 1080W / 100-120V AC: 972W`. - `Max. PoE Wattage per Port by PSE: PoE 15.4W / PoE+ 30W / PoE++ 60W / PoE+++ 90W`. - `Switching Capacity 920 Gbps`, `Total Non-Blocking Throughput 460 Gbps` - the description already said 920 and is confirmed, not changed. 1,080 W is modelled because it is the figure the vendor prints first and the one this spec quotes; the 100-120 V ceiling is recorded in `poe.note` rather than dropped, the way `ecs-24-poe.json` records a supply-dependent budget. No port, rate, class or capability changed. Changes: - `devices/ubiquiti/usw-pro-xg-48-poe.json`: `poe.budgetW` + `poe.sourceUrl` + `poe.note`. Gates: `node scripts/syntax-check.js` (474 files, all OK); `node scripts/audit-port-types.js` (2,355 models, 29,724 ports, 0 offending); `node test/hardware-invariants.test.js` (26 passed, 0 failed); `node test/spec-vs-description.test.js` (3 passed); `node test/poe.test.js` (21 passed); `node test/request-queue.test.js` (32 passed); `node scripts/check-doc-citations.js` (clean); `scripts/regen-registry-doc.js` (no change - the registry does not carry budgets).
devices(ubiquiti): the Pro XG 48 PoE declared 48 PSE ports and no budget (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke and Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Test (Node 20) (pull_request) Successful in 1m3s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 4s
3895e237f1
The spec carried `poeOut: true` on all 48 copper ports and no `poe.budgetW`,
so the loader fell through to the model-name parser, which reads no wattage out
of "USW-Pro-XG-48-PoE": budget 0 W, budgetSource "name". Forty-eight PoE+++
ports that could light nothing, while the description beside them claimed a
1080 W budget.

Ubiquiti publishes the split the description had already taken the top half of:
Total PoE Availability 200-240 V AC: 1,080 W / 100-120 V AC: 972 W. The 1,080 W
figure is modelled (the one the vendor lists first and the one the description
quotes) and the 100-120 V ceiling is recorded in `poe.note`, following
ecs-24-poe.json, which notes a budget that depends on supply instead of picking
one silently.

Sources, both read this pass:
- https://techspecs.ui.com/unifi/switching/usw-pro-xg-48-poe (HTTP 200, 663,473 B)
  "Port Layout 2.5 GbE RJ45 16 (All PoE+++) ... 10 GbE RJ45 32 (All PoE+++) ...
   25G SFP28 4", "Total PoE Availability 200-240V AC: 1080W 100-120V AC: 972W",
  "Max. PoE Wattage per Port by PSE: PoE 15.4W / PoE+ 30W / PoE++ 60W / PoE+++ 90W",
  "Switching Capacity 920 Gbps", "Total Non-Blocking Throughput 460 Gbps".

No port, rate or class changed; only the budget the ports needed.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 00:59:03 +00:00
jaylouisw deleted branch catalogue/1120-0052 2026-11-20 01:09:48 +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!2235
No description provided.