devices(ubiquiti): three 24-port PoE switches sourced 15.4 W from every socket #2397
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2397
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1121-0852"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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-250Wdeclaredpoe.budgetW: 250and nopoeOuton any of its 24 copper ports.ES-24-500WdeclaredbudgetUnknownand nopoeOuteither, and its copper ports also carried noconnectorand nospeedCaps, with the RJ45 serial console missing (26 jacks modelled for 27 physical).engine/media.jsderivePortHardware()fills that silence withiface.poeOut = 15.4on any copper port of a device whose label says PoE - soshow power inline, the faceplate andDevice.poeDraw()all reported 15.4 W on hardware rated 34 W / 34.2 W, and onUS-24-250Wthe 250 W aggregate sat beside a per-port figure that could not produce it.ES-24-250Whad the opposite silence:poeOut: true, whichweb/faceplate.jsnum()refuses (it needs a number) andpoeDraw()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):https://techspecs.ui.com/uisp/wired/es-24-500w(HTTP 200, 582,269 B):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.
devices/ubiquiti/us-24-250w.jsonpoeOut: null,speedCaps: [1G, 10M]poeOut: 34,poeOutClass: PoE+,speedCaps: [1G, 100M, 10M]devices/ubiquiti/es-24-250w.jsonpoeOut: truepoeOut: 34.2,poeOutClass: PoE+devices/ubiquiti/es-24-500w.jsonpoeOut, no consolerj45,[1G, 100M, 10M],poeOut: 34.2,PoE+;consoleport added; capabilitiespoe-pse, 802.3af, 802.3at, passive-poeThe hundred-megabit rung on
US-24-250Wis not incidental: the same page prints(1G/100M/10M)and the row listed only1Gand10M, so a 100M device could not train.What was not invented.
ES-24-500Whas noTotal PoE availablerow on either surface - unlike itsES-24-250Wsibling, which prints250W. The 500 W is the PSU rating and the whole-box ceiling including PoE, sobudgetWstaysnullwithbudgetUnknown: trueandDevice.poeBudgetSourcestays'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 newtest/ubiquiti-24-poe-per-port-watts.test.js(46 checks) and the existingtest/ubiquiti-gen1-poe-budget.test.js,test/poe-inference.test.js,test/hardware-invariants.test.js.