ubiquiti: give the UDW its published 420 W PoE budget and 10M speed cap (#130 follow-up) #1979

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

Refs #130 (does not close it - the Pro is still unpublished).

While re-checking the fallback this issue names, I found the fallback itself was wrong: #130's thread and docs/DEVICE_REGISTRY.md both describe devices/ubiquiti/udw.json as carrying "a 420 W budget", and it did not. The spec had 12 PSE ports and no poe.budgetW, so show power inline on a UDW prints

budget not modelled on UniFi Dream Wall-xxxx: the ports are reported, the power they could supply is not

What the vendor actually publishes

Read today, crawler UA, Ubiquiti-hosted only:

field value source
PoE Budget 420 W https://techspecs.ui.com/unifi/cloud-gateways/udw (200, 704,702 B, server-rendered)
Max. PoE wattage per port by PSE PoE 15.4 W / PoE+ 30 W / PoE++ 60 W same page, and dl.ui.com/ds/udw_ds.pdf §PoE interface
Max. Power Consumption 112 W excluding PoE output both
1 GbE RJ45 17 (4 PoE++; 4 PoE+; 4 PoE), 1G/100M/10M both
2.5 GbE RJ45 1 (2.5G/1G/100M) both
10G SFP+ 2 (10G/1G) both

The PDF text layer corroborates the port census verbatim - "(17) LAN: GbE RJ45 ports", "(1) WAN: 2.5 GbE RJ45 port", "(1) LAN: 10G SFP+ port", "(1) WAN: 10G SFP+ port", "(4) PoE ... (4) PoE+ ... (4) PoE++ ...", "Max. power consumption 532W" with the two 550 W PSUs - and the 420 W budget is on the spec page only, which is why the budget was missing.

What this changes

devices/ubiquiti/udw.json:

  • adds "poe": {"budgetW": 420, "sourceUrl": "https://techspecs.ui.com/unifi/cloud-gateways/udw"} - Device now resolves poeBudget = 420, poeBudgetSource = 'research', with 12 PSE ports;
  • adds 10M to the 17 GbE ports' speedCaps (1G/100M/10M is what the page prints; the spec said 1G/100M);
  • description now says "112 W max excluding PoE output; 420 W PoE budget", so the 112 W can no longer be read as a PSE budget - the same trap the E6608/9600 passes were opened for.

No port, class or budget is invented: the 12 PoE ports and their 4/4/4 split are the datasheet's, the 420 W is the spec page's, and nothing was inferred from the Pro (which still has no vendor page, datasheet, FCC grant or store listing).

Gates

  • node scripts/syntax-check.js - 414 files, OK
  • node scripts/audit-port-types.js - no port contradicts its declared type
  • node scripts/run-tests.js - 341 suites, 11,852 assertions, 0 failed (includes hardware-invariants, catalogue-hygiene, import-devices-capabilities)
  • node scripts/regen-registry-doc.js - registry current, 2,356 models, no doc change
  • import-devices capability tripwire: capabilities unchanged, none dropped
Refs #130 (does **not** close it - the Pro is still unpublished). While re-checking the fallback this issue names, I found the fallback itself was wrong: #130's thread and `docs/DEVICE_REGISTRY.md` both describe `devices/ubiquiti/udw.json` as carrying "a 420 W budget", and it did not. The spec had 12 PSE ports and no `poe.budgetW`, so `show power inline` on a UDW prints ``` budget not modelled on UniFi Dream Wall-xxxx: the ports are reported, the power they could supply is not ``` ## What the vendor actually publishes Read today, crawler UA, Ubiquiti-hosted only: | field | value | source | |--|--|--| | PoE Budget | **420 W** | <https://techspecs.ui.com/unifi/cloud-gateways/udw> (200, 704,702 B, server-rendered) | | Max. PoE wattage per port by PSE | PoE 15.4 W / PoE+ 30 W / PoE++ 60 W | same page, and `dl.ui.com/ds/udw_ds.pdf` §PoE interface | | Max. Power Consumption | **112 W** *excluding PoE output* | both | | 1 GbE RJ45 | 17 (4 PoE++; 4 PoE+; 4 PoE), **1G/100M/10M** | both | | 2.5 GbE RJ45 | 1 (2.5G/1G/100M) | both | | 10G SFP+ | 2 (10G/1G) | both | The PDF text layer corroborates the port census verbatim - "(17) LAN: GbE RJ45 ports", "(1) WAN: 2.5 GbE RJ45 port", "(1) LAN: 10G SFP+ port", "(1) WAN: 10G SFP+ port", "(4) PoE ... (4) PoE+ ... (4) PoE++ ...", "Max. power consumption 532W" with the two 550 W PSUs - and the 420 W budget is on the spec page only, which is why the budget was missing. ## What this changes `devices/ubiquiti/udw.json`: * adds `"poe": {"budgetW": 420, "sourceUrl": "https://techspecs.ui.com/unifi/cloud-gateways/udw"}` - `Device` now resolves `poeBudget = 420`, `poeBudgetSource = 'research'`, with 12 PSE ports; * adds `10M` to the 17 GbE ports' `speedCaps` (`1G/100M/10M` is what the page prints; the spec said `1G/100M`); * description now says "112 W max **excluding PoE output**; 420 W PoE budget", so the 112 W can no longer be read as a PSE budget - the same trap the E6608/9600 passes were opened for. No port, class or budget is invented: the 12 PoE ports and their 4/4/4 split are the datasheet's, the 420 W is the spec page's, and nothing was inferred from the Pro (which still has no vendor page, datasheet, FCC grant or store listing). ## Gates * `node scripts/syntax-check.js` - 414 files, OK * `node scripts/audit-port-types.js` - no port contradicts its declared type * `node scripts/run-tests.js` - 341 suites, 11,852 assertions, 0 failed (includes `hardware-invariants`, `catalogue-hygiene`, `import-devices-capabilities`) * `node scripts/regen-registry-doc.js` - registry current, 2,356 models, no doc change * import-devices capability tripwire: capabilities unchanged, none dropped
ubiquiti: give the UDW its published 420 W PoE budget and 10M speed cap
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
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 48s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 9s
0c51f2d8eb
The Dream Wall spec carried 12 PSE ports and no budget, so `show power inline`
answered 'budget not modelled' on a device Ubiquiti publishes a budget for.
techspecs.ui.com/unifi/cloud-gateways/udw states 'PoE Budget 420W' and
'Max. Power Consumption 112W (Excluding PoE output)' - the 112 W in the
description was the device draw, not the PSE budget. Also records the 1G RJ45
ports' 10M rate (the page prints 1G/100M/10M) and says 112 W excludes PoE.

Refs #130.
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!1979
No description provided.