devices(ubiquiti): three PoE budgets that were adapter ratings, and the storefront route map #2274
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!2274
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-0722"
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 — no closing keyword: the UDW-PRO census is still unpublished, and nothing below models it.
Three Ubiquiti rows sourced PoE and could not say how much
node scripts/audit-poe-budget.jslistedusw-flex,udb-switchandeav-xg-24-poeas silent — PoE out on the panel, nopoe.budgetW— and two of the three carried the wrong figure in prose. All rows below were read from the product's own tech-spec payload on 2026-11-20, redirects not followed.ubiquiti/usw-flexTotal PoE Availability - PoE++/60W PoE adapter input: 46 W; PoE+ input: 20 W; PoE input: 8 W, with the vendor's note60W PoE adapter sold separatelyubiquiti/udb-switchTotal PoE Availability - 60W AC adapter input: 35 W / 210W AC adapter input: 185 Wubiquiti/eav-xg-24-poe200-240V AC shared: 2,150 W; 100-120V AC shared: 1,850 W; 200-240V AC redundant: 1,050 W; 100-120V AC redundant: 850 W— all with (2) 1,200 W modulesThe defect is one class, the same one as the 150 W rows in #2265: a power-supply rating read as a PSE allocation. The Flex's 60 W is the adapter; on it the switch hands out 46 W, and 20 W when it is itself fed from an 802.3at port — four 15.4 W cameras need 61.6 W, so a Flex on a PoE+ uplink cannot run its whole panel whatever the setting. The UDB-Switch's 60 W is likewise the smaller adapter: 35 W across eight PoE+ ports (4.4 W average) as shipped on it, 185 W only with the 210 W adapter. The EAV's 2,150 W is real but conditional — the same chassis in a 100-120 V rack with redundant feed gives 850 W.
audit-poe-budget: silent 88 -> 85, prose-figure 13 -> 10.Storefront route map, read while looking for a UDW-PRO artefact
research/ubiquiti-storefront-structure-spec-payload.md. Two facts worth keeping:store.ui.com/us/en/products/udw(200, 568,234 B) embeds the structured spec in__NEXT_DATA__—technicalSpecification.sections[].features[]as label/value rows, plusdocuments: [{InstallationGuide, https://dl.ui.com/qig/udw}]andhistoricalSlugs. For a slug that is known, the storefront is a second vendor copy of the spec, not just a shopping page.store.ui.com/us/en/category/cloud-gateways-wifi-integrated(200, 426,733 B) enumerates 15 cloud-gateway products with full specs — and omits the UDW itself, whose page 200s and whosecategory.currentCategory.idis that same slug, while a different category slug returns the same 15. So it is an index that cannot be cited as a negative: the same rule the UXG control already forced on the techspecs grids.us/en/products/udw-proremains 404 (204,478 B, one byte-identical not-found body for every miss) against 200 / 568,234 B forudw. Cleaner than techspecs, where the Pro slug is a 1-byte 307 andcurl -Lturns a miss into the front page.Gates
syntax-check483 files OK;audit-port-typesno port contradicts its declared type;hardware-invariants26 passed / 0 failed;audit-poe-budgetbudget-with-no-PSE 0; registry doc regenerated fromresearch/open-device-requests.json.