devices(ubiquiti): the 48-port EdgeSwitches billed every PoE socket as 1 W #2400
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!2400
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1121-0922"
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 (no closing keyword - the UDW-PRO request is still blocked on a vendor source that does not exist; this is the increment underneath it).
The Pro is unchanged. Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /, and following it lands on the techspecs home page: 609,911 B,udw-prooccurring zero times);https://store.ui.com/us/en/products/udw-pro-> 404 (213,322 B not-found body). Nothing has appeared.The defect this pass found.
ES-48-500WandES-48-750WcarriedpoeOut: trueon all 48 copper ports - the bare direction bit thatengine/media.jspoeDraw()bills as 1 W and the faceplate'snum()prints as nothing - on chassis Ubiquiti rates at 34.2 W per port by PSE. Every socket refused a 30 W 802.3at access point.Sources (all Ubiquiti, read 2026-11-21):
https://techspecs.ui.com/uisp/wired/es-48-500wNetworking interface (48) GbE RJ45 ports / (2) 1/10G SFP+ / (2) 1G SFP;PoE interface (48) PoE/PoE+ 2-pair / (48) 24V DC passive PoE 2-pair;Max. PoE wattage per port by PSE PoE+: 34.2W / Passive PoE: 17W;Total PoE available 500Whttps://techspecs.ui.com/uisp/wired/es-48-750w(48) 10/100/1000 Mbps RJ45;Max. PoE+ wattage per port by PSE 34.2W;Max. passive PoE wattage per port 17W;Power supply AC/DC, internal, 750W;Max. power consumption Includes PoE output: 750W / Excludes: 64W; noTotal PoE availablerowhttps://dl.ui.com/qsg/ES-48-500W_ES-48-750W/ES-48-500W_ES-48-750W_EN.htmlModel: ES-48-500W, ES-48-750W;RJ45 (Ports 1 - 48) ... 10/100/1000 Ethernet connections;Max. PoE+ Wattage per Port by PSE 34.2W;Max. Passive PoE Wattage per Port 17W;The PoE settings for ports 1-48 are set to PoE+ auto by default, so 802.3af/at devices can be plugged in and automatically receive PoEWhat changed. All 48 copper sockets on both models now declare
poeOut: 34.2withpoeOutClass: "PoE+"(the shipped PoE+ auto state, not the 802.3af default the engine had been inventing), and both specs declare802.3afbeside802.3at.ES-48-500Walso gains the 10M rung: its tech-spec row abbreviates the ladder toGbE, while the quick-start guide that names both models prints10/100/1000for ports 1-48. The 17 W 24 V passive ceiling sits on the same jacks and is not additive, so it is recorded innotesrather than on the ports.Not invented.
ES-48-750WkeepsbudgetW: null/budgetUnknown: true. Its 750 W is the internal PSU and the whole-box ceiling including PoE; unlike the 500 W sibling Ubiquiti prints no total-PoE row, so the allocator stays told nothing rather than 750 W from the model name.ES-48-500Wkeeps the published 500 W allocation (poeBudgetSource: 'research').Gates.
node scripts/syntax-check.js-> 523 files, all OK.node scripts/audit-port-types.js-> Gated: 0 contradicting ports.node scripts/audit-devices.js-> 2,352 models, 0 uncablable ethernet ports, 0 hard defects.node scripts/audit-poe-budget.js-> 0 budgets inferred from the model name, 0 budgets with no PSE port.node test/hardware-invariants.test.js-> 26/26. Newtest/ubiquiti-48-poe-per-port-watts.test.js-> 41 checks (census, per-port watts, direction, budget, a 30 W AP cabled to Port 48). All 32*poe*/faceplate suites re-run green;scripts/regen-registry-doc.jsreports the registry current (no generated-file drift).