devices(ubiquiti): the Flex 2.5G made its power inlet a PSE #2391

Merged
jaylouisw merged 1 commit from catalogue/1121-0752 into main 2026-11-21 08:12:22 +00:00
Owner

Refs #130

The Dream Wall Pro request is unchanged and still has no vendor surface. This pass fixed a POE DIRECTION defect on the Flex 2.5G that a lab substituting the UDW would meet: its 10G RJ45 power inlet was modelled as a 15.4 W PSE, and its eight PoE++ outlets as 802.3af.

Defect. devices/ubiquiti/usw-flex-2-5g-8-poe.json declared poe.budgetW: 196 and no PoE direction on any socket. derivePortHardware() (engine/media.js) fills that silence with the 802.3af default on every copper port of a switch whose label says PoE, so all nine copper sockets reported 15.4 W out - web/faceplate.js prints PoE out 15.4 W, web/app.js prints PSE, 15.4 W out. The eighth and ninth of those sockets are wrong in opposite directions: the outlets are PoE++, and the 10G RJ45 is where the box gets its power.

Source - https://techspecs.ui.com/unifi/switching/usw-flex-2-5g-8-poe (200, 632,312 B, server-rendered), read 2026-11-21:

row value
Port Layout 2.5 GbE RJ45 8 (All PoE++) (2.5G/1G/100M/10M), 10 GbE RJ45 1 (PoE+++) (10G/5G/2.5G/1G/100M), 10G SFP+ 1 (10G/1G)
PoE Ports PoE++ 8
Max. PoE Wattage per Port by PSE PoE 15.4W / PoE+ 32W / PoE++ 64W
Max. PoE Output Up to PoE++ (so the 10G socket is not an output)
Power Method (1) AC/DC adapter (Excluded), (1) PoE+++
Max. Power Consumption 14W (Excluding PoE output) with PoE input
Total PoE Availability PoE+++ input: 76W / PoE++ input: 46W / PoE+ input: 16W / 210W AC adapter input: 196W

The inlet figure is the vendor's own arithmetic, not a standards lookup: 76 W available plus 14 W maximum consumption is exactly the 90 W an 802.3bt Type 4 source must supply. Ubiquiti prints availability, not input draw, so the spec records the derivation in notes.

There is no datasheet text layer for this SKU: https://dl.ui.com/ds/usw-flex-2-5g-8-poe_ds.pdf answers 200 with the 609,911-byte techspecs front page.

Result. 8 x 2.5G RJ45 at poeOut: 64, poeOutClass: "PoE++"; Port 9 (10G RJ45) at poeIn: 90 with no poeOut; the SFP+ cage neither sources nor sinks; capabilities gain poe-pse, 802.3af, 802.3at, 802.3bt; the 196 W AC-adapter budget is unchanged. New test/usw-flex-2-5g-poe-census.test.js (27 checks) pins the census, checks the engine no longer reports a PSE on Port 9, powers a 22 W U6 Enterprise on Port 1, and shows a 90 W upstream port charging the inlet in full.

Gates. scripts/syntax-check.js 519 files OK; scripts/audit-port-types.js 0 offending ports; scripts/import-devices.js capability tripwire clean; test/hardware-invariants.test.js 26/0; test/spec-vs-description.test.js 3/0; test/poe-inference.test.js 19/0; test/poe.test.js 21/0; docs/CONNECTORS.md regenerated (977 port shapes, was 976).

Blocker on #130, unchanged: the whole UDW-PRO census - RJ45/SFP+ counts and rates, which are WAN, PoE class mix and budget, drive bays, cellular options. techspecs.ui.com/unifi/cloud-gateways/udw-pro -> 307 Location: /; store.ui.com/us/en/products/udw-pro -> 404. No spec written.

Refs #130 The Dream Wall Pro request is unchanged and still has no vendor surface. This pass fixed a POE DIRECTION defect on the Flex 2.5G that a lab substituting the UDW would meet: its 10G RJ45 power inlet was modelled as a 15.4 W PSE, and its eight PoE++ outlets as 802.3af. **Defect.** `devices/ubiquiti/usw-flex-2-5g-8-poe.json` declared `poe.budgetW: 196` and no PoE direction on any socket. `derivePortHardware()` (`engine/media.js`) fills that silence with the 802.3af default on every copper port of a switch whose label says PoE, so all nine copper sockets reported 15.4 W out - `web/faceplate.js` prints `PoE out 15.4 W`, `web/app.js` prints `PSE, 15.4 W out`. The eighth and ninth of those sockets are wrong in opposite directions: the outlets are PoE++, and the 10G RJ45 is where the box *gets* its power. **Source** - `https://techspecs.ui.com/unifi/switching/usw-flex-2-5g-8-poe` (200, 632,312 B, server-rendered), read 2026-11-21: | row | value | |---|---| | Port Layout | `2.5 GbE RJ45 8 (All PoE++) (2.5G/1G/100M/10M)`, `10 GbE RJ45 1 (PoE+++) (10G/5G/2.5G/1G/100M)`, `10G SFP+ 1 (10G/1G)` | | PoE Ports | `PoE++ 8` | | Max. PoE Wattage per Port by PSE | `PoE 15.4W / PoE+ 32W / PoE++ 64W` | | Max. PoE Output | `Up to PoE++` (so the 10G socket is not an output) | | Power Method | `(1) AC/DC adapter (Excluded), (1) PoE+++` | | Max. Power Consumption | `14W (Excluding PoE output) with PoE input` | | Total PoE Availability | `PoE+++ input: 76W / PoE++ input: 46W / PoE+ input: 16W / 210W AC adapter input: 196W` | The inlet figure is the vendor's own arithmetic, not a standards lookup: 76 W available plus 14 W maximum consumption is exactly the 90 W an 802.3bt Type 4 source must supply. Ubiquiti prints availability, not input draw, so the spec records the derivation in `notes`. There is no datasheet text layer for this SKU: `https://dl.ui.com/ds/usw-flex-2-5g-8-poe_ds.pdf` answers 200 with the 609,911-byte techspecs front page. **Result.** 8 x 2.5G RJ45 at `poeOut: 64`, `poeOutClass: "PoE++"`; Port 9 (10G RJ45) at `poeIn: 90` with no `poeOut`; the SFP+ cage neither sources nor sinks; capabilities gain `poe-pse`, `802.3af`, `802.3at`, `802.3bt`; the 196 W AC-adapter budget is unchanged. New `test/usw-flex-2-5g-poe-census.test.js` (27 checks) pins the census, checks the engine no longer reports a PSE on Port 9, powers a 22 W U6 Enterprise on Port 1, and shows a 90 W upstream port charging the inlet in full. **Gates.** `scripts/syntax-check.js` 519 files OK; `scripts/audit-port-types.js` 0 offending ports; `scripts/import-devices.js` capability tripwire clean; `test/hardware-invariants.test.js` 26/0; `test/spec-vs-description.test.js` 3/0; `test/poe-inference.test.js` 19/0; `test/poe.test.js` 21/0; `docs/CONNECTORS.md` regenerated (977 port shapes, was 976). **Blocker on #130, unchanged:** the whole UDW-PRO census - RJ45/SFP+ counts and rates, which are WAN, PoE class mix and budget, drive bays, cellular options. `techspecs.ui.com/unifi/cloud-gateways/udw-pro` -> 307 `Location: /`; `store.ui.com/us/en/products/udw-pro` -> 404. No spec written.
devices(ubiquiti): the Flex 2.5G made its power inlet a PSE
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke and Docker build (pull_request) Successful in 24s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Test (Node 20) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 5s
e1d2ded1c1
USW-Flex-2.5G-8-PoE declared a 196 W budget and no PoE direction on any of
its ten sockets. derivePortHardware() fills that silence with the 802.3af
default on every copper port of a box whose label says PoE, so all nine
copper sockets reported 15.4 W out - including the 10G RJ45, which is the
switch's power INLET.

Ubiquiti's tech-spec table (https://techspecs.ui.com/unifi/switching/usw-flex-2-5g-8-poe,
200, 632,312 B) prints "2.5 GbE RJ45 8 (All PoE++)", "PoE Ports PoE++ 8",
"Max. PoE Wattage per Port by PSE PoE 15.4W / PoE+ 32W / PoE++ 64W" and
"Max. PoE Output Up to PoE++", so the eight outlets now declare the vendor's
64 W PSE ceiling and the PoE++ class word. The same rows list the 10G RJ45 as
"(PoE+++)" beside "Power Method (1) AC/DC adapter (Excluded), (1) PoE+++"
and "Power Input Method DC Input / PoE", so it declares poeIn and no poeOut.
The 90 W is the vendor's arithmetic, not a standard lookup: "PoE+++ input:
76W" available plus "14W ... with PoE input" maximum consumption is exactly
the 90 W a Type 4 source must supply.

No datasheet text layer exists for this SKU - dl.ui.com/ds/usw-flex-2-5g-8-poe_ds.pdf
answers 200 with the 609,911-byte techspecs front page.

Refs #130
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 07:57:58 +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!2391
No description provided.