devices(ubiquiti): the EdgePoint R6 and R8 could not power the radio they exist for #2206

Merged
jaylouisw merged 1 commit from catalogue/1119-2022 into main 2026-11-19 21:12:21 +00:00
Owner

Refs #130 (does not close — the Dream Wall Pro itself is still without a vendor surface; see the thread).

What this increment found

Two members of the EdgePoint family in devices/ubiquiti/ could not power the airMAX radio they exist for. Same datasheet, two different failures:

spec was now
devices/ubiquiti/ep-r6.json poe-pse claimed, zero PSE ports, no poe block 5 x poeOut: 16.8 passive (eth0–eth4), poe.budgetW 65, poeIn: 7 on eth0, 10M rung
devices/ubiquiti/ep-r8.json poeOut: true, poeOutClass: "PoE" on eth0 and eth1 only — eth0 is the vendor's PoE input port, and "PoE" is 802.3af, which this chassis has nowhere — while eth2–eth7 (five real PSEs) were dry; no poe block; poe-pd missing eth0 poeIn: 40 and no output; eth1–eth2 poeOut: 75.6 passive (54V x 1.4A); eth3–eth7 poeOut: 16.8 passive (24V x 0.7A); poe.budgetW 284; poe-pd declared

With no poe block, engine/simulator.js computePoe() opened with if (!dev.poeBudget) continue; and skipped both boxes — not "unknown", skipped. show power inline had nothing to report and no radio on the tower could be powered by either router.

Budgets are DERIVED, and say so in poe.note with the arithmetic and the PoE-input alternative:

  • EP-R6: 24V DC, 3A = 72 W less 7W (Excludes PoE output) = 65 W (PoE-input path: 33.6 - 7 = 26.6 W)
  • EP-R8: 54V DC, 6A = 324 W less 40W (Excludes PoE output) = 284 W (PoE-input path: 162 - 40 = 122 W)

No 802.3af/at/bt capability is claimed on either: every output row the vendor prints is passive, so a 48 V 802.3 PD will not negotiate.

Evidence

  • https://dl.ui.com/datasheets/edgemax/EdgePoint_DS.pdf — HTTP 200, application/pdf, 6,571,516 B, 12 pp, text layer; page 6 = EP-R6 table, page 7 = EP-R8 table, page 9 = EP-S16 table.
  • https://techspecs.ui.com/uisp/wired/ep-r6 — HTTP 200, 577,753 B, rendered spec table (not the 609,911 B front page).
  • https://techspecs.ui.com/uisp/wired/ep-r8 — HTTP 200, 578,035 B, same rows.

Vendor rows used verbatim: R6 Passive PoE Output (5) 24V / 0.7A, 2-Pair (+4, 5; -7, 8) Passive PoE, eth0 to eth4; R8 Passive PoE Output (2) 54V or 24V / 1.4A, 4-Pair ... eth1 to eth2, (5) 24V / 0.7A, 2-Pair ... eth3 to eth7, Passive PoE Input (2) 54V / 1.5A ... eth0 and PoE In with PoE In is DC Only, No Data.

Deliberately not modelled

The R8 datasheet says two of its eight copper positions are RJ45/SFP combination ports but never says which two, and the QSG keys (qig/ep-r8.pdf, guides/edgemax/EdgePoint_QSG.pdf) all answer 200 with the same 609,911 B front page. The pairing is left undeclared rather than guessed — ten cableable links into eight positions is exactly the bug a guessed comboWith causes. Recorded in research/ubiquiti-edgepoint-poe-census.md.

Tests

test/edgepoint-poe.test.js (new, 31 assertions) pins both rows, both budgets, both PoE-input directions, and that a NBE-5AC-Gen2 cabled to eth4 on the R6 and eth3 on the R8 is powered. test/poe-inference.test.js: EP-R6 leaves the PD_ONLY list — it was put there on the strength of its own description, not the vendor table — and is pinned by its own assertion instead, the way ER-10X was.

Also corrects the EP-S16 row page citations (hardware table is page 9, not page 8), found while re-reading the same PDF.

Gates

syntax-check 466 files OK; audit-port-types clean; audit-devices no hard defects; hardware-invariants 26/0; spec-vs-description 3/0; audit-poe-budget silent PSEs 102 -> 101; run-tests 387 suites / 13,002 assertions, 0 failed; control-bytes clean; doc-citations clean; registry doc current (2,355 models, regenerated, no diff).

Refs #130 (does not close — the Dream Wall Pro itself is still without a vendor surface; see the thread). ## What this increment found Two members of the EdgePoint family in `devices/ubiquiti/` could not power the airMAX radio they exist for. Same datasheet, two different failures: | spec | was | now | |---|---|---| | `devices/ubiquiti/ep-r6.json` | `poe-pse` claimed, **zero PSE ports**, no `poe` block | 5 x `poeOut: 16.8` passive (`eth0`–`eth4`), `poe.budgetW 65`, `poeIn: 7` on `eth0`, `10M` rung | | `devices/ubiquiti/ep-r8.json` | `poeOut: true, poeOutClass: "PoE"` on **eth0 and eth1 only** — `eth0` is the vendor's PoE *input* port, and "PoE" is 802.3af, which this chassis has nowhere — while `eth2`–`eth7` (five real PSEs) were dry; no `poe` block; `poe-pd` missing | `eth0` `poeIn: 40` and no output; `eth1`–`eth2` `poeOut: 75.6` passive (54V x 1.4A); `eth3`–`eth7` `poeOut: 16.8` passive (24V x 0.7A); `poe.budgetW 284`; `poe-pd` declared | With no `poe` block, `engine/simulator.js` `computePoe()` opened with `if (!dev.poeBudget) continue;` and **skipped both boxes** — not "unknown", skipped. `show power inline` had nothing to report and no radio on the tower could be powered by either router. Budgets are DERIVED, and say so in `poe.note` with the arithmetic and the PoE-input alternative: - EP-R6: `24V DC, 3A` = 72 W less `7W (Excludes PoE output)` = **65 W** (PoE-input path: 33.6 - 7 = 26.6 W) - EP-R8: `54V DC, 6A` = 324 W less `40W (Excludes PoE output)` = **284 W** (PoE-input path: 162 - 40 = 122 W) No 802.3af/at/bt capability is claimed on either: every output row the vendor prints is passive, so a 48 V 802.3 PD will not negotiate. ## Evidence - `https://dl.ui.com/datasheets/edgemax/EdgePoint_DS.pdf` — HTTP 200, `application/pdf`, 6,571,516 B, 12 pp, text layer; page 6 = EP-R6 table, page 7 = EP-R8 table, page 9 = EP-S16 table. - `https://techspecs.ui.com/uisp/wired/ep-r6` — HTTP 200, 577,753 B, rendered spec table (not the 609,911 B front page). - `https://techspecs.ui.com/uisp/wired/ep-r8` — HTTP 200, 578,035 B, same rows. Vendor rows used verbatim: R6 `Passive PoE Output (5) 24V / 0.7A, 2-Pair (+4, 5; -7, 8) Passive PoE, eth0 to eth4`; R8 `Passive PoE Output (2) 54V or 24V / 1.4A, 4-Pair ... eth1 to eth2`, `(5) 24V / 0.7A, 2-Pair ... eth3 to eth7`, `Passive PoE Input (2) 54V / 1.5A ... eth0 and PoE In` with `PoE In is DC Only, No Data`. ## Deliberately not modelled The R8 datasheet says two of its eight copper positions are **RJ45/SFP combination** ports but never says which two, and the QSG keys (`qig/ep-r8.pdf`, `guides/edgemax/EdgePoint_QSG.pdf`) all answer 200 with the same 609,911 B front page. The pairing is left undeclared rather than guessed — ten cableable links into eight positions is exactly the bug a guessed `comboWith` causes. Recorded in `research/ubiquiti-edgepoint-poe-census.md`. ## Tests `test/edgepoint-poe.test.js` (new, 31 assertions) pins both rows, both budgets, both PoE-input directions, and that a NBE-5AC-Gen2 cabled to `eth4` on the R6 and `eth3` on the R8 is powered. `test/poe-inference.test.js`: EP-R6 leaves the `PD_ONLY` list — it was put there on the strength of its own description, not the vendor table — and is pinned by its own assertion instead, the way ER-10X was. Also corrects the EP-S16 row page citations (hardware table is page 9, not page 8), found while re-reading the same PDF. ## Gates syntax-check 466 files OK; audit-port-types clean; audit-devices no hard defects; hardware-invariants 26/0; spec-vs-description 3/0; audit-poe-budget silent PSEs 102 -> 101; run-tests 387 suites / 13,002 assertions, 0 failed; control-bytes clean; doc-citations clean; registry doc current (2,355 models, regenerated, no diff).
devices(ubiquiti): the EdgePoint R6 and R8 could not power the radio they exist for (refs #130)
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 8s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 4s
a78372f4a7
Both are outdoor tower routers whose point is that an airMAX radio plugs into them
and is powered by them. From the same datasheet, both were catalogued as boxes that
source nothing:

* EP-R6 declared poe-pse with zero PSE ports. The vendor prints "(5) 24V / 0.7A,
  2-Pair ... Passive PoE, eth0 to eth4" - all five copper ports are PSEs at 16.8 W.
* EP-R8 had the direction inverted: poeOut with class "PoE" (802.3af) on eth0 and
  eth1 only, on hardware with no 802.3 detection anywhere, eth0 being the port the
  vendor lists under PoE *input*. eth2-eth7 - five real PSE ports - were dry.
  eth1-eth2 are 54V or 24V/1.4A (75.6 W), eth3-eth7 24V/0.7A (16.8 W), all passive.

Neither row had a `poe` block, so engine/simulator.js skipped both at
`if (!dev.poeBudget) continue;` and `show power inline` said nothing at all.
Budgets are derived from printed input and draw and say so: 24V x 3A - 7W = 65 W
(EP-R6), 54V x 6A - 40W = 284 W (EP-R8), with the PoE-input alternatives in the
note. EP-R6 leaves test/poe-inference.test.js's PD_ONLY list for the same reason
ER-10X did - the list was built from descriptions that said "PoE-in", not from the
vendor's table - and is pinned in its own assertion instead.

Also corrects the EP-S16 row's page citations: the hardware table is page 9 of the
datasheet, not page 8 (page 8 is the EdgeOS software table). The research note that
is now the family census had the same off-by-one.

Sources: dl.ui.com/datasheets/edgemax/EdgePoint_DS.pdf (200, application/pdf,
6,571,516 B, 12 pp, page 6 = EP-R6, page 7 = EP-R8, page 9 = EP-S16),
techspecs.ui.com/uisp/wired/ep-r6 (200, 577,753 B),
techspecs.ui.com/uisp/wired/ep-r8 (200, 578,035 B). The combo pairing of the R8's
two RJ45/SFP positions is not published, so it is left undeclared rather than
guessed - recorded in research/ubiquiti-edgepoint-poe-census.md.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 20:43:23 +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!2206
No description provided.