devices(ubiquiti): the Dream Wall billed all twelve PoE sockets as 1 W (refs #130) #2404

Merged
jaylouisw merged 1 commit from catalogue/1121-0952 into main 2026-11-21 10:12:09 +00:00
Owner

Refs #130 (no closing keyword: the request is for UDW-PRO, and Ubiquiti still publishes no page for that SKU - see the blocker below).

UDW-PRO remains unbuildable, re-measured this minute: https://techspecs.ui.com/unifi/cloud-gateways/udw-pro -> 307, 1 byte, Location: /; https://store.ui.com/us/en/products/udw-pro -> 404, 1 byte. Nothing has appeared since the 09:2x pass.

The defect this pass fixed is on the Dream Wall that does exist - the only chassis a lab can substitute, and the one whose panel the request's port list would have to come from. All twelve powered sockets carried the bare direction bit poeOut: true:

surface reading
engine/device.js poeDraw() adds iface.poeOut per cabled socket, so true is 1 W
engine/validation.js pseDraw() sums the same field against the budget, so a 420 W PSE never shows load
web/faceplate.js num() refuses a boolean, so no socket printed a PoE out figure

Measured before: two 25.5 W U7-Pros on eth0/eth4 made poeDraw() answer 2 W. A chassis rated 4x PoE++ / 4x PoE+ / 4x PoE could not account for a single 30 W AP.

Vendor figures, both surfaces read 2026-11-21:

  • https://techspecs.ui.com/unifi/cloud-gateways/udw (200, 704,702 B, server-rendered table): PoE Budget 420W; Max. PoE Wattage per Port by PSE PoE: 15.4W / PoE+: 30W / PoE++: 60W; Voltage Range PoE Mode PoE: 44-57V / PoE+/PoE++: 50-57V
  • https://dl.ui.com/ds/udw_ds.pdf (200, 544,909 B, 3 pp, text layer): PoE interface (4) PoE ... (4) PoE+ ... (4) PoE++ ...; the same three Max. PoE wattage per port by PSE rows

Each socket now declares the ceiling of the class it already carried - eth0-3 60 W PoE++, eth4-7 30 W PoE+, eth8-eth11 15.4 W PoE. The class-to-socket ordering is untouched: neither surface numbers which four sockets are which, so this pass replaced the figure, not the assignment. The panel's four-of-each sums to 421.6 W against the published 420 W budget; that arithmetic is the vendor's and is stated in the spec's notes rather than reconciled.

Gates: syntax-check 524 files OK; audit-port-types 0 gated contradictions; import-devices --dry-run clean for this spec (its only warnings are pre-existing mikrotik cAP ax capability tokens); hardware-invariants 26/26; full suite 444 suites, 14975 assertions, 0 failed; regen-registry-doc reports the pages current. New regression: test/ubiquiti-dream-wall-poe.test.js (16 assertions) - asserts the three class ceilings, four sockets each, no cage sourcing power, poeDraw() summing 90 W for the two cabled ceilings, and computePoe() spending 51 W of 420.

Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class split and budget, PSU configuration - because Ubiquiti publishes no page for that SKU on any surface that has ever carried it: not in the techspecs cloud-gateway grid, not in the US/EU/UK storefronts, no FCC grant under SWX, no archived capture, and udw-pro occurs zero times in ~610 KB. Unblock: Ubiquiti listing the Pro, or its quick-start guide printing a port layout.

Refs #130 (no closing keyword: the request is for UDW-PRO, and Ubiquiti still publishes no page for that SKU - see the blocker below). **UDW-PRO remains unbuildable, re-measured this minute:** `https://techspecs.ui.com/unifi/cloud-gateways/udw-pro` -> `307`, 1 byte, `Location: /`; `https://store.ui.com/us/en/products/udw-pro` -> `404`, 1 byte. Nothing has appeared since the 09:2x pass. **The defect this pass fixed is on the Dream Wall that does exist** - the only chassis a lab can substitute, and the one whose panel the request's port list would have to come from. All twelve powered sockets carried the bare direction bit `poeOut: true`: | surface | reading | |---|---| | engine/device.js `poeDraw()` | adds `iface.poeOut` per cabled socket, so `true` is **1 W** | | engine/validation.js `pseDraw()` | sums the same field against the budget, so a 420 W PSE never shows load | | web/faceplate.js `num()` | refuses a boolean, so no socket printed a `PoE out` figure | Measured before: two 25.5 W U7-Pros on eth0/eth4 made `poeDraw()` answer **2 W**. A chassis rated 4x PoE++ / 4x PoE+ / 4x PoE could not account for a single 30 W AP. **Vendor figures, both surfaces read 2026-11-21:** - `https://techspecs.ui.com/unifi/cloud-gateways/udw` (200, 704,702 B, server-rendered table): `PoE Budget 420W`; `Max. PoE Wattage per Port by PSE PoE: 15.4W / PoE+: 30W / PoE++: 60W`; `Voltage Range PoE Mode PoE: 44-57V / PoE+/PoE++: 50-57V` - `https://dl.ui.com/ds/udw_ds.pdf` (200, 544,909 B, 3 pp, text layer): `PoE interface (4) PoE ... (4) PoE+ ... (4) PoE++ ...`; the same three `Max. PoE wattage per port by PSE` rows Each socket now declares the ceiling of the class it already carried - eth0-3 60 W PoE++, eth4-7 30 W PoE+, eth8-eth11 15.4 W PoE. **The class-to-socket ordering is untouched:** neither surface numbers which four sockets are which, so this pass replaced the figure, not the assignment. The panel's four-of-each sums to 421.6 W against the published 420 W budget; that arithmetic is the vendor's and is stated in the spec's notes rather than reconciled. **Gates:** `syntax-check` 524 files OK; `audit-port-types` 0 gated contradictions; `import-devices --dry-run` clean for this spec (its only warnings are pre-existing mikrotik cAP ax capability tokens); `hardware-invariants` 26/26; full suite `444 suites, 14975 assertions, 0 failed`; `regen-registry-doc` reports the pages current. New regression: `test/ubiquiti-dream-wall-poe.test.js` (16 assertions) - asserts the three class ceilings, four sockets each, no cage sourcing power, `poeDraw()` summing 90 W for the two cabled ceilings, and `computePoe()` spending 51 W of 420. **Blocker, unchanged and precise:** the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class split and budget, PSU configuration - because Ubiquiti publishes no page for that SKU on any surface that has ever carried it: not in the techspecs cloud-gateway grid, not in the US/EU/UK storefronts, no FCC grant under `SWX`, no archived capture, and `udw-pro` occurs zero times in ~610 KB. Unblock: Ubiquiti listing the Pro, or its quick-start guide printing a port layout.
devices(ubiquiti): the Dream Wall billed all twelve PoE sockets as 1 W (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
CI / Server smoke and Docker build (pull_request) Successful in 42s
CI / Test (Node 18) (pull_request) Successful in 54s
CI / Test (Node 20) (pull_request) Successful in 55s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 2s
d8c8e48061
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 10:01:18 +00:00
jaylouisw deleted branch catalogue/1121-0952 2026-11-21 10:12:11 +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!2404
No description provided.