devices(tp-link): wall-plate PoE passthrough watts (EAP235-Wall, EAP615-Wall) #2441
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!2441
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1121-1522"
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 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: truebit and no wattage.poeDraw()bills 1 W for it,parsePoeBudget()finds nothing, andshow power inlineon either AP answered:After this PR, the same lab (C1000-8P uplink, Axis M3086-V on the passthrough jack) reads:
Sources (tp-link.com US pages, HTTP 200, crawler user-agent, read 2026-11-21):
PoE Out · PoE Passthrough (Pins 1,2+; 3,6-) · PoE Out (requires 802.3at PoE input and the maximum output is 13 W)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: eth3poeOut: 13,poe.budgetW: 13.devices/tp-link/eap615-wall.json: eth3poeOut: 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.budgetWis 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 bothpoe.notefields and the descriptions rather than left implicit — it wants a schema field before the engine can refuse it.poeInis left at the 12.95 W class-3 allowance, which is what each AP draws with the passthrough off.Sibling left alone.
EAP225-Wallstays on the silent list: its page prints only9W or 25.5W including PoE Outand 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 zeroudw-pro.