poe(fs): the PI35A-1 injector supplies 30 W, so say so #2448

Merged
jaylouisw merged 1 commit from catalogue/1121-1622 into main 2026-11-21 16:38:18 +00:00
Owner

Refs #130 (not Fixes: the UDW-Pro itself is still unpublished).

2026-11-21 16:2x UTC — the Pro is unchanged; this increment gave the FS PI35A-1 injector the 30 W it was refusing to name. 13 -> 12 on audit-poe-budget's silent list.

Re-measured this run: https://techspecs.ui.com/unifi/cloud-gateways/udw-pro -> 307, 1 byte (Location: https://techspecs.ui.com/); https://store.ui.com/us/en/products/udw-pro -> 404, 213,322 B; https://dl.ui.com/ds/udw_pro_ds.pdf -> 302 -> techspecs.ui.com. Nothing has appeared.

Why this device. With the only open device-request permanently blocked on a SKU Ubiquiti does not sell, the pass took the next name on scripts/audit-poe-budget.js's silent list (13 devices that source PoE and cannot say how much): a single-port injector is the smallest possible census and the one a Dream Wall lab uses to power a camera off a dumb switch port.

The defect. devices/fs/pi35a-1.json shipped poeOut: true on its output jack and no poe block, so Device fell through to the model-name parser, found nothing in PI35A-1, and show power inline printed Supplied: not measured over one row, then "budget not modelled on FS PI35A-1 PoE injector-d1: the ports are reported, the power they could supply is not".

Measured before, with a 32 W RUCKUS R770 cabled to poe: the AP came up powered (poeBudget 0, source name), i.e. an injector with a 30 W ceiling powered a load above it and said nothing.

The vendor page. https://resource.fs.com/mall/file/datasheet/single-port-101001000m-gigabit-poe-injector.pdf (HTTP 200, 551,064 B, 3 pp, text layer, read 2026-11-21), p.2 is a three-model table. Its text layer run-order does not align with its columns, so the cells were read by x-position against the header row (PSM-CW6AP x=210.2, PI18A-1 x=342.0, PI35A-1 x=463.8):

row PSM-CW6AP PI18A-1 PI35A-1
PoE Standards IEEE 802.3af/at IEEE 802.3af IEEE 802.3af/at
Total Power 30W 18W 35W
PoE Port Power 30W 15.4W 30W

The 35 W is the injector's own adapter rating (Input Voltage 100-240VAC, 50/60Hz, 0.56A Max, Output Voltage 52V DC), not a figure a cable can carry, so the budget is the port ceiling, 30 W — the other 5 W is conversion loss. Reading the row as a single run would have given PI35A-1 15.4 W (the af model's column) or 35 W (the adapter), which is why the cell positions are recorded in the spec's poe.note.

The change. poeOut: 30 / PoE+ on poe, plus poe: { budgetW: 30, standard: "802.3at", sourceUrl: <datasheet>, note: ... }; description and notes now state it is a PSE in its own right, not a passthrough.

Measured after: poeBudget 30, source research, and the same R770 is refused — poe auto power-deny 0.0 ... poe: PSE budget exhausted: 32 W requested, 30 W left. Available/Used/Remaining now print 30.0/0.0/30.0.

Gates. scripts/syntax-check.js -> 541 files, all OK. scripts/audit-port-types.js -> 0 gated, 0 contradicted. scripts/audit-poe-budget.js -> silent 13 -> 12, inferred 0, unknown 25, orphan 0. test/hardware-invariants.test.js -> 26 passed, 0 failed. scripts/audit-devices.js -> 0 hard defects. scripts/check-control-bytes.js -> clean. test/poe.test.js -> 21 passed, 0 failed. scripts/regen-registry-doc.js -> catalogue pages current (2,352 models, 258 vendors), no diff.

Still blocked, unchanged: #130's UDW-Pro. No tech-spec page, no store page, no datasheet; nothing to census. No guess was made.

Refs #130 (not Fixes: the UDW-Pro itself is still unpublished). **2026-11-21 16:2x UTC — the Pro is unchanged; this increment gave the FS PI35A-1 injector the 30 W it was refusing to name. 13 -> 12 on audit-poe-budget's silent list.** Re-measured this run: `https://techspecs.ui.com/unifi/cloud-gateways/udw-pro` -> **307, 1 byte** (`Location: https://techspecs.ui.com/`); `https://store.ui.com/us/en/products/udw-pro` -> **404, 213,322 B**; `https://dl.ui.com/ds/udw_pro_ds.pdf` -> **302 -> techspecs.ui.com**. Nothing has appeared. **Why this device.** With the only open `device-request` permanently blocked on a SKU Ubiquiti does not sell, the pass took the next name on `scripts/audit-poe-budget.js`'s silent list (13 devices that source PoE and cannot say how much): a single-port injector is the smallest possible census and the one a Dream Wall lab uses to power a camera off a dumb switch port. **The defect.** `devices/fs/pi35a-1.json` shipped `poeOut: true` on its output jack and no `poe` block, so `Device` fell through to the model-name parser, found nothing in `PI35A-1`, and `show power inline` printed `Supplied: not measured` over one row, then *"budget not modelled on FS PI35A-1 PoE injector-d1: the ports are reported, the power they could supply is not"*. Measured before, with a **32 W RUCKUS R770** cabled to `poe`: the AP came up **powered** (`poeBudget` 0, source `name`), i.e. an injector with a 30 W ceiling powered a load above it and said nothing. **The vendor page.** `https://resource.fs.com/mall/file/datasheet/single-port-101001000m-gigabit-poe-injector.pdf` (HTTP 200, 551,064 B, 3 pp, text layer, read 2026-11-21), p.2 is a three-model table. Its text layer run-order does not align with its columns, so the cells were read **by x-position** against the header row (PSM-CW6AP x=210.2, PI18A-1 x=342.0, PI35A-1 x=463.8): | row | PSM-CW6AP | PI18A-1 | PI35A-1 | |---|---|---|---| | PoE Standards | IEEE 802.3af/at | IEEE 802.3af | **IEEE 802.3af/at** | | Total Power | 30W | 18W | **35W** | | PoE Port Power | 30W | 15.4W | **30W** | The 35 W is the injector's own adapter rating (Input Voltage 100-240VAC, 50/60Hz, **0.56A Max**, Output Voltage 52V DC), not a figure a cable can carry, so the budget is the **port ceiling, 30 W** — the other 5 W is conversion loss. Reading the row as a single run would have given PI35A-1 15.4 W (the af model's column) or 35 W (the adapter), which is why the cell positions are recorded in the spec's `poe.note`. **The change.** `poeOut: 30` / `PoE+` on `poe`, plus `poe: { budgetW: 30, standard: "802.3at", sourceUrl: <datasheet>, note: ... }`; description and notes now state it is a PSE in its own right, not a passthrough. Measured after: `poeBudget` 30, source `research`, and the same R770 is **refused** — `poe auto power-deny 0.0 ... poe: PSE budget exhausted: 32 W requested, 30 W left`. Available/Used/Remaining now print 30.0/0.0/30.0. **Gates.** `scripts/syntax-check.js` -> 541 files, all OK. `scripts/audit-port-types.js` -> 0 gated, 0 contradicted. `scripts/audit-poe-budget.js` -> silent 13 -> **12**, inferred 0, unknown 25, orphan 0. `test/hardware-invariants.test.js` -> 26 passed, 0 failed. `scripts/audit-devices.js` -> 0 hard defects. `scripts/check-control-bytes.js` -> clean. `test/poe.test.js` -> 21 passed, 0 failed. `scripts/regen-registry-doc.js` -> catalogue pages current (2,352 models, 258 vendors), no diff. **Still blocked, unchanged:** #130's UDW-Pro. No tech-spec page, no store page, no datasheet; nothing to census. No guess was made.
poe(fs): the PI35A-1 injector supplies 30 W, so say so
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Test (Node 20) (pull_request) Successful in 1m2s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 2s
5e617cc856
The FS PI35A-1 shipped poeOut: true with no poe block, so Device fell
through to the model-name parser, found no figure in PI35A-1, and
show power inline answered 'budget not modelled' - measured before: a
32 W RUCKUS R770 cabled to the output jack came up powered, and the
injector printed 'Supplied: not measured' over one row.

The datasheet's p.2 table (3 pp, text layer) has three models in three
columns. Read by cell position, PI35A-1 is the third column: PoE
Standards 'IEEE 802.3af/at', Total Power 35W, PoE Port Power 30W.
The 35 W is the adapter rating (100-240 VAC, 0.56 A max, 52 V DC out),
not a cable figure, so the budget is the 30 W port ceiling.

After: budget 30 W, source research, and the same R770 is refused with
'PSE budget exhausted: 32 W requested, 30 W left'.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 16:29:39 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 16:30:28 +00:00
jaylouisw deleted branch catalogue/1121-1622 2026-11-21 16:38:19 +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!2448
No description provided.