ubiquiti: give the Pro XG 8 PoE the 155 W PoE budget its prose already claimed (refs #130) #2010

Merged
jaylouisw merged 1 commit from catalogue/1118-1726 into main 2026-11-18 18:08:35 +00:00
Owner

Refs #130 (does not close it - no UDW-PRO source exists; re-checked today: the cloud-gateway grid is 200 / 610,412 B with zero occurrences of udw-pro, and .../udw-pro still answers 307 to the site root).

What was wrong

devices/ubiquiti/usw-pro-xg-8-poe.json said "155 W PoE budget" in its own description and had no poe block. Device therefore fell through the field lookup to the model-name parser (mediaLib.parsePoeBudget), which finds nothing in USW-Pro-XG-8-PoE and yields 0 W:

Device('usw-pro-xg-8-poe').poeBudget   0    source 'name'

So the switch claimed eight PoE++ ports and a budget it could not tell the engine about - the mirror image of the PBE-5AC-Gen2 and the same defect as the UDW before #1877: the number was in the prose, not in the field the engine reads.

The source

https://techspecs.ui.com/unifi/switching/usw-pro-xg-8-poe - HTTP 200, 654,427 B, crawler UA, rendered spec table:

row value
Total PoE Availability 155W
PoE Ports 8, all PoE++
Max. PoE Wattage per Port by PSE PoE 15.4 W / PoE+ 30 W / PoE++ 60 W
Max. Power Consumption 61 W (excluding PoE output) / 210 W (including PoE output)
Power Supply AC/DC, external, 210 W

155 W is a published allocation, not arithmetic on the 210 W adapter - the 61 W device draw comes out of that adapter, and the two figures are what make 155 W the honest ceiling.

Change

poe: { budgetW: 155, sourceUrl, note }, note recording the per-port PSE ceilings and the consequence a lab will actually meet: eight PoE++ sinks at 60 W ask 480 W of a 155 W budget. Port census, speedCaps (10G/5G/2.5G/1G/100M on the eight RJ45, 10G/1G on the SFP+) and switching capacity (200 Gbps) were re-read against the same page and need no change.

Gates

  • Device('usw-pro-xg-8-poe').poeBudget -> 155, source research (was 0 / name)
  • scripts/audit-poe-budget.js - Ubiquiti silent PSEs 130 -> 129; PSEs that cannot be asked 130 -> 129
  • node scripts/syntax-check.js - 419 files OK
  • node scripts/audit-port-types.js - no port contradicts its declared type
  • node test/hardware-invariants.test.js - 26 passed, 0 failed
  • node test/poe.test.js - 18 passed, 0 failed
  • npm test - 345 suites, 11,982 assertions, 0 failed
  • npm run regen:registry-doc - catalogue pages already current
Refs #130 (does not close it - no UDW-PRO source exists; re-checked today: the cloud-gateway grid is 200 / 610,412 B with zero occurrences of `udw-pro`, and `.../udw-pro` still answers 307 to the site root). ## What was wrong `devices/ubiquiti/usw-pro-xg-8-poe.json` said **"155 W PoE budget"** in its own description and had **no `poe` block**. `Device` therefore fell through the field lookup to the model-name parser (`mediaLib.parsePoeBudget`), which finds nothing in `USW-Pro-XG-8-PoE` and yields **0 W**: ``` Device('usw-pro-xg-8-poe').poeBudget 0 source 'name' ``` So the switch claimed eight PoE++ ports and a budget it could not tell the engine about - the mirror image of the PBE-5AC-Gen2 and the same defect as the UDW before #1877: the number was in the prose, not in the field the engine reads. ## The source `https://techspecs.ui.com/unifi/switching/usw-pro-xg-8-poe` - HTTP 200, 654,427 B, crawler UA, rendered spec table: | row | value | |--|--| | Total PoE Availability | **155W** | | PoE Ports | 8, all PoE++ | | Max. PoE Wattage per Port by PSE | PoE 15.4 W / PoE+ 30 W / PoE++ 60 W | | Max. Power Consumption | 61 W (excluding PoE output) / 210 W (including PoE output) | | Power Supply | AC/DC, external, 210 W | 155 W is a published allocation, not arithmetic on the 210 W adapter - the 61 W device draw comes out of that adapter, and the two figures are what make 155 W the honest ceiling. ## Change `poe: { budgetW: 155, sourceUrl, note }`, note recording the per-port PSE ceilings and the consequence a lab will actually meet: eight PoE++ sinks at 60 W ask 480 W of a 155 W budget. Port census, `speedCaps` (10G/5G/2.5G/1G/100M on the eight RJ45, 10G/1G on the SFP+) and switching capacity (200 Gbps) were re-read against the same page and need no change. ## Gates - `Device('usw-pro-xg-8-poe').poeBudget` -> **155**, source `research` (was 0 / `name`) - `scripts/audit-poe-budget.js` - Ubiquiti silent PSEs 130 -> 129; PSEs that cannot be asked 130 -> 129 - `node scripts/syntax-check.js` - 419 files OK - `node scripts/audit-port-types.js` - no port contradicts its declared type - `node test/hardware-invariants.test.js` - 26 passed, 0 failed - `node test/poe.test.js` - 18 passed, 0 failed - `npm test` - **345 suites, 11,982 assertions, 0 failed** - `npm run regen:registry-doc` - catalogue pages already current
ubiquiti: give the Pro XG 8 PoE the 155 W budget its own text claimed (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 19s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 18s
d528e09af3
usw-pro-xg-8-poe.json said '155 W PoE budget' in its description and carried
no poe block, so Device fell through to the model-name parser, got nothing
from USW-Pro-XG-8-PoE, and reported 0 W to the engine. Same failure as the
UDW in #1877: the number was in the prose, not in the field the engine reads.

techspecs.ui.com/unifi/switching/usw-pro-xg-8-poe (200, 654,427 B, read
2026-11-18) states 'Total PoE Availability: 155W' - a fixed figure, not the
210 W adapter rating - with a per-port PSE ceiling of PoE 15.4 W / PoE+ 30 W
/ PoE++ 60 W and max power consumption 61 W excluding PoE output. Eight
PoE++ sinks at 60 W would ask 480 W of a 155 W budget, which is exactly the
refusal a lab should hit.

Verified: Device('usw-pro-xg-8-poe').poeBudget is 155 (source 'research'),
was 0 (source 'name'). audit-poe-budget drops the Ubiquiti silent count by
one; npm test 345 suites / 11,982 assertions / 0 failed.
forgejo-actions force-pushed catalogue/1118-1726 from d528e09af3
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 19s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 18s
to 314e88e9a7 2026-11-18 17:47:08 +00:00
Compare
forgejo-actions force-pushed catalogue/1118-1726 from 314e88e9a7 to bf6d4fe155
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
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 57s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 24s
2026-11-18 18:00:14 +00:00
Compare
jaylouisw deleted branch catalogue/1118-1726 2026-11-18 18:08:36 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!2010
No description provided.