devices(ubiquiti): three 24-port PoE switches sourced 15.4 W from every socket #2397

Merged
jaylouisw merged 1 commit from catalogue/1121-0852 into main 2026-11-21 09:11:26 +00:00
Owner

Refs #130

Three 24-port PoE switches reported the 802.3af default on sockets their own vendor page rates far higher. The UDW-PRO request behind this run is unchanged and still has no Ubiquiti source, so nothing here closes it; this is the adjacent census defect a Dream Wall lab would put underneath the box, the same way the last increment fixed the Pro PoE racks.

The defect. US-24-250W declared poe.budgetW: 250 and no poeOut on any of its 24 copper ports. ES-24-500W declared budgetUnknown and no poeOut either, and its copper ports also carried no connector and no speedCaps, with the RJ45 serial console missing (26 jacks modelled for 27 physical). engine/media.js derivePortHardware() fills that silence with iface.poeOut = 15.4 on any copper port of a device whose label says PoE - so show power inline, the faceplate and Device.poeDraw() all reported 15.4 W on hardware rated 34 W / 34.2 W, and on US-24-250W the 250 W aggregate sat beside a per-port figure that could not produce it. ES-24-250W had the opposite silence: poeOut: true, which web/faceplate.js num() refuses (it needs a number) and poeDraw() adds as 1 W.

Ubiquiti's own rows, read 2026-11-21.

https://techspecs.ui.com/unifi/switching/us-24-250w (HTTP 200, 638,959 B):

Port Layout        1 GbE RJ45 24 (All PoE+) (1G/100M/10M)
                   1G SFP 2 (1G)
PoE Ports          PoE+ 24
Max. PoE Wattage per Port by PSE   PoE 17W / PoE+ 34W
Max. PoE Output    Up to PoE+
Total PoE Availability   250W
Max. Power Consumption   30W (Excluding PoE output)

https://techspecs.ui.com/uisp/wired/es-24-500w (HTTP 200, 582,269 B):

Networking interface  (24) 10/100/1000 Mbps RJ45 Ethernet ports
                      (2) 1 Gbps SFP ports
Management interface  (1) RJ45 serial port, Ethernet In/Out-Band
Power supply          AC/DC, internal, 500W
Max. power consumption  Includes PoE output: 500W / Excludes PoE output: 30W
PoE interface         PoE/PoE+ (Pins 1, 2+; 3, 6-) / 24V DC passive PoE (Pins 4, 5+; 7, 8-)
Max. PoE+ wattage per port by PSE   34.2W
Max. passive PoE wattage per port   17W

The installation guide the same page links, https://dl.ui.com/qsg/ES-24-250W_ES-24-500W/ES-24-250W_ES-24-500W_EN.html (HTTP 200, 22,805 B), repeats the interface counts and both per-port ceilings and states the shipped configuration: "The PoE settings for ports 1-24 are set to PoE+ auto by default, so 802.3af/at devices can be plugged in and automatically receive PoE" - which is why the class word is PoE+ and not passive, even though the same jacks accept 24V passive.

What changed.

spec before after
devices/ubiquiti/us-24-250w.json 24x poeOut: null, speedCaps: [1G, 10M] 24x poeOut: 34, poeOutClass: PoE+, speedCaps: [1G, 100M, 10M]
devices/ubiquiti/es-24-250w.json 24x poeOut: true 24x poeOut: 34.2, poeOutClass: PoE+
devices/ubiquiti/es-24-500w.json 24x no connector / no ladder / no poeOut, no console 24x rj45, [1G, 100M, 10M], poeOut: 34.2, PoE+; console port added; capabilities poe-pse, 802.3af, 802.3at, passive-poe

The hundred-megabit rung on US-24-250W is not incidental: the same page prints (1G/100M/10M) and the row listed only 1G and 10M, so a 100M device could not train.

What was not invented. ES-24-500W has no Total PoE available row on either surface - unlike its ES-24-250W sibling, which prints 250W. The 500 W is the PSU rating and the whole-box ceiling including PoE, so budgetW stays null with budgetUnknown: true and Device.poeBudgetSource stays 'unknown'; the per-port ceilings went on the ports instead. Nothing was copied from the sibling model: same enclosure, same guide, but every field above is a row on the model's own page.

Gates. node scripts/syntax-check.js -> 521 files OK. node scripts/audit-port-types.js -> 0 contradicting, 0 fibre-as-copper. node scripts/audit-devices.js -> 2352 models, 0 uncablable ports. node scripts/audit-poe-budget.js -> 0 inferred-from-model-name, 0 budget-without-PSE. node scripts/regen-registry-doc.js -> socket census 29,768 -> 29,769 (the ES-24-500W console). node scripts/run-tests.js -> 442 suites, 14,906 assertions, 0 failed, including the new test/ubiquiti-24-poe-per-port-watts.test.js (46 checks) and the existing test/ubiquiti-gen1-poe-budget.test.js, test/poe-inference.test.js, test/hardware-invariants.test.js.

Refs #130 Three 24-port PoE switches reported the 802.3af default on sockets their own vendor page rates far higher. The UDW-PRO request behind this run is unchanged and still has no Ubiquiti source, so nothing here closes it; this is the adjacent census defect a Dream Wall lab would put underneath the box, the same way the last increment fixed the Pro PoE racks. **The defect.** `US-24-250W` declared `poe.budgetW: 250` and no `poeOut` on any of its 24 copper ports. `ES-24-500W` declared `budgetUnknown` and no `poeOut` either, and its copper ports also carried no `connector` and no `speedCaps`, with the RJ45 serial console missing (26 jacks modelled for 27 physical). `engine/media.js` `derivePortHardware()` fills that silence with `iface.poeOut = 15.4` on any copper port of a device whose label says PoE - so `show power inline`, the faceplate and `Device.poeDraw()` all reported 15.4 W on hardware rated 34 W / 34.2 W, and on `US-24-250W` the 250 W aggregate sat beside a per-port figure that could not produce it. `ES-24-250W` had the opposite silence: `poeOut: true`, which `web/faceplate.js` `num()` refuses (it needs a number) and `poeDraw()` adds as 1 W. **Ubiquiti's own rows, read 2026-11-21.** `https://techspecs.ui.com/unifi/switching/us-24-250w` (HTTP 200, 638,959 B): ``` Port Layout 1 GbE RJ45 24 (All PoE+) (1G/100M/10M) 1G SFP 2 (1G) PoE Ports PoE+ 24 Max. PoE Wattage per Port by PSE PoE 17W / PoE+ 34W Max. PoE Output Up to PoE+ Total PoE Availability 250W Max. Power Consumption 30W (Excluding PoE output) ``` `https://techspecs.ui.com/uisp/wired/es-24-500w` (HTTP 200, 582,269 B): ``` Networking interface (24) 10/100/1000 Mbps RJ45 Ethernet ports (2) 1 Gbps SFP ports Management interface (1) RJ45 serial port, Ethernet In/Out-Band Power supply AC/DC, internal, 500W Max. power consumption Includes PoE output: 500W / Excludes PoE output: 30W PoE interface PoE/PoE+ (Pins 1, 2+; 3, 6-) / 24V DC passive PoE (Pins 4, 5+; 7, 8-) Max. PoE+ wattage per port by PSE 34.2W Max. passive PoE wattage per port 17W ``` The installation guide the same page links, `https://dl.ui.com/qsg/ES-24-250W_ES-24-500W/ES-24-250W_ES-24-500W_EN.html` (HTTP 200, 22,805 B), repeats the interface counts and both per-port ceilings and states the shipped configuration: *"The PoE settings for ports 1-24 are set to PoE+ auto by default, so 802.3af/at devices can be plugged in and automatically receive PoE"* - which is why the class word is PoE+ and not passive, even though the same jacks accept 24V passive. **What changed.** | spec | before | after | | --- | --- | --- | | `devices/ubiquiti/us-24-250w.json` | 24x `poeOut: null`, `speedCaps: [1G, 10M]` | 24x `poeOut: 34`, `poeOutClass: PoE+`, `speedCaps: [1G, 100M, 10M]` | | `devices/ubiquiti/es-24-250w.json` | 24x `poeOut: true` | 24x `poeOut: 34.2`, `poeOutClass: PoE+` | | `devices/ubiquiti/es-24-500w.json` | 24x no connector / no ladder / no `poeOut`, no console | 24x `rj45`, `[1G, 100M, 10M]`, `poeOut: 34.2`, `PoE+`; `console` port added; capabilities `poe-pse, 802.3af, 802.3at, passive-poe` | The hundred-megabit rung on `US-24-250W` is not incidental: the same page prints `(1G/100M/10M)` and the row listed only `1G` and `10M`, so a 100M device could not train. **What was not invented.** `ES-24-500W` has **no** `Total PoE available` row on either surface - unlike its `ES-24-250W` sibling, which prints `250W`. The 500 W is the PSU rating and the whole-box ceiling *including* PoE, so `budgetW` stays `null` with `budgetUnknown: true` and `Device.poeBudgetSource` stays `'unknown'`; the per-port ceilings went on the ports instead. Nothing was copied from the sibling model: same enclosure, same guide, but every field above is a row on the model's own page. **Gates.** `node scripts/syntax-check.js` -> 521 files OK. `node scripts/audit-port-types.js` -> 0 contradicting, 0 fibre-as-copper. `node scripts/audit-devices.js` -> 2352 models, 0 uncablable ports. `node scripts/audit-poe-budget.js` -> 0 inferred-from-model-name, 0 budget-without-PSE. `node scripts/regen-registry-doc.js` -> socket census 29,768 -> 29,769 (the ES-24-500W console). `node scripts/run-tests.js` -> 442 suites, 14,906 assertions, 0 failed, including the new `test/ubiquiti-24-poe-per-port-watts.test.js` (46 checks) and the existing `test/ubiquiti-gen1-poe-budget.test.js`, `test/poe-inference.test.js`, `test/hardware-invariants.test.js`.
devices(ubiquiti): three 24-port PoE switches sourced 15.4 W from every socket
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke and Docker build (pull_request) Successful in 26s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 2s
b1c8263388
US-24-250W and ES-24-500W declared a budget or a PSU rating and no poeOut on any
copper port, so derivePortHardware() filled the silence with the 802.3af default:
15.4 W on a chassis Ubiquiti rates at 34 W / 34.2 W PoE+. ES-24-500W was also
missing the rj45 connector, the speed ladder and the RJ45 serial console (26
jacks modelled for 27 physical). ES-24-250W carried a bare 'poeOut: true', which
the faceplate cannot print and poeDraw() adds as 1 W.

Sources: techspecs.ui.com/unifi/switching/us-24-250w (638,959 B),
techspecs.ui.com/uisp/wired/es-24-500w (582,269 B), and the ES-24-250W/ES-24-500W
quick-start guide at dl.ui.com/qsg/ES-24-250W_ES-24-500W/.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 09:02:02 +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!2397
No description provided.