devices(ubiquiti): the mobile routers billed 10 W of passthrough as 1 W (#130) #2411

Merged
jaylouisw merged 1 commit from catalogue/1121-1052 into main 2026-11-21 11:38:49 +00:00
Owner

Refs #130 — no closing keyword: the UDW-PRO census is still unpublished. This increment is the same PoE defect class #2404/#2407 fixed on the Dream Wall and five cloud gateways, left standing on the two mobile routers.

The defect: devices/ubiquiti/umr.json (rj45-2) and devices/ubiquiti/umr-industrial.json (eth1) carried poeOut: true beside a poe.budgetW of 10 W whose own note quotes Ubiquiti's line. Device.poeDraw() adds iface.poeOut into its watt total, so true bills 1 W; pseDraw() sums the same field against the 10 W budget, so a 9 W camera on the passthrough was priced at 1 W and the budget could never bind. Both sockets now say poeOut: 10.

Evidence (server-rendered tech-spec table, read 2026-11-21):

The class stays PoE+ because that is the upstream feed the passthrough requires; the 10 W is a passthrough cap well below the PoE+ class ceiling, so the two fields deliberately disagree (stated in both notes).

Trap recorded in both specs: /unifi/cloud-gateways/umr and /umr-industrial answer 307 to /, which is why an earlier pass left these rows alone — the live pages are under /unifi/integrations/ with the -us suffix. The UDW-PRO probe is unchanged: techspecs.ui.com/unifi/cloud-gateways/udw-pro -> 307/1 byte, store.ui.com/us/en/products/udw-pro -> 404.

Gates: syntax-check 527 files OK; audit-port-types 0 gated; import-devices --dry-run clean (one unrelated mikrotik capability warning, pre-existing); hardware-invariants 26/26; regen-registry-doc current (2,352 models); --filter=ubiquiti 8 suites / 615 assertions, --filter=poe 29 / 919, full suite 447 suites / 15,149 assertions, 0 failed. New test/ubiquiti-mobile-router-pse.test.js, 24 assertions incl. poeDraw() after cabling a powered device to each passthrough.

Refs #130 — no closing keyword: the UDW-PRO census is still unpublished. This increment is the same PoE defect class #2404/#2407 fixed on the Dream Wall and five cloud gateways, left standing on the two mobile routers. The defect: `devices/ubiquiti/umr.json` (rj45-2) and `devices/ubiquiti/umr-industrial.json` (eth1) carried `poeOut: true` beside a `poe.budgetW` of 10 W whose own note quotes Ubiquiti's line. `Device.poeDraw()` adds `iface.poeOut` into its watt total, so `true` bills **1 W**; `pseDraw()` sums the same field against the 10 W budget, so a 9 W camera on the passthrough was priced at 1 W and the budget could never bind. Both sockets now say `poeOut: 10`. Evidence (server-rendered tech-spec table, read 2026-11-21): - https://techspecs.ui.com/unifi/integrations/umr-us — 200, 708,698 B: "PoE Interface (1) PoE input / (1) PoE output (Max. 10W, requires PoE+ switch)" - https://techspecs.ui.com/unifi/integrations/umr-industrial-us — 200, 693,659 B: identical row The class stays `PoE+` because that is the upstream feed the passthrough requires; the 10 W is a passthrough cap well below the PoE+ class ceiling, so the two fields deliberately disagree (stated in both notes). Trap recorded in both specs: `/unifi/cloud-gateways/umr` and `/umr-industrial` answer **307 to `/`**, which is why an earlier pass left these rows alone — the live pages are under `/unifi/integrations/` with the `-us` suffix. The UDW-PRO probe is unchanged: `techspecs.ui.com/unifi/cloud-gateways/udw-pro` -> 307/1 byte, `store.ui.com/us/en/products/udw-pro` -> 404. Gates: syntax-check 527 files OK; audit-port-types 0 gated; import-devices --dry-run clean (one unrelated mikrotik capability warning, pre-existing); hardware-invariants 26/26; regen-registry-doc current (2,352 models); `--filter=ubiquiti` 8 suites / 615 assertions, `--filter=poe` 29 / 919, full suite 447 suites / 15,149 assertions, 0 failed. New `test/ubiquiti-mobile-router-pse.test.js`, 24 assertions incl. `poeDraw()` after cabling a powered device to each passthrough.
devices(ubiquiti): the mobile routers billed 10 W of passthrough as 1 W (#130)
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 27s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 3s
af4a6db2d4
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 10:59:23 +00:00
jaylouisw deleted branch catalogue/1121-1052 2026-11-21 11:38:51 +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!2411
No description provided.