catalogue(usw-ultra): the PoE budget is a function of the power input, and port 8 takes power rather than giving it #2005
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2005
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-1626"
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?
Related to #130, which found the same defect one layer up: a PoE budget that exists in a description but not in
poe.budgetW, so the engine falls through to the model-name parser. This PR does not close #130 - UDW-PRO still has no Ubiquiti source.What the three specs said
devices/ubiquiti/usw-ultra.json,-60wand-210weach carried the description "42 W PoE budget" - including the 210 W one - and none carriedpoe.budgetW:show power inlineUSW-Ultrabudget not modelled: the ports are reported, the power they could supply is notUDW-style parser gets nothing from the nameUSW-Ultra-60WUSW-Ultra-210WAll three also gave the switch 8 PSE ports, the eighth being
eth7atpoeOutClass: "PoE++"(60 W).What Ubiquiti publishes
One row, "Total PoE Availability", with five values keyed on how the unit is powered:
All three print the identical five-row table: the SKU suffix names the adapter, not a different PoE engine. The store page says the same in prose - "PoE input is supported for switch operation, with PoE+/PoE++ input or AC power required for PoE output" - and offers the one product with "No AC Adapter" / "60W AC Adapter" / "210W AC Adapter" as power options (https://store.ui.com/us/en/products/usw-ultra, 200, 673,337 B;
.../usw-ultra-210w, 200, 660,250 B).So each spec now holds the row its own name selects: 42 W / 52 W / 202 W, with all five figures in
poe.noteso a lab powered from a different adapter takes that row instead of inheriting this one - the same shape as the ECS-24-PoE PSU table.The census error the same table corrected
The port layout is "8 (7 PoE+; 1 PoE++ input)" and "Max. PoE Output: Up to PoE+", with "Max. PoE Wattage per Port by PSE: PoE+ 30 W" and no PoE++ PSE row. Port 8 is where the unit takes power from an upstream switch - which is why its power method reads "(1) AC/DC adapter (Excluded) / (1) PoE++" and why the store requires PoE+/PoE++ input or AC power for any PoE output at all.
eth7is therefore"poeOut": 0, "poeIn": 9(9 W is the vendor's "max. power consumption excluding PoE output with PoE input"), so the model reports 7 PSE ports rather than 8. This is the phantom-PoE class again - the extra UDM draw - this time on the source side of one port.The eight ports also regained the
10Mcap that the vendor's own "(1G/100M/10M)" line gives them and the specs had dropped.Verified, not assumed
Gates
node scripts/syntax-check.js- 418 files, all OKnode scripts/audit-port-types.js- no port contradicts its declared typenode scripts/audit-poe-budget.js- silent 130 -> 129, name-inferred 22 -> 20, orphans 0node test/hardware-invariants.test.js- 26 passed, 0 failednode test/poe.test.js- 18 passed, 0 failed;duplicate-models21,port-roles19,combo19,apply-research10 - all 0 failedresearch/poe-budget-field-census.mdgains section 4 recording the family and the corrected cohortsTrap for the next pass:
https://dl.ui.com/ds/usw-ultra_ds.pdf302s tohttps://techspecs.ui.com/and serves the same 609,911-byte home page as every missingdl.ui.comdocument - there is no Ultra datasheet, and that page is not one.1effe910d2567f07aae2567f07aae2tocb44083f88cb44083f88tob2c0eeb11eCI has never dispatched for this branch — four SHAs, zero checks, while a sibling PR from the same loop got 8/8.
Statuses for
567f07aa,cb44083fand the current headb2c0eeb1all reporttotal_count: 0. #2007 (catalogue/1118-1656, created the same minute) got its full 8. So this is branch-specific, not repo-wide.Likely mechanism: the "PR rebase / arm auto-merge" workflow force-pushes the branch when it is behind, and a bot-token push appears to suppress the resulting event — so each rebase lands a new SHA that starts no run, checks stay empty, the PR stays unmergeable, and the loop rebases again.
b2c0eeb1already contains currentmain(0df1bef6), so a further rebase is a no-op; what is needed is a human/loop-origin push of the same tree so thepull_requestevent fires.What I verified locally on
b2c0eeb1(so nobody has to re-derive it):main: already up to date, no conflicttest/poe.test.js: 18 passed, 0 failedscripts/check-canonical-urls.js: OK — 3154 files, every project URL canonicalscripts/check-control-bytes.js: cleanThe tree looks good. I am not merging it with an empty status (standing rule: green head SHA only). If it stays stale, an empty commit pushed from the loop's own credentials should be enough to get the event to fire.
b2c0eeb11eto4b6f2ae22b4b6f2ae22b4ec1a15ccaChecks recovered the same way, then merged as
c142e739. Same cause as #2008:1effe910was checked (run 6463), the rebase bot force-pushed4b6f2ae2, no run for it. Close/reopen produced run 6497; Node 20 failed once there (Test (Node 20)only, 18 and 22 green) and a second close/reopen on4ec1a15cpassed 8/8 — so that failure was transient, not a defect. Nothing in the diff needed changing.