devices(ubiquiti): the UCG-Fiber's PoE+ port, from the store page's key features (#130) #2105

Merged
jaylouisw merged 1 commit from catalogue/1119-0622 into main 2026-11-19 06:41:12 +00:00
Owner

Refs #130 (references it; does not close it - the UDW-PRO itself is still unmodelled, because Ubiquiti publishes no page, datasheet, grant or store entry for that SKU).

What was wrong

devices/ubiquiti/ucg-fiber.json modelled a 30 W PoE budget it never declared and a gateway that cannot source a watt. Its own rendered tech-spec table (https://techspecs.ui.com/unifi/cloud-gateways/ucg-fiber, 200, 667,242 B, __NEXT_DATA__ -> props.pageProps.product.technicalSpecification) prints

PoE Budget            = 30W
Voltage Range PoE Mode = 50-57V
2.5 GbE RJ45 = 4 (2.5G/1G/100M/10M)
10 GbE RJ45  = 1 (10G/2.5G/1G)
10G SFP+     = 2 (10G/1G)

and marks no port PoE; its Max. PoE Wattage per Port by PSE group is present but empty. A previous pass (research/ubiquiti-cloud-gateway-poe-budgets.md) therefore recorded the budget and left the row without a single PSE - correct at the time, since a budget with no port is the condition scripts/audit-poe-budget.js refuses.

What the vendor does publish

The store product page for the same SKU is a second vendor surface, and it names the class the tech-spec table omits. https://store.ui.com/us/en/products/ucg-fiber (200, 595,865 B, server-rendered, displaySku = UCG-Fiber (30W)), keyFeatures:

(1) 10G SFP+ and (1) 10 GbE RJ45 WAN port
(1) 10G SFP+ LAN port
Integrated 4-port switch with (1) PoE+ port

So: one 802.3at (PoE+) port among the four 2.5 GbE RJ45 ports, against a 30 W budget = one port at its 30 W PSE ceiling.

Changes

file change
devices/ubiquiti/ucg-fiber.json capabilities += poe-pse, 802.3at; Port 1 poeOut: 30 / poeOutClass: PoE+; poe.budgetW: 30 sourced to the store page with the placement caveat in poe.note; first sourceUrl (techspecs.ui.com/unifi/cloud-gateways/ucg-fiber); the 10G RJ45 WAN port gains connector: rj45 and speedCaps: [10G, 2.5G, 1G]
devices/ubiquiti/ucg-max.json sourceUrl - the row had none (census already matched: 5x 2.5G RJ45)
devices/ubiquiti/UCG-Ultra.json sourceUrl - the row had none (census already matched: 1x 2.5G + 4x 1G)
research/ubiquiti-cloud-gateway-poe-budgets.md the UCG-Fiber row closed out; method note that store.ui.com/.../products/<slug> renders port classes the tech-spec table drops

Placement is stated, not invented. Neither host says which of the four ports is the PoE+ one, so Port 1 carries it and poe.note says so - the same treatment devices/zyxel/gs1900-24ep.json gives a datasheet that publishes a count and no numbering.

Gates

  • node scripts/syntax-check.js - 443 files, all OK
  • node scripts/audit-port-types.js - "No port contradicts its declared type."
  • node scripts/audit-poe-budget.js - 108 of 403 PSEs unaskable (was 108 of 402: the new PSE arrives with a source, so no silent row was added); "Budget with no PSE port: 0"
  • node test/hardware-invariants.test.js 26/0, poe-inference 17/0, spec-vs-description 3/0, capability-vocabulary 13/0, import-devices-capabilities 34/0, importer-roundtrip 26/0
  • node scripts/run-tests.js - 364 suites, 12,420 assertions, 0 failed
Refs #130 (references it; does not close it - the UDW-PRO itself is still unmodelled, because Ubiquiti publishes no page, datasheet, grant or store entry for that SKU). ## What was wrong `devices/ubiquiti/ucg-fiber.json` modelled a 30 W PoE budget it never declared and a gateway that cannot source a watt. Its own rendered tech-spec table (https://techspecs.ui.com/unifi/cloud-gateways/ucg-fiber, 200, 667,242 B, `__NEXT_DATA__ -> props.pageProps.product.technicalSpecification`) prints ``` PoE Budget = 30W Voltage Range PoE Mode = 50-57V 2.5 GbE RJ45 = 4 (2.5G/1G/100M/10M) 10 GbE RJ45 = 1 (10G/2.5G/1G) 10G SFP+ = 2 (10G/1G) ``` and marks **no** port PoE; its `Max. PoE Wattage per Port by PSE` group is present but empty. A previous pass (`research/ubiquiti-cloud-gateway-poe-budgets.md`) therefore recorded the budget and left the row without a single PSE - correct at the time, since a budget with no port is the condition `scripts/audit-poe-budget.js` refuses. ## What the vendor does publish The **store product page** for the same SKU is a second vendor surface, and it names the class the tech-spec table omits. `https://store.ui.com/us/en/products/ucg-fiber` (200, 595,865 B, server-rendered, `displaySku` = `UCG-Fiber (30W)`), `keyFeatures`: ``` (1) 10G SFP+ and (1) 10 GbE RJ45 WAN port (1) 10G SFP+ LAN port Integrated 4-port switch with (1) PoE+ port ``` So: **one 802.3at (PoE+) port among the four 2.5 GbE RJ45 ports**, against a 30 W budget = one port at its 30 W PSE ceiling. ## Changes | file | change | |---|---| | `devices/ubiquiti/ucg-fiber.json` | `capabilities` += `poe-pse`, `802.3at`; Port 1 `poeOut: 30` / `poeOutClass: PoE+`; `poe.budgetW: 30` sourced to the store page with the placement caveat in `poe.note`; first `sourceUrl` (`techspecs.ui.com/unifi/cloud-gateways/ucg-fiber`); the 10G RJ45 WAN port gains `connector: rj45` and `speedCaps: [10G, 2.5G, 1G]` | | `devices/ubiquiti/ucg-max.json` | `sourceUrl` - the row had none (census already matched: 5x 2.5G RJ45) | | `devices/ubiquiti/UCG-Ultra.json` | `sourceUrl` - the row had none (census already matched: 1x 2.5G + 4x 1G) | | `research/ubiquiti-cloud-gateway-poe-budgets.md` | the UCG-Fiber row closed out; method note that `store.ui.com/.../products/<slug>` renders port classes the tech-spec table drops | **Placement is stated, not invented.** Neither host says *which* of the four ports is the PoE+ one, so Port 1 carries it and `poe.note` says so - the same treatment `devices/zyxel/gs1900-24ep.json` gives a datasheet that publishes a count and no numbering. ## Gates - `node scripts/syntax-check.js` - 443 files, all OK - `node scripts/audit-port-types.js` - "No port contradicts its declared type." - `node scripts/audit-poe-budget.js` - 108 of 403 PSEs unaskable (was 108 of 402: the new PSE arrives with a source, so no silent row was added); "Budget with no PSE port: 0" - `node test/hardware-invariants.test.js` 26/0, `poe-inference` 17/0, `spec-vs-description` 3/0, `capability-vocabulary` 13/0, `import-devices-capabilities` 34/0, `importer-roundtrip` 26/0 - `node scripts/run-tests.js` - 364 suites, 12,420 assertions, 0 failed
devices(ubiquiti): the UCG-Fiber's PoE+ port, from the store page's key features (#130)
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 8s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 16s
CI / Arm auto-merge (pull_request) Successful in 3s
39b908f6c7
The rendered tech-spec table prints 'PoE Budget = 30W' and marks no port PoE, so the row
was left with no PSE at all - a 30 W gateway that cannot power one access point. The
vendor's own store page for the same SKU (displaySku 'UCG-Fiber (30W)') states the class
and the count in its key features: 'Integrated 4-port switch with (1) PoE+ port'.

- ucg-fiber: poe-pse + 802.3at, poeOut 30 / PoE+ on Port 1 (placement unpublished on
  either host - same convention as zyxel/gs1900-24ep), poe.budgetW 30, sourceUrl.
  The 10G RJ45 WAN port also gains connector rj45 and speedCaps 10G/2.5G/1G.
- ucg-max, UCG-Ultra: the sourceUrl they never had; censuses already matched the table.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 06:31:19 +00:00
jaylouisw deleted branch catalogue/1119-0622 2026-11-19 06:41:14 +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!2105
No description provided.