devices(ubiquiti): the ER-X family modelled no PoE, and none of the three cited a source (refs #130) #2138

Merged
jaylouisw merged 1 commit from catalogue/1119-1052 into main 2026-11-19 11:11:17 +00:00
Owner

Refs #130 (does not close it — the Dream Wall Pro is still unbuildable; this is the family the request falls back into).

The request's stated lab is NAT, DHCP, VPN, cellular WAN in a routed topology. The three compact EdgeOS routers below are the cheapest rows a requester is handed for it, and all three had no sourceUrl at all — every port count, rate and power figure in them was unattributed. The two PoE members also modelled no PoE: the ER-X's eth4/PoE Out sourced nothing and its eth0/PoE In was not a PD, so a lab that powered the router from a PoE switch was told it was not powered.

spec was vendor (read 2026-11-19) now
devices/ubiquiti/ER-X.json 5 ports, no source, no PoE Data/PoE Input (1) + Data (3) + Data/PoE Passthrough (1); 5 W max; power method 12 V adapter or 24 V passive PoE; QSG: passthrough ≈23 V 5 W from 24 V PoE in (≈23 V 11 W from a 24 V/2.5 A supply) poeIn: 5 on port1, poeOut: 5 (passive) on port5, poe.budgetW: 5, datasheet + QSG cited
devices/ubiquiti/ER-X-SFP.json 6 ports, no source, no PoE Data/PoE Output (5) + (1) 100/1000 SFP; 12 W/port, 50 W combined, passive 24 V pins 4,5+/7,8-; 24 V 2.5 A adapter only 5 × poeOut: 12 (passive), poe.budgetW: 50, datasheet + tech-spec cited
devices/ubiquiti/edgerouter4.json 4 ports, no source, no PoE claim either way (3) 10/100/1000 RJ45 + (1) 1 Gbps SFP; AC C13, 13 W; the page has no PoE row at all poeIn: false on the three copper ports, tech-spec + store cited

Sources. https://dl.ui.com/datasheets/edgemax/EdgeRouter_X_DS.pdf (200, application/pdf, 3,594,850 B, 7 pp — one PDF, two tables: ER-X p5, ER-X-SFP p6), https://dl.ui.com/guides/edgemax/EdgeRouter_ER-X_QSG.pdf (200, application/pdf, 1,362,583 B, 18 pp — the only place the ER-X passthrough watts are printed), techspecs.ui.com/uisp/wired/{er-x,er-x-sfp,er-4} (200; 575,859 / 582,211 / 575,010 B), store.ui.com/us/en/products/{er-x,er-x-sfp,er-4} (200; 326,228 / 328,876 / 323,081 B).

Traps recorded in research/ubiquiti-edgerouter-poe-census.md:

  • The ER-X tech-spec page prints Metworking interface: (3) 10/100/1000 RJ45 ports (Ubiquiti's typo) and hides the other two ports in its PoE interface row — reading that row alone models a three-port router.
  • The per-port 12 W / combined 50 W rows on that PDF sit under the ER-X-SFP heading; applying them to the ER-X would invent a 50 W budget.
  • dl.ui.com/datasheets/ER-X.pdf, dl.ui.com/qig/er-x/, dl.ubnt.com/datasheets/edgerouterx/ER-X_DS.pdf, .../EdgeRouter_4_DS.pdf and .../EdgeRouter_X_SFP_DS.pdf all answer 200 with the 609,911-byte tech-specs front page — so a 200 proves nothing on that host in either direction (the ER-X has a datasheet, the ER-4 does not).

One thing this pass found and did not fix: er-4.json and edgerouter4.json are the same EdgeRouter 4 under two model strings, both citing the same page. The pair is waived in test/known-issues.json (duplicateLabels, a list that can only shrink), so collapsing it decides which model string labs keep — its own increment. This PR corrects the EdgeRouter-4 row; the two still agree that the box can neither sink nor source power.

Gates. syntax-check.js 449 files OK · audit-port-types.js "No port contradicts its declared type" · audit-poe-budget.js silent PSEs 104 of 405 (2 PSE ports added, 0 added silent; budget-with-no-PSE-port still 0) · hardware-invariants.test.js 26/26 · poe-inference 17/17 · poe 21/21 · poe-agreement 17/17 · poe-allocation-order 26/26 · run-tests.js 370 suites, 12,589 assertions, 0 failed. Registry doc regenerated, no diff.

One earlier attempt on this branch declared poe-pd as a device capability; isPoePd() then gave ports 2–4 a 12.95 W draw each (15 W of phantom PD on a 5 W router), so the token is deliberately absent and the single PD port carries its own figure — the same lesson as #2128.

Refs #130 (does not close it — the Dream Wall Pro is still unbuildable; this is the family the request falls back into). The request's stated lab is *NAT, DHCP, VPN, cellular WAN* in a routed topology. The three compact EdgeOS routers below are the cheapest rows a requester is handed for it, and all three had **no `sourceUrl` at all** — every port count, rate and power figure in them was unattributed. The two PoE members also modelled **no PoE**: the ER-X's `eth4/PoE Out` sourced nothing and its `eth0/PoE In` was not a PD, so a lab that powered the router from a PoE switch was told it was not powered. | spec | was | vendor (read 2026-11-19) | now | |---|---|---|---| | `devices/ubiquiti/ER-X.json` | 5 ports, no source, no PoE | Data/PoE **Input** (1) + Data (3) + Data/PoE **Passthrough** (1); 5 W max; power method 12 V adapter **or 24 V passive PoE**; QSG: passthrough ≈23 V **5 W** from 24 V PoE in (≈23 V 11 W from a 24 V/2.5 A supply) | `poeIn: 5` on port1, `poeOut: 5` (`passive`) on port5, `poe.budgetW: 5`, datasheet + QSG cited | | `devices/ubiquiti/ER-X-SFP.json` | 6 ports, no source, no PoE | Data/PoE **Output** (5) + (1) 100/1000 SFP; **12 W/port, 50 W combined**, passive 24 V pins 4,5+/7,8-; 24 V 2.5 A adapter only | 5 × `poeOut: 12` (`passive`), `poe.budgetW: 50`, datasheet + tech-spec cited | | `devices/ubiquiti/edgerouter4.json` | 4 ports, no source, no PoE claim either way | (3) 10/100/1000 RJ45 + (1) 1 Gbps SFP; **AC C13, 13 W**; the page has no PoE row at all | `poeIn: false` on the three copper ports, tech-spec + store cited | **Sources.** `https://dl.ui.com/datasheets/edgemax/EdgeRouter_X_DS.pdf` (200, `application/pdf`, 3,594,850 B, 7 pp — one PDF, two tables: ER-X p5, ER-X-SFP p6), `https://dl.ui.com/guides/edgemax/EdgeRouter_ER-X_QSG.pdf` (200, `application/pdf`, 1,362,583 B, 18 pp — the only place the ER-X passthrough watts are printed), `techspecs.ui.com/uisp/wired/{er-x,er-x-sfp,er-4}` (200; 575,859 / 582,211 / 575,010 B), `store.ui.com/us/en/products/{er-x,er-x-sfp,er-4}` (200; 326,228 / 328,876 / 323,081 B). **Traps recorded** in `research/ubiquiti-edgerouter-poe-census.md`: - The ER-X tech-spec page prints `Metworking interface: (3) 10/100/1000 RJ45 ports` (Ubiquiti's typo) and hides the other two ports in its `PoE interface` row — reading that row alone models a three-port router. - The per-port `12 W` / `combined 50 W` rows on that PDF sit under the **ER-X-SFP** heading; applying them to the ER-X would invent a 50 W budget. - `dl.ui.com/datasheets/ER-X.pdf`, `dl.ui.com/qig/er-x/`, `dl.ubnt.com/datasheets/edgerouterx/ER-X_DS.pdf`, `.../EdgeRouter_4_DS.pdf` and `.../EdgeRouter_X_SFP_DS.pdf` all answer **200 with the 609,911-byte tech-specs front page** — so a 200 proves nothing on that host in either direction (the ER-X has a datasheet, the ER-4 does not). **One thing this pass found and did not fix:** `er-4.json` and `edgerouter4.json` are the same EdgeRouter 4 under two model strings, both citing the same page. The pair is waived in `test/known-issues.json` (`duplicateLabels`, a list that can only shrink), so collapsing it decides which model string labs keep — its own increment. This PR corrects the `EdgeRouter-4` row; the two still agree that the box can neither sink nor source power. **Gates.** `syntax-check.js` 449 files OK · `audit-port-types.js` "No port contradicts its declared type" · `audit-poe-budget.js` silent PSEs **104 of 405** (2 PSE ports added, 0 added silent; budget-with-no-PSE-port still 0) · `hardware-invariants.test.js` 26/26 · `poe-inference` 17/17 · `poe` 21/21 · `poe-agreement` 17/17 · `poe-allocation-order` 26/26 · `run-tests.js` **370 suites, 12,589 assertions, 0 failed**. Registry doc regenerated, no diff. One earlier attempt on this branch declared `poe-pd` as a device capability; `isPoePd()` then gave ports 2–4 a 12.95 W draw each (15 W of phantom PD on a 5 W router), so the token is deliberately absent and the single PD port carries its own figure — the same lesson as #2128.
devices(ubiquiti): the ER-X family modelled no PoE, and none of the three cited a source (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 5s
3d0af797b8
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 11:02:42 +00:00
jaylouisw deleted branch catalogue/1119-1052 2026-11-19 11:11:18 +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!2138
No description provided.