devices(ubiquiti): the EdgeRouter 10X passed power through no port, and drew it on nine (refs #130) #2179

Merged
jaylouisw merged 1 commit from catalogue/1119-1622 into main 2026-11-19 16:37:47 +00:00
Owner

Refs #130

The UDW-PRO itself is still blocked (no Ubiquiti-hosted page, datasheet, QSG, grant, storefront entry or firmware platform names it; the nine surfaces in the issue thread are exhausted and were not re-walked). This PR spends the increment on the routed-lab fallback path the issue's stated lab needs - a router that can be the gateway, NAT/DHCP/VPN - and on the one EdgeRouter row in it that could not pass power.

What was wrong

devices/ubiquiti/er-10x.json (EdgeRouter 10X) declared poe-pse and modelled no sourcing port, so a lab cabling an AP to it got:

ER10X # show power inline
% No PoE on ER10X: no port on this device can supply power

Ubiquiti's tech-spec table prints both sockets: PoE In: (1) 24V passive PoE port, 2-pair (4, 5+; 7, 8-) and PoE Out: (1) 24V passive PoE port, 2-pair (4, 5+; 7, 8-), with Passive PoE output = DC/PoE passthrough and Passive PoE Max. wattage per port = 15W (24V, 0.63A). The store page for the same SKU summarises it: "Gigabit router with a built-in Layer 2 switch, (10) Gigabit RJ45 ports, a PoE input, and PoE passthrough port."

The same silence ran the other way: the row keeps the device-level poe-pd token, so isPoePd() gave all ten copper ports a 12.95 W 802.3af draw - 124.55 W of phantom load on hardware whose supply is a 24 W adapter and whose max consumption is 8 W.

After

probe before after
show power inline (AP on eth9) % No PoE ... no port on this device can supply power Available:15.0(w) Used:13.0(w) Remaining:2.0(w) / eth9 auto on 12.95 W AP
device PD draw 124.55 W over ten ports 8 W on eth0, false on eth1-eth9
PSE ports 0 1 (eth9, 24V passive, 15 W)
poe.budgetW absent 15 (the vendor's per-port ceiling; the one outlet is the whole budget)
speedCaps ["1G","100M"] [1000,100,10] - the vendor says "10/100/1000"

Which socket is which is a convention, not a vendor figure (neither host numbers the PoE pair): inlet on eth0, outlet on eth9 (last port), the same placement as devices/ubiquiti/ER-X.json and devices/ubiquiti/ucg-fiber.json. The count (1 + 1), the class (24V passive), the 15 W ceiling and the 8 W draw are the vendor's.

test/poe-inference.test.js had ER-10X on its PD_ONLY list - which is part of why "sources nothing" survived. It leaves that list and gets a stricter assertion in its place: exactly one outlet (eth9, 15 W) and exactly one inlet (eth0, 8 W), so the ten-port-PSE defect the list was written for is still refused.

Sources (read 2026-11-19)

Trap recorded in notes: this SKU has no datasheet or quick-start - https://dl.ui.com/datasheets/edgemax/EdgeRouter_10X_DS.pdf and https://dl.ui.com/guides/edgemax/EdgeRouter_10X_QSG.pdf both answer 200 with the 609,911-byte techspecs front page, the silent fallback already trapped for ucg-fiber/uxg-pro/er-6p/er-12p. The console port (Management interface = (1) RJ45 serial port) is recorded in notes, not interfaces, per docs/DEVICE_SCHEMA.md.

Gates

  • node scripts/syntax-check.js - 459 files, all OK
  • node scripts/audit-port-types.js - no port contradicts its declared type
  • node scripts/audit-poe-budget.js - 407 PSEs (was 406), 0 budgets with no PSE port
  • node test/hardware-invariants.test.js - 26 passed, 0 failed
  • node scripts/regen-registry-doc.js - catalogue pages current (2,356 models, 29,719 sockets)
  • node scripts/import-devices.js --dry-run - refusal list unchanged from main (two pre-existing duplicate spellings in research/incoming), 0 capability losses
  • node scripts/run-tests.js - 380 suites, 12,863 assertions, 0 failed
Refs #130 The UDW-PRO itself is still blocked (no Ubiquiti-hosted page, datasheet, QSG, grant, storefront entry or firmware platform names it; the nine surfaces in the issue thread are exhausted and were not re-walked). This PR spends the increment on the routed-lab fallback path the issue's stated lab needs - a router that can be the gateway, NAT/DHCP/VPN - and on the one EdgeRouter row in it that could not pass power. ## What was wrong `devices/ubiquiti/er-10x.json` (EdgeRouter 10X) declared `poe-pse` and modelled no sourcing port, so a lab cabling an AP to it got: ER10X # show power inline % No PoE on ER10X: no port on this device can supply power Ubiquiti's tech-spec table prints both sockets: **PoE In: (1) 24V passive PoE port, 2-pair (4, 5+; 7, 8-)** and **PoE Out: (1) 24V passive PoE port, 2-pair (4, 5+; 7, 8-)**, with **Passive PoE output = DC/PoE passthrough** and **Passive PoE Max. wattage per port = 15W (24V, 0.63A)**. The store page for the same SKU summarises it: "Gigabit router with a built-in Layer 2 switch, (10) Gigabit RJ45 ports, a PoE input, and PoE passthrough port." The same silence ran the other way: the row keeps the device-level `poe-pd` token, so `isPoePd()` gave all ten copper ports a 12.95 W 802.3af draw - **124.55 W of phantom load** on hardware whose supply is a 24 W adapter and whose max consumption is 8 W. ## After | probe | before | after | |---|---|---| | `show power inline` (AP on eth9) | `% No PoE ... no port on this device can supply power` | `Available:15.0(w) Used:13.0(w) Remaining:2.0(w)` / `eth9 auto on 12.95 W AP` | | device PD draw | 124.55 W over ten ports | 8 W on eth0, `false` on eth1-eth9 | | PSE ports | 0 | 1 (eth9, 24V passive, 15 W) | | `poe.budgetW` | absent | 15 (the vendor's per-port ceiling; the one outlet is the whole budget) | | `speedCaps` | `["1G","100M"]` | `[1000,100,10]` - the vendor says "10/100/1000" | Which socket is which is a convention, not a vendor figure (neither host numbers the PoE pair): inlet on eth0, outlet on eth9 (last port), the same placement as `devices/ubiquiti/ER-X.json` and `devices/ubiquiti/ucg-fiber.json`. The count (1 + 1), the class (24V passive), the 15 W ceiling and the 8 W draw are the vendor's. `test/poe-inference.test.js` had ER-10X on its `PD_ONLY` list - which is part of why "sources nothing" survived. It leaves that list and gets a stricter assertion in its place: exactly one outlet (`eth9`, 15 W) and exactly one inlet (`eth0`, 8 W), so the ten-port-PSE defect the list was written for is still refused. ## Sources (read 2026-11-19) - https://techspecs.ui.com/uisp/wired/er-10x - HTTP 200, 576,148 B (a real product page, not the 609,911 B fallback) - https://store.ui.com/us/en/products/er-10x - HTTP 200, 323,875 B, same table plus the one-line summary Trap recorded in `notes`: this SKU has **no datasheet or quick-start** - `https://dl.ui.com/datasheets/edgemax/EdgeRouter_10X_DS.pdf` and `https://dl.ui.com/guides/edgemax/EdgeRouter_10X_QSG.pdf` both answer 200 with the 609,911-byte techspecs front page, the silent fallback already trapped for ucg-fiber/uxg-pro/er-6p/er-12p. The console port (**Management interface = (1) RJ45 serial port**) is recorded in `notes`, not `interfaces`, per `docs/DEVICE_SCHEMA.md`. ## Gates - `node scripts/syntax-check.js` - 459 files, all OK - `node scripts/audit-port-types.js` - no port contradicts its declared type - `node scripts/audit-poe-budget.js` - 407 PSEs (was 406), 0 budgets with no PSE port - `node test/hardware-invariants.test.js` - 26 passed, 0 failed - `node scripts/regen-registry-doc.js` - catalogue pages current (2,356 models, 29,719 sockets) - `node scripts/import-devices.js --dry-run` - refusal list unchanged from main (two pre-existing duplicate spellings in research/incoming), 0 capability losses - `node scripts/run-tests.js` - 380 suites, 12,863 assertions, 0 failed
devices(ubiquiti): the EdgeRouter 10X passed power through no port, and drew it on nine (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 12s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Docker build (pull_request) Successful in 35s
CI / Arm auto-merge (pull_request) Successful in 6s
2b1fd02e8a
Ubiquiti's own tech-spec table for the ER-10X prints two PoE sockets - "PoE In: (1) 24V
passive PoE port, 2-pair (4, 5+; 7, 8-)" and "PoE Out: (1) 24V passive PoE port", with
"Passive PoE output = DC/PoE passthrough" and "Passive PoE Max. wattage per port = 15W (24V,
0.63A)". The row modelled neither: it declared `poe-pse` with no port sourcing, so
`show power inline` answered "% No PoE on ER10X: no port on this device can supply power" on
a router whose whole purpose in a small lab is to pass 24V out to one AP.

The same silence ran the other way. The row keeps the device-level `poe-pd` token, and
`isPoePd()` then gave all ten copper ports a 12.95 W 802.3af draw: 124.55 W of phantom load
on hardware whose supply is a 24 W adapter and whose own max consumption is 8 W.

Now: eth0 poeIn 8 (the vendor's max draw), eth1-eth8 poeIn false, eth9 poeOut 15 / passive
with a 15 W budget, all from the same table. speedCaps normalised to [1000,100,10] - the
vendor says "10/100/1000", the row said "1G"/"100M".

test/poe-inference.test.js had ER-10X on its PD_ONLY list, which is where the "sources
nothing" state came from being defended. It leaves that list for its own assertion: one
outlet, one inlet, no ten-port PSE.

Refs #130.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 16:31:58 +00:00
jaylouisw deleted branch catalogue/1119-1622 2026-11-19 16:37:50 +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!2179
No description provided.