devices(ubiquiti): the EdgeRouter PoE routers source 44 W and 40 W and declared neither #2135

Merged
jaylouisw merged 1 commit from catalogue/1119-1022 into main 2026-11-19 10:40:59 +00:00
Owner

Refs #130. This does not answer the Dream Wall Pro request: the Pro's vendor surfaces are still empty when re-measured today (techspecs.ui.com/unifi/cloud-gateways/udw-pro -> 307, 1 byte, landing on the 609,911-byte front page; the cloud-gateway index 610,412 B with zero udw-pro cards; store.ui.com/us/en/products/udw-pro 404). No UDW-PRO spec is written.

What this does: the two EdgeRouter PoE routers in the same fallback family

devices/ubiquiti/er-6p.json and devices/ubiquiti/er-12p.json carried poeOut on 5 and 10 copper ports with no poe.budgetW. engine/simulator.js:2561 opens computePoe() with if (!dev.poeBudget) continue;, so those ports were not "unknown" - they were skipped, and show power inline said nothing while the ports could power nothing. That is the exact failure #130 found on the UDW.

spec ports budget vendor's operands (read 2026-11-19)
er-6p.json 5 passive 44 W 60 W external adapter, max consumption 16 W (excluding PoE output); per port 24 W (24 V, 1 A, 4-pair) / 12 W (24 V, 0.5 A, 2-pair)
er-12p.json 10 passive 40 W 60 W adapter, max consumption 20 W (excludes PoE output); per port 17 W (24 V), 2-pair only

Neither page prints a "PoE budget" row. The figures are the arithmetic of the stated configuration (adapter minus device draw), and poe.note says so in as many words, keeps the per-port ceilings, and tells a lab with a larger in-range supply to declare its own.

Sources

Two traps recorded in research/ubiquiti-edgerouter-poe-census.md: dl.ui.com/ds/er-6p_ds.pdf and .../er-12p_ds.pdf answer 302 to the techspecs root, and dl.ui.com/qig/er-6p/ is a 6,176-byte iframe shell rather than a quick-start PDF - so every figure above is tech-spec-only, not datasheet-backed.

Also corrected

  • poeOutClass was PoE on ports the vendor calls 24 V passive; it is now passive (an 802.3af claim is 48 V and would invite a PD that cannot run).
  • er-12p.json declared "speedCaps": ["1G", "100M"] - strings where the schema wants Mbps, and missing the 10M the vendor prints: now [10, 100, 1000] on all ten ports.

Gates

  • node scripts/syntax-check.js - 448 files, all OK
  • node scripts/audit-port-types.js - "No port contradicts its declared type."
  • node scripts/audit-poe-budget.js - silent PSEs 106 -> 104; orphan budgets 0
  • node test/hardware-invariants.test.js - 26 passed, 0 failed
  • node test/poe.test.js - 18 passed, 0 failed
  • importer capability tripwire (dry run over both specs) - "Would add: 2 duplicates: 0 rejected: 0"; no capability dropped
  • node scripts/run-tests.js - 369 suites, 12,572 assertions, 0 failed
  • node scripts/regen-registry-doc.js - registry current, no diff
Refs #130. This does not answer the Dream Wall Pro request: the Pro's vendor surfaces are still empty when re-measured today (`techspecs.ui.com/unifi/cloud-gateways/udw-pro` -> 307, 1 byte, landing on the 609,911-byte front page; the cloud-gateway index 610,412 B with zero `udw-pro` cards; `store.ui.com/us/en/products/udw-pro` 404). No UDW-PRO spec is written. ## What this does: the two EdgeRouter PoE routers in the same fallback family `devices/ubiquiti/er-6p.json` and `devices/ubiquiti/er-12p.json` carried `poeOut` on 5 and 10 copper ports with **no `poe.budgetW`**. `engine/simulator.js:2561` opens `computePoe()` with `if (!dev.poeBudget) continue;`, so those ports were not "unknown" - they were skipped, and `show power inline` said nothing while the ports could power nothing. That is the exact failure #130 found on the UDW. | spec | ports | budget | vendor's operands (read 2026-11-19) | |--|--|--|--| | `er-6p.json` | 5 passive | **44 W** | 60 W external adapter, max consumption **16 W (excluding PoE output)**; per port 24 W (24 V, 1 A, 4-pair) / 12 W (24 V, 0.5 A, 2-pair) | | `er-12p.json` | 10 passive | **40 W** | 60 W adapter, max consumption **20 W (excludes PoE output)**; per port **17 W (24 V)**, 2-pair only | Neither page prints a "PoE budget" row. The figures are the arithmetic of the stated configuration (adapter minus device draw), and `poe.note` says so in as many words, keeps the per-port ceilings, and tells a lab with a larger in-range supply to declare its own. ## Sources - <https://techspecs.ui.com/uisp/wired/er-6p> - 200, 582,715 B - <https://techspecs.ui.com/uisp/wired/er-12p> - 200, 575,620 B - <https://store.ui.com/us/en/products/er-6p> - 200, 332,139 B (same table) - <https://store.ui.com/us/en/products/er-12p> - 200, 323,284 B Two traps recorded in `research/ubiquiti-edgerouter-poe-census.md`: `dl.ui.com/ds/er-6p_ds.pdf` and `.../er-12p_ds.pdf` answer 302 to the techspecs root, and `dl.ui.com/qig/er-6p/` is a 6,176-byte iframe shell rather than a quick-start PDF - so every figure above is tech-spec-only, not datasheet-backed. ## Also corrected - `poeOutClass` was `PoE` on ports the vendor calls **24 V passive**; it is now `passive` (an 802.3af claim is 48 V and would invite a PD that cannot run). - `er-12p.json` declared `"speedCaps": ["1G", "100M"]` - strings where the schema wants Mbps, and missing the 10M the vendor prints: now `[10, 100, 1000]` on all ten ports. ## Gates - `node scripts/syntax-check.js` - 448 files, all OK - `node scripts/audit-port-types.js` - "No port contradicts its declared type." - `node scripts/audit-poe-budget.js` - silent PSEs **106 -> 104**; orphan budgets 0 - `node test/hardware-invariants.test.js` - 26 passed, 0 failed - `node test/poe.test.js` - 18 passed, 0 failed - importer capability tripwire (dry run over both specs) - "Would add: 2 duplicates: 0 rejected: 0"; no capability dropped - `node scripts/run-tests.js` - 369 suites, 12,572 assertions, 0 failed - `node scripts/regen-registry-doc.js` - registry current, no diff
devices(ubiquiti): ER-6P and ER-12P source 44 W and 40 W and declared neither (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 11s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Docker build (pull_request) Successful in 21s
CI / Arm auto-merge (pull_request) Successful in 4s
6bf26791ef
Both EdgeRouter PoE routers carried poeOut on every copper port with no
poe.budgetW, so engine/simulator.js skipped them entirely: the ports were not
reported unknown, they were passed over and could power nothing.

Vendor figures, read 2026-11-19:
- techspecs.ui.com/uisp/wired/er-6p 200, 582,715 B
- techspecs.ui.com/uisp/wired/er-12p 200, 575,620 B
- store.ui.com/us/en/products/er-6p, er-12p corroborate the same tables

Neither page prints a total PoE budget. What they print is the included 60 W
(24 V, 2.5 A) adapter, max consumption excluding PoE output (16 W / 20 W), and
a per-port ceiling (24 W 4-pair / 12 W 2-pair; 17 W). The budgets recorded are
that arithmetic - 44 W and 40 W - labelled as derived in poe.note, with the
per-port ceilings kept alongside.

Also: port classes were PoE (an 802.3af 48 V claim) on ports the vendor calls
24 V passive; ER-12P speedCaps were strings and omitted the vendor's 10M rate.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 10:31:52 +00:00
jaylouisw deleted branch catalogue/1119-1022 2026-11-19 10:41:01 +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!2135
No description provided.