devices(ubiquiti): the NanoSwitch priced a 72 W passthrough load at 3 W #2431
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!2431
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1121-1352"
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 (the Dream Wall Pro link is still absent; this is the catalogue defect beside it, not a close).
devices/ubiquiti/n-sw.jsonshipped three sockets on the barepoeOut: truedirection bit and nopoe.budgetW.Device.poeDraw()(engine/device.js) adds that bit as 1 W, andpseDraw()(engine/validation.js) sums the same field against the budget - so the unit had no budget to exceed.Measured before (HEAD~1 spec, three Ubiquiti R2AC radios, 24 W passive draw each):
The vendor's page -
https://techspecs.ui.com/uisp/wired/n-sw(HTTP 200, 575,565 B, server-rendered<td class="key">table, crawler user-agent, read 2026-11-21):(4) GbE RJ45 ports [(1) PoE-in, (3) PoE passthrough]Passive 24V, 2-pair PoE-inTypical: 1.5W / Max.: 30W24V, 2-pair, 1A per port (24W)24V, 2-pair, 1A for 3 ports (30W)The fix. eth0-eth2 declare
poeOut: 24in thepassiveclass (they had claimedPoE/802.3af, which the vendor'sPower method: Passive 24Vcontradicts, and on which a standard PD cannot come up);poe.budgetWis 30 W with the vendor's line inpoe.note; eth3 becomes the PoE-in socket (poeIn: 1.5, the typical consumption), so the spec'spoe-pdcapability finally has a socket that accepts power. Three sockets at 24 W reach 72 W against a 30 W aggregate, which is why the budget and not only the per-port ceiling is carried.The vendor prints no port numbers - only
(1) PoE-in, (3) PoE passthrough- so this pass fixed the count, the wattages and the class without renumbering the panel: the sockets that already carriedpoeOutstay the PSE sockets and the fourth becomes the input.Measured after (test/ubiquiti-n-sw-poe-passthrough.test.js, 19 assertions):
Gates:
scripts/syntax-check.js536 files OK;scripts/audit-port-types.js0 gated, 0 contradicting;scripts/audit-poe-budget.jssilent PSEs 19 -> 18;test/hardware-invariants.test.js26 passed;test/catalogue-hygiene.test.js25 passed; the six N-SW-touching suites (poe-inference, show-vlan-ports-wrap, show-vlan-router-ports, stp-port-channel-cost, vlan-name-length, etherchannel-summary-layout) pass;docs/DEVICE_REGISTRY.mdregenerated with no diff.Still blocked on #130 itself: re-measured this run -
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro307 ->/,https://store.ui.com/us/en/products/udw-pro404 (213,322 B),https://dl.ui.com/ds/udw_pro_ds.pdf302 ->https://techspecs.ui.com/. No UDW-PRO row exists to model.