devices(ubiquiti): the UCG-Fiber's PoE+ port, from the store page's key features (#130) #2105
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!2105
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-0622"
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 (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.jsonmodelled 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) printsand marks no port PoE; its
Max. PoE Wattage per Port by PSEgroup 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 conditionscripts/audit-poe-budget.jsrefuses.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: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
devices/ubiquiti/ucg-fiber.jsoncapabilities+=poe-pse,802.3at; Port 1poeOut: 30/poeOutClass: PoE+;poe.budgetW: 30sourced to the store page with the placement caveat inpoe.note; firstsourceUrl(techspecs.ui.com/unifi/cloud-gateways/ucg-fiber); the 10G RJ45 WAN port gainsconnector: rj45andspeedCaps: [10G, 2.5G, 1G]devices/ubiquiti/ucg-max.jsonsourceUrl- the row had none (census already matched: 5x 2.5G RJ45)devices/ubiquiti/UCG-Ultra.jsonsourceUrl- the row had none (census already matched: 1x 2.5G + 4x 1G)research/ubiquiti-cloud-gateway-poe-budgets.mdstore.ui.com/.../products/<slug>renders port classes the tech-spec table dropsPlacement is stated, not invented. Neither host says which of the four ports is the PoE+ one, so Port 1 carries it and
poe.notesays so - the same treatmentdevices/zyxel/gs1900-24ep.jsongives a datasheet that publishes a count and no numbering.Gates
node scripts/syntax-check.js- 443 files, all OKnode 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.js26/0,poe-inference17/0,spec-vs-description3/0,capability-vocabulary13/0,import-devices-capabilities34/0,importer-roundtrip26/0node scripts/run-tests.js- 364 suites, 12,420 assertions, 0 failed