devices(tp-link): wall-plate PoE passthrough watts (EAP235-Wall, EAP615-Wall) #2441

Merged
jaylouisw merged 1 commit from catalogue/1121-1522 into main 2026-11-21 15:37:37 +00:00
Owner

Refs #130 only — this does not close the Dream Wall Pro request.

What this fixes. Both Omada wall plates declared a PoE passthrough port with the bare poeOut: true bit and no wattage. poeDraw() bills 1 W for it, parsePoeBudget() finds nothing, and show power inline on either AP answered:

eth3      auto   not measured
budget not modelled on AP1: the ports are reported, the power they could supply is not

After this PR, the same lab (C1000-8P uplink, Axis M3086-V on the passthrough jack) reads:

Available:13.0(w) Used:13.0(w) Remaining:0.0(w)
Interface Admin  Oper       Power   Device
eth3      auto   on         13.0    CAM1

Sources (tp-link.com US pages, HTTP 200, crawler user-agent, read 2026-11-21):

Model URL bytes quote
EAP235-Wall v1.20 https://www.tp-link.com/us/business-networking/omada-wifi-wall-plate/eap235-wall/v1.20/ 188,991 PoE Out · PoE Passthrough (Pins 1,2+; 3,6-) · PoE Out (requires 802.3at PoE input and the maximum output is 13 W)
EAP615-Wall v1 https://www.tp-link.com/us/business-networking/omada-sdn-access-point/eap615-wall/v1/ 230,762 The PoE OUT feature requires 802.3at PoE+ input. The maximum power output for POE pass-through is 13 W (EU version) or 12 W (US version), based on laboratory testing.

devices/tp-link/eap235-wall.json: eth3 poeOut: 13, poe.budgetW: 13. devices/tp-link/eap615-wall.json: eth3 poeOut: 12 (the US figure, since the spec is sourced from the /us/ page), poe.budgetW: 12.

The subtraction that is not used. The EAP235-Wall page also prints 9.8W (PoE Out Not Included) / 24.4W (PoE Out Included). 24.4 - 9.8 = 14.6 W, but only 13 W can leave the jack: the 1.6 W difference is the converter's own loss. The vendor's stated output is modelled, not the subtraction — the same class of error as reading a PSU rating as a PSE ceiling.

Both figures are conditional, and the schema cannot say so. TP-Link states the passthrough exists only when an 802.3at port feeds the AP; on an 802.3af uplink the AP runs (9.8 W / 11.5 W) and the jack is dead. poe.budgetW is unconditional, so a lab that feeds these APs from an 802.3af port will still see 13 W / 12 W allocated on eth3. That is written into both poe.note fields and the descriptions rather than left implicit — it wants a schema field before the engine can refuse it. poeIn is left at the 12.95 W class-3 allowance, which is what each AP draws with the passthrough off.

Sibling left alone. EAP225-Wall stays on the silent list: its page prints only 9W or 25.5W including PoE Out and no maximum output, so the only figure available is an upper bound (16.5 W) that includes the converter's loss. Not modelled from a subtraction.

Gates. node scripts/syntax-check.js — 539 files, all OK. node scripts/audit-port-types.js — 0 contradictions. node scripts/audit-devices.js — 0 hard defects, 0 uncablable ports. node test/hardware-invariants.test.js — 26 passed, 0 failed. node test/poe.test.js — 21 passed. node test/poe-inference.test.js — 21 passed. node scripts/audit-poe-budget.js — silent PSEs 16 → 14.

#130 status. Re-measured at 15:2x UTC: techspecs.ui.com/unifi/cloud-gateways/udw-pro → 307 → / (1 B); store.ui.com/us/en/products/udw-pro → 404 (213,322 B); the gateway index → 200, 610,412 B, still zero udw-pro.

Refs #130 only — this does not close the Dream Wall Pro request. **What this fixes.** Both Omada wall plates declared a PoE *passthrough* port with the bare `poeOut: true` bit and no wattage. `poeDraw()` bills 1 W for it, `parsePoeBudget()` finds nothing, and `show power inline` on either AP answered: ``` eth3 auto not measured budget not modelled on AP1: the ports are reported, the power they could supply is not ``` After this PR, the same lab (C1000-8P uplink, Axis M3086-V on the passthrough jack) reads: ``` Available:13.0(w) Used:13.0(w) Remaining:0.0(w) Interface Admin Oper Power Device eth3 auto on 13.0 CAM1 ``` **Sources** (tp-link.com US pages, HTTP 200, crawler user-agent, read 2026-11-21): | Model | URL | bytes | quote | |---|---|---|---| | EAP235-Wall v1.20 | https://www.tp-link.com/us/business-networking/omada-wifi-wall-plate/eap235-wall/v1.20/ | 188,991 | `PoE Out · PoE Passthrough (Pins 1,2+; 3,6-) · PoE Out (requires 802.3at PoE input and the maximum output is 13 W)` | | EAP615-Wall v1 | https://www.tp-link.com/us/business-networking/omada-sdn-access-point/eap615-wall/v1/ | 230,762 | `The PoE OUT feature requires 802.3at PoE+ input. The maximum power output for POE pass-through is 13 W (EU version) or 12 W (US version), based on laboratory testing.` | `devices/tp-link/eap235-wall.json`: eth3 `poeOut: 13`, `poe.budgetW: 13`. `devices/tp-link/eap615-wall.json`: eth3 `poeOut: 12` (the US figure, since the spec is sourced from the /us/ page), `poe.budgetW: 12`. **The subtraction that is *not* used.** The EAP235-Wall page also prints `9.8W (PoE Out Not Included) / 24.4W (PoE Out Included)`. 24.4 - 9.8 = 14.6 W, but only 13 W can leave the jack: the 1.6 W difference is the converter's own loss. The vendor's stated output is modelled, not the subtraction — the same class of error as reading a PSU rating as a PSE ceiling. **Both figures are conditional, and the schema cannot say so.** TP-Link states the passthrough exists only when an 802.3at port feeds the AP; on an 802.3af uplink the AP runs (9.8 W / 11.5 W) and the jack is dead. `poe.budgetW` is unconditional, so a lab that feeds these APs from an 802.3af port will still see 13 W / 12 W allocated on eth3. That is written into both `poe.note` fields and the descriptions rather than left implicit — it wants a schema field before the engine can refuse it. `poeIn` is left at the 12.95 W class-3 allowance, which is what each AP draws with the passthrough off. **Sibling left alone.** `EAP225-Wall` stays on the silent list: its page prints only `9W or 25.5W including PoE Out` and no maximum output, so the only figure available is an upper bound (16.5 W) that includes the converter's loss. Not modelled from a subtraction. **Gates.** `node scripts/syntax-check.js` — 539 files, all OK. `node scripts/audit-port-types.js` — 0 contradictions. `node scripts/audit-devices.js` — 0 hard defects, 0 uncablable ports. `node test/hardware-invariants.test.js` — 26 passed, 0 failed. `node test/poe.test.js` — 21 passed. `node test/poe-inference.test.js` — 21 passed. `node scripts/audit-poe-budget.js` — silent PSEs 16 → 14. **#130 status.** Re-measured at 15:2x UTC: `techspecs.ui.com/unifi/cloud-gateways/udw-pro` → 307 → `/` (1 B); `store.ui.com/us/en/products/udw-pro` → 404 (213,322 B); the gateway index → 200, 610,412 B, still zero `udw-pro`.
devices(tp-link): wall-plate PoE passthrough watts (EAP235-Wall, EAP615-Wall)
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 1m7s
CI / Test (Node 22) (pull_request) Successful in 1m5s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 4s
139b143298
Both Omada wall plates advertised a passthrough PSE with the bare
poeOut: true bit and no watts, so show power inline answered
'budget not modelled' and poeDraw() billed 1 W per port.

Vendor figures, tp-link.com US pages read 2026-11-21:
- EAP235-Wall v1.20: 'PoE Out (requires 802.3at PoE input and the
  maximum output is 13 W)'; 9.8 W / 24.4 W including PoE Out.
- EAP615-Wall v1: 'The maximum power output for POE pass-through is
  13 W (EU version) or 12 W (US version), based on laboratory testing.'

Refs #130
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 15:29:19 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 15:30:20 +00:00
jaylouisw deleted branch catalogue/1121-1522 2026-11-21 15:37:39 +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!2441
No description provided.