devices(ubiquiti): four cloud-gateway rows carry the PoE budget the vendor prints #2101

Merged
jaylouisw merged 1 commit from catalogue/1119-0552 into main 2026-11-19 06:08:28 +00:00
Owner

Refs #130

The defect. A row that declares poe-pse and carries poeOut ports but no poe.budgetW is not a box with an unknown budget: engine/simulator.js opens with if (!dev.poeBudget) continue;, so the PSE is skipped, nothing on it can be powered, and show power inline has no allocation to report. Four UniFi cloud gateways were in that state while the vendor's own spec table printed a budget for each.

spec what the vendor prints ports as printed before
devices/ubiquiti/udr.json PoE Budget = 40W, PoE = 15.4W, 44-57V 1 GbE RJ45 = 5 (2 PoE) poe-pse, 2 poeOut, no budget
devices/ubiquiti/udr7.json PoE Budget = 15.4W, PoE = 15.4W, 44-57V 2.5 GbE RJ45 = 4 (1 PoE) poe-pse, 1 poeOut, no budget
devices/ubiquiti/udm-se.json PoE Budget = 180W, PoE = 15.4W, PoE+ = 30W (6) PoE + (2) PoE+ poe-pse, 8 poeOut, no budget, no sourceUrl at all
devices/ubiquiti/ucg-industrial.json PoE Budget = DC input: 270W / ATX power: 75W, PoE+ = 30W, PoE+++ = 90W 2 PoE+++, 2 PoE+, 1 PoE+++ poe-pse, 5 poeOut, no budget

Sources, read 2026-11-19 off each product's rendered spec table (__NEXT_DATA__ -> pageProps.product.technicalSpecification, i.e. the table on the page):

Two of them are cross-read against the datasheet text layer so the number does not rest on one surface: https://dl.ui.com/ds/udr_ds.pdf (200, 771,202 B, 3 pp) prints PoE budget 40W beside PoE interface (2) PoE (Pair B 4, 5+; 7, 8-) and Max. PoE wattage per port by PSE 15.4W; https://dl.ui.com/ds/udm_se_ds.pdf (200, 358,669 B, 3 pp) prints the PoE/PoE+ placement and per-port maxima but no aggregate, which is why the 180 W is cited to the spec table and the placement to the sheet. UCG-Industrial's 270 W is the DC-input ceiling with the ATX figure (75 W) in poe.note, the same convention as devices/allied-telesis/at-x530dp-28ghxm.json. No poe.perPortW is written: each PSE port already carries its poeOutClass, and a single number cannot describe a mixed box (UDM-SE is 6 x 15.4 W + 2 x 30 W).

Deliberately left alone. devices/ubiquiti/ucg-fiber.json prints PoE Budget = 30W on the same table and marks no port PoE in it; its document list holds only {"type":"InstallationGuide","url":"https://ui.com/qig/ucg-fiber"}, and dl.ui.com/ds/ucg-fiber.pdf, ucg-fiber_ds.pdf and ucgf_ds.pdf all 302 to the techspecs root. A budget with no PSE port is the condition scripts/audit-poe-budget.js refuses, and a poeOut port the vendor has not marked would be invented. The exact missing field - which of the five RJ45 ports sources PoE, at which class - is recorded in the research note.

research/ubiquiti-cloud-gateway-poe-budgets.md holds the full 17-row table and the two method traps (the Max. PoE Wattage per Port by PSE feature exists with no value on all five pages; product.datasheet is null even where a datasheet exists, so product.documents is the pointer).

Gates

  • node scripts/syntax-check.js - 442 files, all OK
  • node scripts/audit-port-types.js - No port contradicts its declared type.
  • node scripts/audit-poe-budget.js - 112 -> 108 of 402 PSEs cannot be asked how much they supply; Budget with no PSE port ... 0
  • node scripts/import-devices.js --dry-run - nothing written; its refusals are the pre-existing peplink/MAX-BR1-PRO-5G and zte/F8648P duplicates in research/incoming, not these rows
  • node scripts/run-tests.js - 363 suites, 12,397 assertions, 0 failed
  • npm run regen:registry-doc - catalogue pages current, no diff

On #130 itself: no Ubiquiti source names a UDW-PRO; the Pro surfaces were measured to exhaustion on earlier passes and were not re-walked here. This entry stays open.

Refs #130 **The defect.** A row that declares `poe-pse` and carries `poeOut` ports but no `poe.budgetW` is not a box with an unknown budget: `engine/simulator.js` opens with `if (!dev.poeBudget) continue;`, so the PSE is skipped, nothing on it can be powered, and `show power inline` has no allocation to report. Four UniFi cloud gateways were in that state while the vendor's own spec table printed a budget for each. | spec | what the vendor prints | ports as printed | before | |---|---|---|---| | `devices/ubiquiti/udr.json` | `PoE Budget = 40W`, `PoE = 15.4W`, `44-57V` | `1 GbE RJ45 = 5 (2 PoE)` | poe-pse, 2 `poeOut`, no budget | | `devices/ubiquiti/udr7.json` | `PoE Budget = 15.4W`, `PoE = 15.4W`, `44-57V` | `2.5 GbE RJ45 = 4 (1 PoE)` | poe-pse, 1 `poeOut`, no budget | | `devices/ubiquiti/udm-se.json` | `PoE Budget = 180W`, `PoE = 15.4W`, `PoE+ = 30W` | `(6) PoE` + `(2) PoE+` | poe-pse, 8 `poeOut`, no budget, **no `sourceUrl` at all** | | `devices/ubiquiti/ucg-industrial.json` | `PoE Budget = DC input: 270W / ATX power: 75W`, `PoE+ = 30W`, `PoE+++ = 90W` | `2 PoE+++, 2 PoE+`, `1 PoE+++` | poe-pse, 5 `poeOut`, no budget | Sources, read 2026-11-19 off each product's rendered spec table (`__NEXT_DATA__` -> `pageProps.product.technicalSpecification`, i.e. the table on the page): - <https://techspecs.ui.com/unifi/cloud-gateways/udr> (200, 685,730 B) - <https://techspecs.ui.com/unifi/cloud-gateways/udr7> (200, 694,473 B) - <https://techspecs.ui.com/unifi/cloud-gateways/udm-se> (200, 682,201 B) - <https://techspecs.ui.com/unifi/cloud-gateways/ucg-industrial> (200, 699,330 B) Two of them are cross-read against the datasheet text layer so the number does not rest on one surface: <https://dl.ui.com/ds/udr_ds.pdf> (200, 771,202 B, 3 pp) prints `PoE budget 40W` beside `PoE interface (2) PoE (Pair B 4, 5+; 7, 8-)` and `Max. PoE wattage per port by PSE 15.4W`; <https://dl.ui.com/ds/udm_se_ds.pdf> (200, 358,669 B, 3 pp) prints the PoE/PoE+ placement and per-port maxima but **no aggregate**, which is why the 180 W is cited to the spec table and the placement to the sheet. UCG-Industrial's 270 W is the DC-input ceiling with the ATX figure (75 W) in `poe.note`, the same convention as `devices/allied-telesis/at-x530dp-28ghxm.json`. No `poe.perPortW` is written: each PSE port already carries its `poeOutClass`, and a single number cannot describe a mixed box (UDM-SE is 6 x 15.4 W + 2 x 30 W). **Deliberately left alone.** `devices/ubiquiti/ucg-fiber.json` prints `PoE Budget = 30W` on the same table and marks no port PoE in it; its document list holds only `{"type":"InstallationGuide","url":"https://ui.com/qig/ucg-fiber"}`, and `dl.ui.com/ds/ucg-fiber.pdf`, `ucg-fiber_ds.pdf` and `ucgf_ds.pdf` all 302 to the techspecs root. A budget with no PSE port is the condition `scripts/audit-poe-budget.js` refuses, and a `poeOut` port the vendor has not marked would be invented. The exact missing field - which of the five RJ45 ports sources PoE, at which class - is recorded in the research note. `research/ubiquiti-cloud-gateway-poe-budgets.md` holds the full 17-row table and the two method traps (the `Max. PoE Wattage per Port by PSE` feature exists with no value on all five pages; `product.datasheet` is `null` even where a datasheet exists, so `product.documents` is the pointer). **Gates** - `node scripts/syntax-check.js` - 442 files, all OK - `node scripts/audit-port-types.js` - `No port contradicts its declared type.` - `node scripts/audit-poe-budget.js` - 112 -> **108** of 402 PSEs cannot be asked how much they supply; `Budget with no PSE port ... 0` - `node scripts/import-devices.js --dry-run` - nothing written; its refusals are the pre-existing `peplink/MAX-BR1-PRO-5G` and `zte/F8648P` duplicates in `research/incoming`, not these rows - `node scripts/run-tests.js` - 363 suites, 12,397 assertions, 0 failed - `npm run regen:registry-doc` - catalogue pages current, no diff **On #130 itself:** no Ubiquiti source names a UDW-PRO; the Pro surfaces were measured to exhaustion on earlier passes and were not re-walked here. This entry stays open.
devices(ubiquiti): four cloud-gateway rows carry the PoE budget the vendor prints
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 3s
8f8c1be4c7
The UDR (40 W), UDR7 (15.4 W), UDM-SE (180 W) and UCG-Industrial (270 W on DC input)
each declared poe-pse and poeOut ports with no poe.budgetW. The allocator skips a PSE
whose budget is 0, so none of them could power anything. UDM-SE also had no sourceUrl
at all, so no field in the row was traceable.

UCG-Fiber's 30 W is left alone: the vendor prints a budget on that page and marks no
port PoE in the same table, and it has no datasheet.

research/ubiquiti-cloud-gateway-poe-budgets.md records what each product's rendered
spec table prints, and the datasheet text layers for the UDR and UDM-SE.

Refs #130
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 06:06:23 +00:00
jaylouisw deleted branch catalogue/1119-0552 2026-11-19 06:08:30 +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!2101
No description provided.