devices(ubiquiti): five cloud gateways billed every PoE socket at 1 W #2407

Merged
jaylouisw merged 1 commit from catalogue/1121-1022 into main 2026-11-21 10:42:39 +00:00
Owner

Refs #130 — this PR does not close it. The Dream Wall Pro still has no vendor source: re-measured this minute, https://techspecs.ui.com/unifi/cloud-gateways/udw-pro -> 307, 1 byte, Location: / and https://store.ui.com/us/en/products/udw-pro -> 404. What it does is repair the gateway rows a lab would substitute for the box, where every PSE socket was billing 1 W.

The defect

UCG-Industrial, UDM-SE, UDR, UDR7 and UDR-5G-Max carried poeOut: true on the sockets that source power — the bare direction bit. Device.poeDraw() (engine/device.js) adds the field into its watt total, so true is 1 W, and pseDraw() (engine/validation.js) sums the same field against poe.budgetW. A 90 W 802.3bt device on UCG-Industrial eth0 was therefore accepted as a 1 W load and the 270 W budget could not bind anywhere; the faceplate's num() refuses a boolean, so the panel drew the badge with no figure.

Each socket now declares the vendor's own per-port ceiling for the class it already carried — the class-to-socket assignment is untouched, because neither surface numbers which sockets are which beyond the counts.

What Ubiquiti prints (all read 2026-11-21, server-rendered tech-spec tables)

model census per-port PSE ceiling budget source
UCG-Industrial 2.5 GbE RJ45 = 4 (2 PoE+++, 2 PoE+), 10 GbE RJ45 = 1 (PoE+++) PoE+ = 30W, PoE+++ = 90W DC input: 270W / ATX power: 75W techspecs ucg-industrial (200, 699,443 B)
UDM-SE (6) PoE + (2) PoE+ (datasheet) PoE = 15.4W, PoE+ = 30W 180W https://dl.ui.com/ds/udm_se_ds.pdf (200, 358,669 B, 3 pp, text layer) + techspecs udm-se (200, 682,320 B)
UDR 1 GbE RJ45 = 5 (2 PoE) PoE = 15.4W 40W techspecs udr (200, 685,837 B)
UDR7 2.5 GbE RJ45 = 4 (1 PoE) PoE = 15.4W 15.4W techspecs udr7 (200, 694,590 B)
UDR-5G-Max 2.5 GbE RJ45 = 4 (1 PoE) PoE = 15.4W 15.4W techspecs udr-5g-max (200, 876,426 B)

Arithmetic, stated rather than reconciled: UCG-Industrial's panel is 3 x 90 + 2 x 30 = 330 W against a 270 W budget, so the budget — not the socket sum — is what show power inline spends; UDM-SE is 152.4 W inside 180 W; UDR is 30.8 W inside 40 W, which is what its own budget note already said.

Files

  • devices/ubiquiti/{ucg-industrial,udm-se,udr,udr7,udr-5g-max}.json — the figure per PSE socket, plus the measurement in poe.note.
  • research/ubiquiti-cloud-gateway-poe-census.md — the table above, the two traps (udm-se_ds.pdf vs udm_se_ds.pdf; the page's doubled table), and the two rows this pass did not touch: /cloud-gateways/umr and /umr-industrial answer 307, so their poeOut: true stays until a page exists.
  • test/ubiquiti-gateway-pse-panel.test.js — 101 assertions, including cabling a powered device to the first PSE socket of each row and reading poeDraw().

Gates

node scripts/syntax-check.js -> 525 files, all OK; node scripts/audit-port-types.js -> 0 gated; node scripts/audit-devices.js -> 0 hard defects; test/hardware-invariants.test.js -> 26/26; node scripts/run-tests.js --filter=ubiquiti -> 7 suites, 591 assertions, 0 failed; --filter=poe -> 29 suites, 919 assertions, 0 failed. Capability lists are unchanged, so the importer tripwire has nothing to fire on.

Refs #130 — this PR does not close it. The Dream Wall **Pro** still has no vendor source: re-measured this minute, `https://techspecs.ui.com/unifi/cloud-gateways/udw-pro` -> **307, 1 byte, `Location: /`** and `https://store.ui.com/us/en/products/udw-pro` -> **404**. What it does is repair the gateway rows a lab would substitute for the box, where every PSE socket was billing 1 W. ## The defect `UCG-Industrial`, `UDM-SE`, `UDR`, `UDR7` and `UDR-5G-Max` carried `poeOut: true` on the sockets that source power — the bare direction bit. `Device.poeDraw()` (`engine/device.js`) adds the field into its watt total, so `true` is **1 W**, and `pseDraw()` (`engine/validation.js`) sums the same field against `poe.budgetW`. A 90 W 802.3bt device on UCG-Industrial eth0 was therefore accepted as a 1 W load and the 270 W budget could not bind anywhere; the faceplate's `num()` refuses a boolean, so the panel drew the badge with no figure. Each socket now declares the vendor's own per-port ceiling for the class it already carried — the class-to-socket assignment is untouched, because neither surface numbers which sockets are which beyond the counts. ## What Ubiquiti prints (all read 2026-11-21, server-rendered tech-spec tables) | model | census | per-port PSE ceiling | budget | source | |--|--|--|--|--| | UCG-Industrial | `2.5 GbE RJ45 = 4 (2 PoE+++, 2 PoE+)`, `10 GbE RJ45 = 1 (PoE+++)` | `PoE+ = 30W`, `PoE+++ = 90W` | `DC input: 270W / ATX power: 75W` | techspecs `ucg-industrial` (200, 699,443 B) | | UDM-SE | `(6) PoE` + `(2) PoE+` (datasheet) | `PoE = 15.4W`, `PoE+ = 30W` | `180W` | `https://dl.ui.com/ds/udm_se_ds.pdf` (200, 358,669 B, 3 pp, text layer) + techspecs `udm-se` (200, 682,320 B) | | UDR | `1 GbE RJ45 = 5 (2 PoE)` | `PoE = 15.4W` | `40W` | techspecs `udr` (200, 685,837 B) | | UDR7 | `2.5 GbE RJ45 = 4 (1 PoE)` | `PoE = 15.4W` | `15.4W` | techspecs `udr7` (200, 694,590 B) | | UDR-5G-Max | `2.5 GbE RJ45 = 4 (1 PoE)` | `PoE = 15.4W` | `15.4W` | techspecs `udr-5g-max` (200, 876,426 B) | Arithmetic, stated rather than reconciled: UCG-Industrial's panel is 3 x 90 + 2 x 30 = **330 W** against a 270 W budget, so the budget — not the socket sum — is what `show power inline` spends; UDM-SE is 152.4 W inside 180 W; UDR is 30.8 W inside 40 W, which is what its own budget note already said. ## Files - `devices/ubiquiti/{ucg-industrial,udm-se,udr,udr7,udr-5g-max}.json` — the figure per PSE socket, plus the measurement in `poe.note`. - `research/ubiquiti-cloud-gateway-poe-census.md` — the table above, the two traps (`udm-se_ds.pdf` vs `udm_se_ds.pdf`; the page's doubled table), and the two rows this pass did **not** touch: `/cloud-gateways/umr` and `/umr-industrial` answer **307**, so their `poeOut: true` stays until a page exists. - `test/ubiquiti-gateway-pse-panel.test.js` — 101 assertions, including cabling a powered device to the first PSE socket of each row and reading `poeDraw()`. ## Gates `node scripts/syntax-check.js` -> 525 files, all OK; `node scripts/audit-port-types.js` -> 0 gated; `node scripts/audit-devices.js` -> 0 hard defects; `test/hardware-invariants.test.js` -> 26/26; `node scripts/run-tests.js --filter=ubiquiti` -> 7 suites, 591 assertions, 0 failed; `--filter=poe` -> 29 suites, 919 assertions, 0 failed. Capability lists are unchanged, so the importer tripwire has nothing to fire on.
devices(ubiquiti): five gateways billed every PoE socket at 1 W (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke and Docker build (pull_request) Successful in 28s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 2s
d6e31a1aa7
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 10:29:04 +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!2407
No description provided.