devices(ubiquiti): the EdgeSwitch 18X sourced power on fifteen sockets it has not got #2403

Merged
jaylouisw merged 1 commit from rev/1121-0942 into main 2026-11-21 10:11:51 +00:00
Owner

Ubiquiti's ES-18X datasheet names both ends of the passthrough in one sentence - "PoE input on port 1 and PoE passthrough on port 16" - while the tech-spec row the entry was built from says only "(1) 24V passive PoE port". The entry put that one port on eth0 (an assumption its own note admitted), and because a switch with poe-pse has its copper ports inferred, derivePortHardware() filled eth1-eth15 with 15.4 W of 802.3af on a 24 V passive box. show power inline listed sixteen PSE ports where the hardware has one.

  • eth15 (port 16): poeOut: 15, poeOutClass: passive - the outlet at the vendor's per-port ceiling.
  • eth0 (port 1): poeIn: 14 - the inlet at the box's own Max. Power Consumption: 14W (Excludes PoE Output), the same shape er-10x.json uses for its 8 W inlet; poe-pd added.
  • eth1-eth14: poeOut: false, so the switch-wide inference cannot re-promote them.
  • poe.budgetW: 10, marked DERIVED (24 W adapter - 14 W draw, the ES-10XP's arithmetic) because Ubiquiti prints no total PoE row. The audit's silent cohort drops 33 -> 32.

test/es-10x-passthrough.test.js pins the outlet, the absence of every other PSE, the inlet, the derived budget and the console's answer.

Sources: ES-18X datasheet, tech specs, EdgeSwitch X datasheet (ES-10X: same construction), HostiFi EdgeMAX PoE table. Open questions in research/es-18x-passthrough-port.md.

Gates: node scripts/syntax-check.js (522 files OK); npm test 442 suites, 14,926 assertions, 0 failed.

Ubiquiti's ES-18X datasheet names both ends of the passthrough in one sentence - "PoE input on port 1 and PoE passthrough on port 16" - while the tech-spec row the entry was built from says only "(1) 24V passive PoE port". The entry put that one port on `eth0` (an assumption its own note admitted), and because a `switch` with `poe-pse` has its copper ports inferred, `derivePortHardware()` filled `eth1`-`eth15` with 15.4 W of 802.3af on a 24 V passive box. `show power inline` listed sixteen PSE ports where the hardware has one. - `eth15` (port 16): `poeOut: 15`, `poeOutClass: passive` - the outlet at the vendor's per-port ceiling. - `eth0` (port 1): `poeIn: 14` - the inlet at the box's own `Max. Power Consumption: 14W (Excludes PoE Output)`, the same shape `er-10x.json` uses for its 8 W inlet; `poe-pd` added. - `eth1`-`eth14`: `poeOut: false`, so the switch-wide inference cannot re-promote them. - `poe.budgetW: 10`, marked **DERIVED** (24 W adapter - 14 W draw, the ES-10XP's arithmetic) because Ubiquiti prints no total PoE row. The audit's silent cohort drops 33 -> 32. `test/es-10x-passthrough.test.js` pins the outlet, the absence of every other PSE, the inlet, the derived budget and the console's answer. Sources: [ES-18X datasheet](https://media.dustin.eu/media/d200001001720050/edgeswitch-18x-product-data-sheet-brochure.pdf), [tech specs](https://techspecs.ui.com/uisp/wired/es-18x), [EdgeSwitch X datasheet](https://dl.ui.com/ds/edgeswitch_x_ds.pdf) (ES-10X: same construction), [HostiFi EdgeMAX PoE table](https://support.hostifi.com/en/articles/8386547-edgemax-which-devices-use-active-poe-and-passive-poe). Open questions in `research/es-18x-passthrough-port.md`. Gates: `node scripts/syntax-check.js` (522 files OK); `npm test` 442 suites, 14,926 assertions, 0 failed.
devices(ubiquiti): the EdgeSwitch 18X sourced power on fifteen sockets it has not got
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
CI / Server smoke and Docker build (pull_request) Successful in 36s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 12s
CI / Test (Node 20) (pull_request) Successful in 1m4s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 3s
033412869a
Ubiquiti's ES-18X datasheet names both ends of the passthrough in one sentence -
"PoE input on port 1 and PoE passthrough on port 16" - while the tech-spec row the
entry was built from says only "(1) 24V passive PoE port". The entry put that one
port on eth0 (an assumption its own note admitted) and, because a switch with
poe-pse has its copper ports inferred, derivePortHardware() filled eth1-eth15 with
15.4 W of 802.3af on a 24 V passive box. show power inline listed sixteen PSE ports
where the hardware has one.

eth15 (port 16) is the outlet at the vendor's 15 W per-port ceiling, classed
passive; eth0 (port 1) declares the inlet at the box's own 14 W max draw; eth1-eth14
declare poeOut: false so inference cannot re-promote them. The budget is a derived
10 W (24 W adapter - 14 W draw), marked DERIVED because Ubiquiti prints no total.

research/es-18x-passthrough-port.md records the sources and the four open questions.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 09:55:16 +00:00
jaylouisw deleted branch rev/1121-0942 2026-11-21 10:11:52 +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!2403
No description provided.