devices(ubiquiti): the ES-5XP billed 1 W a port and a phantom 802.3af PSE on its management socket (#130) #2438

Merged
jaylouisw merged 1 commit from catalogue/1121-1452 into main 2026-11-21 15:08:37 +00:00
Owner

Refs #130 (does not close it — the UDW-PRO is still absent from Ubiquiti's catalogue; see below).

What this fixes

devices/ubiquiti/es-5xp.json advertised five PoE ports and could not say a single watt
about any of them, and it advertised a sixth that does not exist.

before vendor after
five data ports bare poeOut: true → poeDraw() 1 W each, faceplate prints nothing "Max. PoE Wattage Per Data Port 11.5 W", "PoE Method Passive" poeOut: 11.5, poeOutClass: "passive"
mgmt no poeOut key → media.js infers a 15.4 W 802.3af PSE on a poe-pse device "PoE Configurable Per Port: Management Port N/A" poeOut: false
poe block absent → parsePoeBudget('ES-5XP') = 0, show power inline says "budget not modelled" "Max. Power Consumption 60 W" on a 24 V / 2.5 A adapter budgetW: 60, cited, with the silence in the note
capabilities no passive-poe PoE method Passive passive-poe (descriptive token, as in es-16xp.json)

Measured before: six PSE ports on a five-port PoE switch — eth0..eth4 at poeOut: true
(1 W each) and mgmt at 15.4 W — and show power inline printed six rows of
not measured under "budget not modelled on EdgeSwitch 5 XP-sw1".

Sources (Ubiquiti-hosted, read 2026-11-21)

  • https://dl.ui.com/datasheets/edgemax/EdgeSwitch_XP_DS.pdf — HTTP 200, application/pdf,
    3,915,117 B, 7 pp, text layer. p.5 is the ES-5XP page: Data Ports (5) 10/100/1000 Ethernet Ports,
    Management Port (1) 10/100 Ethernet Port, PoE Out Voltage Range 22-24VDC,
    Max. PoE Wattage Per Data Port 11.5 W, PoE Method Passive,
    PoE Configurable Per Port: Management Port N/A, Data Ports Off/24V,
    Power Input 24VDC, 2.5A Power Adapter (Included), Max. Power Consumption 60 W.
  • https://techspecs.ui.com/uisp/wired/es-5xp — HTTP 200, 574,944 B, rendered table; the same
    rows as (5) 10/100/1000 Ethernet ports, (1) 10/100 Ethernet port,
    24V DC, 2.5A power adapter (Included), Max. power consumption 60W, Max. PoE wattage per port 11.5W,
    PoE configurable per port: Management port: N/A / Data ports: Off/24V. No total PoE row.

Not invented

60 W is quoted, not derived: the sheet prints it and 24 V × 2.5 A is 60 W, so it is the included
adapter's ceiling. Ubiquiti prints no "PoE budget" row and — unlike its EdgeRouter pages, which say
"Max. power consumption 16 W (excluding PoE output)" — does not say whether the box's own draw sits
inside the 60 W. It is recorded as an input envelope, the same reading es-16xp.json takes of
that chassis's "300 watts of power", and the note states the margin (5 × 11.5 W = 57.5 W leaves 2.5 W).
No per-port wattage, class or budget was guessed.

After

show power inline on a 60 W envelope:

Available:60.0(w) Used:8.5(w) Remaining:51.5(w)
Interface Admin  Oper       Power   Device
--------- ------ ---------- ------- -------------------
eth3      auto   on         8.5     airCube Home WiFi AP-ap1
4 ports with nothing plugged in: eth0, eth1, eth2, eth4

and show power inline mgmt → % mgmt on EdgeSwitch 5 XP-sw1 cannot supply power (it is not a PSE port).

New test/ubiquiti-es-5xp-poe.test.js: 23 checks covering the vendor census, the five 11.5 W passive
PSEs, the absent 15.4 W phantom on mgmt, the cited budget, and the live show power inline read.

Gates

  • node scripts/syntax-check.js — 538 files, all OK
  • node scripts/audit-port-types.js — 0 contradictions gated
  • node scripts/audit-devices.js — 2,352 models / 0 uncablable / 0 hard defects
  • node scripts/audit-poe-budget.js — silent PSEs 17 → 16; ES-5XP no longer listed
  • node test/hardware-invariants.test.js — 26/26
  • node test/catalogue-hygiene.test.js — 25/25; capability-vocabulary 13/13; poe 21/21; poe-inference 21/21
  • full runner — 458 suites / 15,524 assertions, 0 failed

Blocker on #130 itself, re-measured this run

https://techspecs.ui.com/unifi/cloud-gateways/udw-pro → 307, 1 B, Location: https://techspecs.ui.com/;
https://store.ui.com/us/en/products/udw-pro → 404, 213,322 B; the sixteen-card gateway index
(.../cloud-gateways, 200, 610,412 B, md5 cf2013856f71affe0ce501b99d5f91d1) still contains
the string udw-pro zero times. Unchanged since 13:5x.

Next in this family: es-8xp.json — the remaining member of the XP datasheet (p.6: 8 data ports,
23 W a port at 48 V, 150 W) — is not in the catalogue at all, and ES-16XP currently models its
16 sockets directly. That is the next item, not this PR.

Refs #130 (does not close it — the UDW-PRO is still absent from Ubiquiti's catalogue; see below). ## What this fixes `devices/ubiquiti/es-5xp.json` advertised five PoE ports and could not say a single watt about any of them, and it advertised a sixth that does not exist. | | before | vendor | after | |---|---|---|---| | five data ports | bare `poeOut: true` → `poeDraw()` 1 W each, faceplate prints nothing | "Max. PoE Wattage Per Data Port 11.5 W", "PoE Method Passive" | `poeOut: 11.5`, `poeOutClass: "passive"` | | `mgmt` | no `poeOut` key → `media.js` infers a **15.4 W 802.3af PSE** on a `poe-pse` device | "PoE Configurable Per Port: **Management Port N/A**" | `poeOut: false` | | `poe` block | absent → `parsePoeBudget('ES-5XP')` = 0, `show power inline` says "budget not modelled" | "Max. Power Consumption 60 W" on a 24 V / 2.5 A adapter | `budgetW: 60`, cited, with the silence in the note | | capabilities | no `passive-poe` | PoE method Passive | `passive-poe` (descriptive token, as in `es-16xp.json`) | Measured before: six PSE ports on a five-port PoE switch — `eth0..eth4` at `poeOut: true` (1 W each) and `mgmt` at **15.4 W** — and `show power inline` printed six rows of `not measured` under *"budget not modelled on EdgeSwitch 5 XP-sw1"*. ## Sources (Ubiquiti-hosted, read 2026-11-21) - `https://dl.ui.com/datasheets/edgemax/EdgeSwitch_XP_DS.pdf` — HTTP 200, `application/pdf`, 3,915,117 B, 7 pp, text layer. p.5 is the ES-5XP page: `Data Ports (5) 10/100/1000 Ethernet Ports`, `Management Port (1) 10/100 Ethernet Port`, `PoE Out Voltage Range 22-24VDC`, `Max. PoE Wattage Per Data Port 11.5 W`, `PoE Method Passive`, `PoE Configurable Per Port: Management Port N/A, Data Ports Off/24V`, `Power Input 24VDC, 2.5A Power Adapter (Included)`, `Max. Power Consumption 60 W`. - `https://techspecs.ui.com/uisp/wired/es-5xp` — HTTP 200, 574,944 B, rendered table; the same rows as `(5) 10/100/1000 Ethernet ports`, `(1) 10/100 Ethernet port`, `24V DC, 2.5A power adapter (Included)`, `Max. power consumption 60W`, `Max. PoE wattage per port 11.5W`, `PoE configurable per port: Management port: N/A / Data ports: Off/24V`. No total PoE row. ## Not invented 60 W is quoted, not derived: the sheet prints it and 24 V × 2.5 A is 60 W, so it is the included adapter's ceiling. Ubiquiti prints no "PoE budget" row and — unlike its EdgeRouter pages, which say "Max. power consumption 16 W (excluding PoE output)" — does not say whether the box's own draw sits inside the 60 W. It is recorded as an **input envelope**, the same reading `es-16xp.json` takes of that chassis's "300 watts of power", and the note states the margin (5 × 11.5 W = 57.5 W leaves 2.5 W). No per-port wattage, class or budget was guessed. ## After `show power inline` on a 60 W envelope: ``` Available:60.0(w) Used:8.5(w) Remaining:51.5(w) Interface Admin Oper Power Device --------- ------ ---------- ------- ------------------- eth3 auto on 8.5 airCube Home WiFi AP-ap1 4 ports with nothing plugged in: eth0, eth1, eth2, eth4 ``` and `show power inline mgmt` → `% mgmt on EdgeSwitch 5 XP-sw1 cannot supply power (it is not a PSE port)`. New `test/ubiquiti-es-5xp-poe.test.js`: 23 checks covering the vendor census, the five 11.5 W passive PSEs, the absent 15.4 W phantom on `mgmt`, the cited budget, and the live `show power inline` read. ## Gates - `node scripts/syntax-check.js` — 538 files, all OK - `node scripts/audit-port-types.js` — 0 contradictions gated - `node scripts/audit-devices.js` — 2,352 models / 0 uncablable / 0 hard defects - `node scripts/audit-poe-budget.js` — silent PSEs **17 → 16**; ES-5XP no longer listed - `node test/hardware-invariants.test.js` — 26/26 - `node test/catalogue-hygiene.test.js` — 25/25; `capability-vocabulary` 13/13; `poe` 21/21; `poe-inference` 21/21 - full runner — 458 suites / 15,524 assertions, 0 failed ## Blocker on #130 itself, re-measured this run `https://techspecs.ui.com/unifi/cloud-gateways/udw-pro` → **307, 1 B, `Location: https://techspecs.ui.com/`**; `https://store.ui.com/us/en/products/udw-pro` → **404, 213,322 B**; the sixteen-card gateway index (`.../cloud-gateways`, 200, **610,412 B**, md5 `cf2013856f71affe0ce501b99d5f91d1`) still contains the string `udw-pro` **zero** times. Unchanged since 13:5x. **Next in this family:** `es-8xp.json` — the remaining member of the XP datasheet (p.6: 8 data ports, 23 W a port at 48 V, 150 W) — is not in the catalogue at all, and `ES-16XP` currently models its 16 sockets directly. That is the next item, not this PR.
devices(ubiquiti): the ES-5XP billed 1 W a port and a phantom PSE on mgmt (#130)
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 27s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Test (Node 20) (pull_request) Successful in 1m4s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
f59e400c4a
Five 24 V passive data ports carried the bare poeOut bit (poeDraw: 1 W each,
faceplate: no figure) and no poe block, so show power inline answered
'budget not modelled'. The 10/100 management socket, on a poe-pse device with
no declared figure, was inferred as a 15.4 W 802.3af PSE - six power ports on
a five-port PoE switch.

Datasheet p.5 (EdgeSwitch_XP_DS.pdf, 3,915,117 B) and the tech-spec page
(574,944 B): (5) 10/100/1000 data ports, (1) 10/100 management port,
11.5 W per data port, PoE method Passive, 'Management Port N/A',
24V/2.5A adapter, 'Max. Power Consumption 60 W'.

Ports now 11.5 W passive, mgmt poeOut:false, poe.budgetW 60 recorded as the
adapter envelope with the datasheet's silence on its composition in the note.
Measured: 8.5 W radio on eth3 -> 'Available:60.0(w) Used:8.5(w) Remaining:51.5(w)';
before, six ports 'not measured' and mgmt at 15.4 W.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 15:00:37 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 15:01:11 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 15:08:13 +00:00
jaylouisw deleted branch catalogue/1121-1452 2026-11-21 15:08:40 +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!2438
No description provided.