devices(ubiquiti): the UISP Router's eight PoE ports were 802.3af phonies with no budget (refs #130) #2165

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

refs #130 (records the catalogue defect found underneath this request; it does not close it)

#130 asks for a Dream Wall Pro and is still blocked - no Ubiquiti surface names UDW-PRO, and the surfaces were not re-walked this pass (nine exhausted, last measured 13:25 today). It spent the increment on the box a routed lab is handed when the requested gateway does not exist: a router that declares PoE and cannot deliver a watt.

devices/ubiquiti/uisp-r.json - the UISP Router, Ubiquiti's eight-port MicroPoP router - was wrong twice on the same rows:

field before vendor
8 copper ports poeOut: true, poeOutClass: "PoE" (802.3af, 48 V negotiated) "PoE interface (8) 27V passive PoE: 2-pair (pins 4, 5+/7, 8-) or 4-pair (pins 1, 2, 4, 5+/3, 6, 7, 8-)", "Passive PoE voltage range 27V DC"
per-port wattage absent "Max. Passive PoE wattage per port 30W/27V DC"
poe block absent "Power supply 27V DC, 4.4A adapter", "Max. power consumption 10W (Excluding PoE output)"

With no poe block, engine/device.js fell through to parsePoeBudget('UISP-R'), which has no figure in it - budget 0, source name. engine/simulator.js opens computePoe() with if (!dev.poeBudget) continue;, so the box was skipped rather than reported unknown: eight advertised PSE ports, no entry in show power inline, and a MicroPoP router that could not power one airMAX radio while saying nothing about why. Same defect class as er-6p/er-12p (#2135) and the LTE Backup Pro (#2150, still open).

Measured before/after (NBE-5AC-Gen2, 12.95 W PD, on eth4):

poeBudget source PSE ports computePoe()
before 0 name 8 (boolean true, class "PoE") no entry at all - not even a denial
after 108.8 research 8 (30 W each, class passive) powers the radio: 12.95 W of 108.8 W

The budget is derived, and says so. Ubiquiti prints no total PoE row for this SKU. It prints the two figures that bound it: the included adapter is 27 V x 4.4 A = 118.8 W, and the router draws "10W (Excluding PoE output)", leaving 108.8 W for the eight ports. Recorded as a derived ceiling in the same shape as devices/antaira/lmp-1002g-sfp-t.json, with the arithmetic in poe.note; eight ports at the vendor's 30 W would be 240 W, so the adapter - not the port count - is what stops a full fill.

Sources (read 2026-11-19, both Ubiquiti-hosted)

  • https://techspecs.ui.com/uisp/wired/uisp-r - HTTP 200, 583,910 B, title "UISP Router - Tech Specs": "(8) GbE RJ45 ports" + "(1) 1G SFP port", the PoE interface / per-port / voltage rows quoted above, "Supported voltage range 24-28V DC", "Max. power consumption 10W (Excluding PoE output)".
  • https://dl.ui.com/ds/uisp-r_ds.pdf - HTTP 200, application/pdf, 2,635,831 B, 2 pp, text layer: the same rows, plus "(8) 10/100/1000 MbE RJ45 ports" (the 10M rung now in speedCaps).
  • Store record: storefrontProduct(slug:"uisp-r") answers displaySku UISP-R, status Available.

Traps recorded: the datasheet key is hyphenated per SKU - dl.ui.com/ds/uisp_router_ds.pdf answers 302 and store.ui.com/us/en/products/uisp-router answers 404, while .../products/uisp-r and dl.ui.com/ds/uisp-r_ds.pdf both resolve.

Test: test/uisp-r-poe.test.js (new, 15 assertions) pins the port census, the 30 W passive class (and the absence of 802.3af/at), the derived budget with its research source, and that computePoe() now powers a radio cabled to eth4.

Gates: syntax-check 454 OK; audit-port-types clean; audit-poe-budget silent-PSE count 104 -> 103; run-tests 376 suites / 12,765 assertions / 0 failed; check-control-bytes clean; doc citations clean; registry doc unchanged (2,356 models, 29,718 sockets - no model added).

Still missing for #130, unchanged: RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, and the cellular/WAN options. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller record naming UDW-PRO, or the requester confirming they meant the UDW already catalogued at devices/ubiquiti/udw.json.

refs #130 (records the catalogue defect found underneath this request; it does not close it) #130 asks for a Dream Wall Pro and is still blocked - no Ubiquiti surface names `UDW-PRO`, and the surfaces were not re-walked this pass (nine exhausted, last measured 13:25 today). It spent the increment on the box a *routed lab* is handed when the requested gateway does not exist: a router that declares PoE and cannot deliver a watt. `devices/ubiquiti/uisp-r.json` - the UISP Router, Ubiquiti's eight-port MicroPoP router - was wrong twice on the same rows: | field | before | vendor | |---|---|---| | 8 copper ports | `poeOut: true`, `poeOutClass: "PoE"` (802.3af, 48 V negotiated) | "PoE interface **(8) 27V passive PoE**: 2-pair (pins 4, 5+/7, 8-) or 4-pair (pins 1, 2, 4, 5+/3, 6, 7, 8-)", "Passive PoE voltage range **27V DC**" | | per-port wattage | absent | "Max. Passive PoE wattage per port **30W/27V DC**" | | `poe` block | absent | "Power supply **27V DC, 4.4A** adapter", "Max. power consumption **10W** (Excluding PoE output)" | With no `poe` block, `engine/device.js` fell through to `parsePoeBudget('UISP-R')`, which has no figure in it - budget 0, source `name`. `engine/simulator.js` opens `computePoe()` with `if (!dev.poeBudget) continue;`, so the box was **skipped rather than reported unknown**: eight advertised PSE ports, no entry in `show power inline`, and a MicroPoP router that could not power one airMAX radio while saying nothing about why. Same defect class as `er-6p`/`er-12p` (#2135) and the LTE Backup Pro (#2150, still open). **Measured before/after** (NBE-5AC-Gen2, 12.95 W PD, on `eth4`): | | poeBudget | source | PSE ports | computePoe() | |---|---|---|---|---| | before | 0 | `name` | 8 (boolean `true`, class "PoE") | no entry at all - not even a denial | | after | 108.8 | `research` | 8 (30 W each, class `passive`) | powers the radio: 12.95 W of 108.8 W | **The budget is derived, and says so.** Ubiquiti prints no total PoE row for this SKU. It prints the two figures that bound it: the included adapter is 27 V x 4.4 A = 118.8 W, and the router draws "10W (Excluding PoE output)", leaving 108.8 W for the eight ports. Recorded as a derived ceiling in the same shape as `devices/antaira/lmp-1002g-sfp-t.json`, with the arithmetic in `poe.note`; eight ports at the vendor's 30 W would be 240 W, so the adapter - not the port count - is what stops a full fill. **Sources** (read 2026-11-19, both Ubiquiti-hosted) - `https://techspecs.ui.com/uisp/wired/uisp-r` - HTTP 200, 583,910 B, title "UISP Router - Tech Specs": "(8) GbE RJ45 ports" + "(1) 1G SFP port", the PoE interface / per-port / voltage rows quoted above, "Supported voltage range 24-28V DC", "Max. power consumption 10W (Excluding PoE output)". - `https://dl.ui.com/ds/uisp-r_ds.pdf` - HTTP 200, `application/pdf`, 2,635,831 B, 2 pp, text layer: the same rows, plus "(8) 10/100/1000 MbE RJ45 ports" (the 10M rung now in `speedCaps`). - Store record: `storefrontProduct(slug:"uisp-r")` answers `displaySku UISP-R`, `status Available`. Traps recorded: the datasheet key is hyphenated per SKU - `dl.ui.com/ds/uisp_router_ds.pdf` answers 302 and `store.ui.com/us/en/products/uisp-router` answers 404, while `.../products/uisp-r` and `dl.ui.com/ds/uisp-r_ds.pdf` both resolve. **Test:** `test/uisp-r-poe.test.js` (new, 15 assertions) pins the port census, the 30 W passive class (and the absence of 802.3af/at), the derived budget with its `research` source, and that `computePoe()` now powers a radio cabled to `eth4`. **Gates:** syntax-check 454 OK; audit-port-types clean; audit-poe-budget silent-PSE count 104 -> 103; run-tests 376 suites / 12,765 assertions / 0 failed; check-control-bytes clean; doc citations clean; registry doc unchanged (2,356 models, 29,718 sockets - no model added). **Still missing for #130, unchanged:** RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, and the cellular/WAN options. **Unblock, unchanged:** any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller record naming `UDW-PRO`, or the requester confirming they meant the `UDW` already catalogued at `devices/ubiquiti/udw.json`.
devices(ubiquiti): the UISP Router's eight PoE ports were 802.3af phonies with no budget (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 3s
864c3d155d
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 14:37:00 +00:00
jaylouisw deleted branch catalogue/1119-1422 2026-11-19 14:41:22 +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!2165
No description provided.