devices(ubiquiti): the Gen1 PoE switches took their budget from the model name, and two of those names are wrong #2142
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!2142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1122"
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 request is still blocked on a product Ubiquiti never listed (no
udw-procard in the cloud-gateway grid, 307 to the site root on techspecs, 404 on the store, noSWX-UDWPROgrant, no firmware platform code). Nothing was modelled from the non-Pro UDW. This PR is the catalogue defect found underneath the request: the Gen1 UniFi switches a routed lab is handed could not be trusted about how much PoE they can supply - and two of them were wrong.The budget came from the model name. Eight
devices/ubiquiti/us-*rows declared PSE ports with nopoe.budgetW, soengine/device.jsfell back toparsePoeBudget(model):us-8-60w.jsonPort Layout 8 (4 PoE),PoE 15.4W/port)us-8-150w.json8 (All PoE+))us-24-250w.jsonPoE 17W / PoE+ 34Wper port)us-24-500w.jsonus-48-500w.jsonus-48-750w.jsonus-8-60w.json's own description already said 48 W while the allocator handed out 60 W, and a second Class-4 AP (25.5 W) fitted under 60 W but not under 48 W - which is the assertion the new test makes.The same label over-reached the PSE count.
media.jsisPoePse()powers every copper port of a switch whose label claims PoE, and this label is "UniFi 8 PoE (Gen1)": ports 5-8 became 15.4 W PSEs on a model the vendor calls8 (4 PoE)- 123.2 W of declared PSE capacity on a 48 W budget. Those four ports now say"poeOut": 0, the conventionfortiswitch-124f-poe.jsonuses. No engine change.Speeds. Every one of these pages prints the copper group as
(1G/100M/10M); the rows offered only1G/100M, so a 10M PoE phone could not negotiate on a port the vendor rates for it.10Madded to the copper ports of all eight rows.Sources (all 200, server-rendered tables, read 2026-11-19):
techspecs.ui.com/unifi/switching/{us-8-60w, us-8-150w, us-24, us-24-250w, us-24-500w, us-48, us-48-500w, us-48-750w}; 634,544 / 630,675 / 616,354 / 638,959 / 629,652 / 617,360 / 626,072 / 619,881 B.research/ubiquiti-unifi-gen1-poe-census.mdcarries the measurements and the traps: everydl.ui.com/ds/us-*_ds.pdfkey is a 302 to the techspecs root, andus-16-150whas no page (307) and no store row (404), so its budget is left as it was rather than invented.Gates:
syntax-check451 files OK;audit-port-typesno contradiction;audit-poe-budgetname-inferred 20 -> 14, "budget with no PSE port" 0;run-tests372 suites, 12,659 assertions, 0 failed (newtest/ubiquiti-gen1-poe-budget.test.js: 41).Eight UniFi Gen1 switch rows declared PSE ports with no poe.budgetW, so engine/device.js fell back to parsePoeBudget(model). US-8-60W was credited 60 W against Ubiquiti's "Total PoE Availability = 48W", US-8-150W 150 W against 130 W - and us-8-60w.json's own description already said 48 W. All six PoE rows now carry the vendor aggregate plus the tech-spec URL; budgets are identical for the other four, traced instead of guessed. The same label ("UniFi 8 PoE (Gen1)") made media.js isPoePse() power all eight copper ports of the US-8-60W, whose vendor census is "8 (4 PoE)": the four data-only ports now say poeOut: 0, as fortiswitch-124f-poe.json already does. Copper speedCaps gain 10M on all eight rows: every page prints the group as (1G/100M/10M). research/ubiquiti-unifi-gen1-poe-census.md records the measurements and the traps (dl.ui.com datasheet keys 302 to the site root; us-16-150w has no page and is left alone).