devices(ubiquiti): the USW-Ultra chassis charges 30 W a port, not 1 W #2417

Merged
jaylouisw merged 1 commit from catalogue/1121-1152 into main 2026-11-21 12:07:57 +00:00
Owner

Refs #130 only - this does not answer the Dream Wall Pro request (the SKU still has no Ubiquiti surface: techspecs.ui.com/unifi/cloud-gateways/udw-pro answers 200 with the 609,911-byte home page, store.ui.com/us/en/products/udw-pro 404, both re-read 2026-11-21 11:5x UTC).

The defect. All three power configurations of the USW-Ultra chassis carried poeOut: true on their seven PoE+ sockets - the bare direction bit, which Device.poeDraw() (engine/device.js) adds as 1 W and pseDraw() (engine/validation.js) sums against the budget. So the 42 W budget could not bind: two 25.5 W access points on eth0/eth1 were both accepted by the cabling guard (2 powered ports draw 2 W of a 42 W budget would have been the arithmetic it never reached), and poeDraw() answered 2 W for 51 W of real load.

What made this one settleable: the vendor prints the per-port ceiling on the same page as the budget, and the spec's own description already said "7 PoE+ PSE ports (30 W/port)" - prose and field disagreed.

model budget page bytes
USW-Ultra 42 W (PoE++ input) https://techspecs.ui.com/unifi/switching/usw-ultra 628,685
USW-Ultra-60W 52 W (60 W adapter) https://techspecs.ui.com/unifi/switching/usw-ultra-60w 628,751
USW-Ultra-210W 202 W (210 W adapter) https://techspecs.ui.com/unifi/switching/usw-ultra-210w 628,783

All three print the same panel: Port Layout 1 GbE RJ45 8 (7 PoE+; 1 PoE++ input), Max. PoE Output Up to PoE+, PoE Ports PoE+ 7, Max. PoE Wattage per Port by PSE PoE+ 30W. eth7 is the PoE++ INPUT that powers the switch and continues to source nothing (poeOut: 0, poeIn: 9).

After. eth0-eth6 declare 30 W in devices/ubiquiti/usw-ultra.json, usw-ultra-60w.json and usw-ultra-210w.json; each poe.note records the vendor row. poeDraw() on one cabled port answers 30 W, the 42 W model refuses the second 25.5 W access point (2 powered ports draw 60 W of a 42 W budget), the 60 W model likewise, and the 210 W model feeds six and refuses the seventh (210 W of a 202 W budget).

Gates. node scripts/syntax-check.js - 531 files, all OK. node scripts/audit-port-types.js - 0 contradicted ports. node scripts/audit-poe-budget.js - unchanged, 0 inferred, 0 orphaned. node scripts/regen-registry-doc.js - no doc change (socket count unchanged). node scripts/run-tests.js --filter=invariant 26 passed; --filter=catalogue 66 passed. New suite test/usw-ultra-poe.test.js: 28 passed, 0 failed.

Refs #130 only - this does not answer the Dream Wall Pro request (the SKU still has no Ubiquiti surface: `techspecs.ui.com/unifi/cloud-gateways/udw-pro` answers 200 with the 609,911-byte home page, `store.ui.com/us/en/products/udw-pro` 404, both re-read 2026-11-21 11:5x UTC). **The defect.** All three power configurations of the USW-Ultra chassis carried `poeOut: true` on their seven PoE+ sockets - the bare direction bit, which `Device.poeDraw()` (`engine/device.js`) adds as **1 W** and `pseDraw()` (`engine/validation.js`) sums against the budget. So the 42 W budget could not bind: two 25.5 W access points on eth0/eth1 were both accepted by the cabling guard (`2 powered ports draw 2 W of a 42 W budget` would have been the arithmetic it never reached), and `poeDraw()` answered 2 W for 51 W of real load. What made this one settleable: the vendor prints the per-port ceiling on the same page as the budget, and the spec's own description already said "7 PoE+ PSE ports (30 W/port)" - prose and field disagreed. | model | budget | page | bytes | |--|--|--|--| | USW-Ultra | 42 W (PoE++ input) | https://techspecs.ui.com/unifi/switching/usw-ultra | 628,685 | | USW-Ultra-60W | 52 W (60 W adapter) | https://techspecs.ui.com/unifi/switching/usw-ultra-60w | 628,751 | | USW-Ultra-210W | 202 W (210 W adapter) | https://techspecs.ui.com/unifi/switching/usw-ultra-210w | 628,783 | All three print the same panel: `Port Layout 1 GbE RJ45 8 (7 PoE+; 1 PoE++ input)`, `Max. PoE Output Up to PoE+`, `PoE Ports PoE+ 7`, `Max. PoE Wattage per Port by PSE PoE+ 30W`. eth7 is the PoE++ INPUT that powers the switch and continues to source nothing (`poeOut: 0`, `poeIn: 9`). **After.** eth0-eth6 declare 30 W in `devices/ubiquiti/usw-ultra.json`, `usw-ultra-60w.json` and `usw-ultra-210w.json`; each `poe.note` records the vendor row. `poeDraw()` on one cabled port answers 30 W, the 42 W model refuses the second 25.5 W access point (`2 powered ports draw 60 W of a 42 W budget`), the 60 W model likewise, and the 210 W model feeds six and refuses the seventh (`210 W of a 202 W budget`). **Gates.** `node scripts/syntax-check.js` - 531 files, all OK. `node scripts/audit-port-types.js` - 0 contradicted ports. `node scripts/audit-poe-budget.js` - unchanged, 0 inferred, 0 orphaned. `node scripts/regen-registry-doc.js` - no doc change (socket count unchanged). `node scripts/run-tests.js --filter=invariant` 26 passed; `--filter=catalogue` 66 passed. New suite `test/usw-ultra-poe.test.js`: 28 passed, 0 failed.
devices(ubiquiti): the USW-Ultra chassis charges 30 W a port, not 1 W
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 26s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Test (Node 20) (pull_request) Successful in 1m2s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 3s
36de4e799d
All three power configurations of the chassis (USW-Ultra 42 W, USW-Ultra-60W
52 W, USW-Ultra-210W 202 W) carried `poeOut: true` on their seven PoE+ sockets,
the bare direction bit that Device.poeDraw() adds as 1 W and that pseDraw()
sums against the budget, so the 42 W budget could not bind: two 25.5 W access
points on eth0/eth1 were both accepted (2 W of 42 W).

techspecs for each SKU, read 2026-11-21, print 'PoE Ports PoE+ 7' and
'Max. PoE Wattage per Port by PSE PoE+ 30W' beside 'Max. PoE Output Up to
PoE+'; eth7 stays the PoE++ input the switch runs from. Each socket now
declares 30 W, which is what the spec's own description already claimed.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 11:57:03 +00:00
jaylouisw deleted branch catalogue/1121-1152 2026-11-21 12:07:58 +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!2417
No description provided.