devices(ubiquiti): the Gateway Fiber could not power the AP its 30 W budget is rated for (refs #130) #2175

Merged
jaylouisw merged 1 commit from catalogue/1119-1552 into main 2026-11-19 16:11:36 +00:00
Owner

Refs #130 — the UDW-Pro request itself is still blocked (no vendor page, datasheet, grant, QSG or storefront entry names UDW-PRO; #1781, #1823, #1864, #1979, #2088, #2093, #2096, #2101). This PR does not answer it and must not close it.

What it fixes is the family the request falls back into: devices/ubiquiti/uxg-fiber.json (UniFi Gateway Fiber) declared no poe-pse, carried no poe block and had no poeOut port — so show power inline answered % No PoE on GW: no port on this device can supply power on a box the vendor says sources 30 W on one of its four 2.5G RJ45 ports.

Vendor census, read today (2026-11-19)

Field Value Source
PoE budget 30 W https://techspecs.ui.com/unifi/cloud-gateways/uxg-fiber — HTTP 200, 649,433 B, row "PoE Budget = 30W"
Max PoE per port by PSE PoE+ = 30 W same page, "Max. PoE Wattage per Port by PSE = PoE+ / 30W"
PoE voltage range 50–57 V same page, "Voltage Range PoE Mode = 50–57V"
PSE port count and class one PoE+ port https://store.ui.com/us/en/products/uxg-fiber — HTTP 200, 476,892 B, displaySku UXG-Fiber (30W): "Integrated 4-port switch with (1) PoE+ port"

Placement is a convention, not a vendor fact: neither host numbers the PoE+ port, so it is on eth0 — the same convention devices/ubiquiti/ucg-fiber.json (Cloud Gateway Fiber, the twin of this box with an identical 30 W / one-PoE+ census) already uses and documents. Count, class and ceiling are the vendor's.

Before / after, measured on the engine, not asserted

before: sim.poe[0] === undefined      -> "% No PoE on GW: no port on this device can supply power"
after : Available:30.0(w) Used:13.0(w) Remaining:17.0(w)
        eth0       auto   on         12.95 W  AP

(cabling a U6-Lite to eth0 — the gateway now powers the one AP its budget is sized for.)

Also updated research/incoming/devices-ubiquiti-gateways.json so a re-import cannot silently drop the new capability (the importer's tripwire refuses a spec that loses a declared capability).

Gates: node scripts/syntax-check.js 459 files OK; node scripts/audit-port-types.js no contradiction; node scripts/check-control-bytes.js clean; node test/hardware-invariants.test.js 26/26; node test/poe.test.js 21/21, poe-inference 17/17; node scripts/run-tests.js 380 suites, 12,862 assertions, 0 failed. scripts/audit-poe-budget.js: 103 of 406 PSEs unaskable (was 103 of 405 — the new PSE is the one that asks, and it answers).

Refs #130 — the UDW-Pro request itself is still blocked (no vendor page, datasheet, grant, QSG or storefront entry names UDW-PRO; #1781, #1823, #1864, #1979, #2088, #2093, #2096, #2101). This PR does not answer it and must not close it. What it fixes is the family the request falls back into: `devices/ubiquiti/uxg-fiber.json` (UniFi Gateway Fiber) declared no `poe-pse`, carried no `poe` block and had no `poeOut` port — so `show power inline` answered `% No PoE on GW: no port on this device can supply power` on a box the vendor says sources 30 W on one of its four 2.5G RJ45 ports. Vendor census, read today (2026-11-19) | Field | Value | Source | |---|---|---| | PoE budget | 30 W | <https://techspecs.ui.com/unifi/cloud-gateways/uxg-fiber> — HTTP 200, 649,433 B, row "PoE Budget = 30W" | | Max PoE per port by PSE | PoE+ = 30 W | same page, "Max. PoE Wattage per Port by PSE = PoE+ / 30W" | | PoE voltage range | 50–57 V | same page, "Voltage Range PoE Mode = 50–57V" | | PSE port count and class | one PoE+ port | <https://store.ui.com/us/en/products/uxg-fiber> — HTTP 200, 476,892 B, displaySku `UXG-Fiber (30W)`: "Integrated 4-port switch with (1) PoE+ port" | Placement is a convention, not a vendor fact: neither host numbers the PoE+ port, so it is on `eth0` — the same convention `devices/ubiquiti/ucg-fiber.json` (Cloud Gateway Fiber, the twin of this box with an identical 30 W / one-PoE+ census) already uses and documents. Count, class and ceiling are the vendor's. Before / after, measured on the engine, not asserted ``` before: sim.poe[0] === undefined -> "% No PoE on GW: no port on this device can supply power" after : Available:30.0(w) Used:13.0(w) Remaining:17.0(w) eth0 auto on 12.95 W AP ``` (cabling a U6-Lite to eth0 — the gateway now powers the one AP its budget is sized for.) Also updated `research/incoming/devices-ubiquiti-gateways.json` so a re-import cannot silently drop the new capability (the importer's tripwire refuses a spec that loses a declared capability). Gates: `node scripts/syntax-check.js` 459 files OK; `node scripts/audit-port-types.js` no contradiction; `node scripts/check-control-bytes.js` clean; `node test/hardware-invariants.test.js` 26/26; `node test/poe.test.js` 21/21, `poe-inference` 17/17; `node scripts/run-tests.js` 380 suites, 12,862 assertions, 0 failed. `scripts/audit-poe-budget.js`: 103 of 406 PSEs unaskable (was 103 of 405 — the new PSE is the one that asks, and it answers).
devices(ubiquiti): the Gateway Fiber declared no PoE, so it could not power the one AP it is rated for (refs #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 10s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 1m7s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 4s
37f6079eaa
techspecs.ui.com/unifi/cloud-gateways/uxg-fiber prints "PoE Budget = 30W", "Max. PoE Wattage per Port by PSE = PoE+ 30W" and "Voltage Range PoE Mode = 50-57V"; store.ui.com/us/en/products/uxg-fiber (displaySku "UXG-Fiber (30W)") says "Integrated 4-port switch with (1) PoE+ port". The row carried neither poe-pse nor a budget, so `show power inline` answered "% No PoE on GW: no port on this device can supply power" and the allocator skipped it.

The vendor does not number the PoE+ port, so eth0 carries it - the same placement convention as devices/ubiquiti/ucg-fiber.json, the Cloud Gateway Fiber twin which records the identical 30 W / one-PoE+ census. One 802.3at port at its 30 W ceiling exactly consumes the budget, so it never binds above a single full-power AP.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 16:00:51 +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!2175
No description provided.