devices(ubiquiti): three PoE budgets that were adapter ratings, and the storefront route map #2274

Merged
jaylouisw merged 1 commit from catalogue/1120-0722 into main 2026-11-20 07:38:52 +00:00
Owner

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.js listed usw-flex, udb-switch and eav-xg-24-poe as silent — PoE out on the panel, no poe.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.

spec was now vendor row
ubiquiti/usw-flex no budget; description claimed 60 W 46 W Total PoE Availability - PoE++/60W PoE adapter input: 46 W; PoE+ input: 20 W; PoE input: 8 W, with the vendor's note 60W PoE adapter sold separately
ubiquiti/udb-switch no budget; description claimed 60 W 185 W Total PoE Availability - 60W AC adapter input: 35 W / 210W AC adapter input: 185 W
ubiquiti/eav-xg-24-poe no budget; description claimed 2,150 W flat 2,150 W, conditioned 200-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 modules

The 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, plus documents: [{InstallationGuide, https://dl.ui.com/qig/udw}] and historicalSlugs. 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 whose category.currentCategory.id is 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-pro remains 404 (204,478 B, one byte-identical not-found body for every miss) against 200 / 568,234 B for udw. Cleaner than techspecs, where the Pro slug is a 1-byte 307 and curl -L turns a miss into the front page.

Gates

syntax-check 483 files OK; audit-port-types no port contradicts its declared type; hardware-invariants 26 passed / 0 failed; audit-poe-budget budget-with-no-PSE 0; registry doc regenerated from research/open-device-requests.json.

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.js` listed `usw-flex`, `udb-switch` and `eav-xg-24-poe` as *silent* — PoE out on the panel, no `poe.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. | spec | was | now | vendor row | |---|---|---|---| | `ubiquiti/usw-flex` | no budget; description claimed **60 W** | **46 W** | `Total PoE Availability - PoE++/60W PoE adapter input: 46 W; PoE+ input: 20 W; PoE input: 8 W`, with the vendor's note `60W PoE adapter sold separately` | | `ubiquiti/udb-switch` | no budget; description claimed **60 W** | **185 W** | `Total PoE Availability - 60W AC adapter input: 35 W / 210W AC adapter input: 185 W` | | `ubiquiti/eav-xg-24-poe` | no budget; description claimed **2,150 W** flat | **2,150 W**, conditioned | `200-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 modules | The 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, plus `documents: [{InstallationGuide, https://dl.ui.com/qig/udw}]` and `historicalSlugs`. 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 whose `category.currentCategory.id` is 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-pro` remains **404** (204,478 B, one byte-identical not-found body for every miss) against **200 / 568,234 B** for `udw`. Cleaner than techspecs, where the Pro slug is a 1-byte 307 and `curl -L` turns a miss into the front page. ## Gates `syntax-check` 483 files OK; `audit-port-types` no port contradicts its declared type; `hardware-invariants` 26 passed / 0 failed; `audit-poe-budget` budget-with-no-PSE 0; registry doc regenerated from `research/open-device-requests.json`.
devices(ubiquiti): three PoE budgets that were adapter ratings, and the storefront's route map
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke and Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 4s
4e5320b593
usw-flex, udb-switch and eav-xg-24-poe source PoE and had no poe.budgetW; two of
them quoted the power adapter's rating as a PSE allocation (60 W on a Flex that
hands out 46 W, 60 W on a UDB-Switch that hands out 35 W on that adapter, 185 W
on the 210 W one). The EAV-XG-24-PoE row keeps its 2,150 W but now names the four
voltage/PSU-mode figures behind it. All three are sourced to their techspecs rows.

Also records the storefront route map read for #130: product pages embed a
structured technicalSpecification, the category page enumerates 15 cloud
gateways and omits the UDW, so it cannot be cited as a negative - Refs #130.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 07:31:26 +00:00
jaylouisw deleted branch catalogue/1120-0722 2026-11-20 07:38:54 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2274
No description provided.