devices(tp-link): EAP225-Wall passthrough wattage (Refs #130) #2445

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

Refs #130 (refs only - #130 stays open; the UDW-PRO is still unmodelled).

The defect. devices/tp-link/eap225-wall.json advertised a PoE passthrough port as a bare poeOut: true bit with no wattage and no poe block. poeDraw() bills 1 W for it, parsePoeBudget('EAP225-Wall') finds nothing in the name, and show power inline answered "budget not modelled" over a row of not measured - the switch is present, the number is not. It was one of 14 devices on node scripts/audit-poe-budget.js's silent list.

The fix. eth3 is now poeOut: 13 with poeOutClass: "PoE+", and the spec carries poe: { budgetW: 13, standard: "802.3at", sourceUrl, note }. One PSE port, so the device total is the port ceiling.

Evidence - the vendor's own spec table, UK/global page (HTTP 200, 153,844 B, text/html, read 2026-11-21):
https://www.omadanetworks.com/uk/business-networking/omada-wifi-wall-plate/eap225-wall/

  • Interface: "Uplink: 1x 10/100 Mbps Ethernet Port / Downlink: 3x 10/100 Mbps Ethernet Ports (One port supports PoE OUT. The PoE OUT feature requires 802.3at PoE+ input and the maximum output is 13 W.)"
  • Power Supply: "802.3af/802.3at PoE"
  • Max. Power Consumption: "9 watts /25.5 watts (PoE Out Included)"
    https://www.tp-link.com/us/business-networking/omada-sdn-access-point/eap225-wall/v2/ (HTTP 200, 224,096 B, the page in sourceUrl) confirms the same port census and the rates (5 GHz 867 Mbps, 2.4 GHz 300 Mbps) but prints no output wattage - so the 13 W traces to the UK page, which the spec says outright.

Checked, not assumed. 25.5 - 9 = 16.5 W is more than the 13 W the jack may pass, so the 25.5 W row is the 802.3at class-4 ceiling, not a measured sum; the vendor's stated output is what is modelled. The 802.3at precondition (a dead passthrough on an 802.3af uplink) is not expressible in the schema today - poe.budgetW is unconditional - so it is recorded in poe.note and the description rather than hidden. The UK page also marks the model "Product EOL : Replace with EAP235- Wall"; the successor is already catalogued (devices/tp-link/eap235-wall.json, same 13 W figure). No numbers were taken from the sibling - each is quoted from its own page.

Gates: syntax-check.js 540 files OK; audit-port-types.js 0 contradicting; audit-poe-budget.js silent 14 -> 13; import-devices.js --dry-run no new refusals; hardware-invariants.test.js 26 passed / 0 failed; catalogue-hygiene.test.js 25/0; faceplate-catalogue.test.js 14/0; regen-registry-doc.js unchanged (2,352 models).

Refs #130 (refs only - #130 stays open; the UDW-PRO is still unmodelled). **The defect.** `devices/tp-link/eap225-wall.json` advertised a PoE passthrough port as a bare `poeOut: true` bit with no wattage and no `poe` block. `poeDraw()` bills 1 W for it, `parsePoeBudget('EAP225-Wall')` finds nothing in the name, and `show power inline` answered "budget not modelled" over a row of `not measured` - the switch is present, the number is not. It was one of 14 devices on `node scripts/audit-poe-budget.js`'s silent list. **The fix.** `eth3` is now `poeOut: 13` with `poeOutClass: "PoE+"`, and the spec carries `poe: { budgetW: 13, standard: "802.3at", sourceUrl, note }`. One PSE port, so the device total is the port ceiling. **Evidence** - the vendor's own spec table, UK/global page (HTTP 200, 153,844 B, text/html, read 2026-11-21): `https://www.omadanetworks.com/uk/business-networking/omada-wifi-wall-plate/eap225-wall/` - Interface: "Uplink: 1x 10/100 Mbps Ethernet Port / Downlink: 3x 10/100 Mbps Ethernet Ports (One port supports PoE OUT. The PoE OUT feature requires 802.3at PoE+ input **and the maximum output is 13 W**.)" - Power Supply: "802.3af/802.3at PoE" - Max. Power Consumption: "9 watts /25.5 watts (PoE Out Included)" `https://www.tp-link.com/us/business-networking/omada-sdn-access-point/eap225-wall/v2/` (HTTP 200, 224,096 B, the page in `sourceUrl`) confirms the same port census and the rates (5 GHz 867 Mbps, 2.4 GHz 300 Mbps) but prints no output wattage - so the 13 W traces to the UK page, which the spec says outright. **Checked, not assumed.** 25.5 - 9 = 16.5 W is *more* than the 13 W the jack may pass, so the 25.5 W row is the 802.3at class-4 ceiling, not a measured sum; the vendor's stated output is what is modelled. The 802.3at precondition (a dead passthrough on an 802.3af uplink) is not expressible in the schema today - `poe.budgetW` is unconditional - so it is recorded in `poe.note` and the description rather than hidden. The UK page also marks the model "Product EOL : Replace with EAP235- Wall"; the successor is already catalogued (`devices/tp-link/eap235-wall.json`, same 13 W figure). No numbers were taken from the sibling - each is quoted from its own page. **Gates:** `syntax-check.js` 540 files OK; `audit-port-types.js` 0 contradicting; `audit-poe-budget.js` silent 14 -> **13**; `import-devices.js --dry-run` no new refusals; `hardware-invariants.test.js` 26 passed / 0 failed; `catalogue-hygiene.test.js` 25/0; `faceplate-catalogue.test.js` 14/0; `regen-registry-doc.js` unchanged (2,352 models).
devices(tp-link): EAP225-Wall passthrough wattage (Refs #130)
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
a67daad7c3
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 15:56:01 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 16:00:49 +00:00
jaylouisw deleted branch catalogue/1121-1552 2026-11-21 16:08:11 +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!2445
No description provided.