devices(ubiquiti): the UISP Router's eight PoE ports were 802.3af phonies with no budget (refs #130) #2165
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!2165
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1422"
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 (records the catalogue defect found underneath this request; it does not close it)
#130 asks for a Dream Wall Pro and is still blocked - no Ubiquiti surface names
UDW-PRO, and the surfaces were not re-walked this pass (nine exhausted, last measured 13:25 today). It spent the increment on the box a routed lab is handed when the requested gateway does not exist: a router that declares PoE and cannot deliver a watt.devices/ubiquiti/uisp-r.json- the UISP Router, Ubiquiti's eight-port MicroPoP router - was wrong twice on the same rows:poeOut: true,poeOutClass: "PoE"(802.3af, 48 V negotiated)poeblockWith no
poeblock,engine/device.jsfell through toparsePoeBudget('UISP-R'), which has no figure in it - budget 0, sourcename.engine/simulator.jsopenscomputePoe()withif (!dev.poeBudget) continue;, so the box was skipped rather than reported unknown: eight advertised PSE ports, no entry inshow power inline, and a MicroPoP router that could not power one airMAX radio while saying nothing about why. Same defect class aser-6p/er-12p(#2135) and the LTE Backup Pro (#2150, still open).Measured before/after (NBE-5AC-Gen2, 12.95 W PD, on
eth4):nametrue, class "PoE")researchpassive)The budget is derived, and says so. Ubiquiti prints no total PoE row for this SKU. It prints the two figures that bound it: the included adapter is 27 V x 4.4 A = 118.8 W, and the router draws "10W (Excluding PoE output)", leaving 108.8 W for the eight ports. Recorded as a derived ceiling in the same shape as
devices/antaira/lmp-1002g-sfp-t.json, with the arithmetic inpoe.note; eight ports at the vendor's 30 W would be 240 W, so the adapter - not the port count - is what stops a full fill.Sources (read 2026-11-19, both Ubiquiti-hosted)
https://techspecs.ui.com/uisp/wired/uisp-r- HTTP 200, 583,910 B, title "UISP Router - Tech Specs": "(8) GbE RJ45 ports" + "(1) 1G SFP port", the PoE interface / per-port / voltage rows quoted above, "Supported voltage range 24-28V DC", "Max. power consumption 10W (Excluding PoE output)".https://dl.ui.com/ds/uisp-r_ds.pdf- HTTP 200,application/pdf, 2,635,831 B, 2 pp, text layer: the same rows, plus "(8) 10/100/1000 MbE RJ45 ports" (the 10M rung now inspeedCaps).storefrontProduct(slug:"uisp-r")answersdisplaySku UISP-R,status Available.Traps recorded: the datasheet key is hyphenated per SKU -
dl.ui.com/ds/uisp_router_ds.pdfanswers 302 andstore.ui.com/us/en/products/uisp-routeranswers 404, while.../products/uisp-randdl.ui.com/ds/uisp-r_ds.pdfboth resolve.Test:
test/uisp-r-poe.test.js(new, 15 assertions) pins the port census, the 30 W passive class (and the absence of 802.3af/at), the derived budget with itsresearchsource, and thatcomputePoe()now powers a radio cabled toeth4.Gates: syntax-check 454 OK; audit-port-types clean; audit-poe-budget silent-PSE count 104 -> 103; run-tests 376 suites / 12,765 assertions / 0 failed; check-control-bytes clean; doc citations clean; registry doc unchanged (2,356 models, 29,718 sockets - no model added).
Still missing for #130, unchanged: RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, and the cellular/WAN options. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller record naming
UDW-PRO, or the requester confirming they meant theUDWalready catalogued atdevices/ubiquiti/udw.json.