devices(ubiquiti): three 150 W PoE rows sourced, and US-16-150W was 28 W over budget #2265
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!2265
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-0522"
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 only.
That request is still blocked and this branch does not answer it:
udw-prois not a Ubiquiti product page (307 to/), not a card in the eight-grid census (408 cards / 398 SKUs re-counted today, one Dream Wall and no Pro tier beside the 73 existing-ProSKUs), and not in the archived storefront. No UDW-PRO field is modelled here, and no family-sibling number is reused for it.What this branch does is the catalogue underneath the queue: three Ubiquiti 150 W PoE rows that served a power-supply rating as a PSE allocation, which is the defect
show power inlinereports as free watts.us-16-150wTotal available PoE 122W; datasheet p.7Including PoE Output 150W / Excluding PoE Output 28Wes-16-150w150W total PoE availabilityes-8-150w150W total PoE availability150 - 28 = 122, and Ubiquiti prints 122 itself, so nothing here is arithmetic of ours. This is the third instance of the class the census file already names (US-8-60W 60 -> 48 W, US-8-150W 150 -> 130 W).
Two census corrections the same tables forced.
ES-8-150WandES-16-150Wboth print an out-of-band UART console that neither spec declared - added (11 and 19 jacks).US-16-150Wkeeps its console: its datasheet model bullets list(1) Serial Console Portwhile its own spec table's Management row readsEthernet In-Bandalone, and that conflict is recorded rather than resolved in either direction.Sources (all Ubiquiti-hosted, measured 2026-11-20):
https://dl.ui.com/datasheets/unifi/UniFi_PoE_Switch.pdf- 200, 3,962,155 B, 12 pp, text layer, one table per model. This is the link the product's own page serves (www.ui.com/downloads/datasheets/...301s here).https://web.archive.org/web/20231113045611id_/https://store.ui.com/us/en/products/us-16-150w- 200, 21,753 B gzip / 131,196 B decoded;Total available PoE 122W,122W total PoE availability, tagpoe:122w.https://web.archive.org/web/20240409153711id_/https://store.ui.com/us/en/products/es-16-150w- 200, 95,590 B decoded;150W total PoE availability.https://web.archive.org/web/20240906195421id_/https://store.ui.com/us/en/products/es-8-150w- 200, 20,742 B gzip / 124,166 B decoded;150W total PoE availability,Management interface: Ethernet In-Band, UART console Out-of-Band.techspecs.ui.com/uisp/wired/es-16-150w200 / 574,980 B,.../es-8-150w200 / 583,247 B (prints no Management row),techspecs.ui.com/unifi/switching/us-16-150w307 to/,dl.ui.com/ds/es-16-150w_ds.pdfandus-16-150w_ds.pdf302 to the techspecs root.Research basis:
research/ubiquiti-unifi-gen1-poe-census.mdsaid this family has no datasheet text layer. That was true only of thedl.ui.com/ds/path; the datasheet lives atdl.ui.com/datasheets/unifi/, and the archived-storefront route for retired SKUs is now recorded with it.Gates:
node scripts/syntax-check.jsall OK;node scripts/audit-port-types.jsno port contradicts its type;node test/hardware-invariants.test.js26/26;npm test401 suites / 13,351 assertions, 0 failed;audit-poe-budget"inferred from name" 11 -> 8.docs/CONNECTORS.mdregenerated (29,731 -> 29,733 sockets).