ubiquiti: cite both mobile-router rows and give the UMR its 10 W passthrough budget #2128

Merged
jaylouisw merged 1 commit from catalogue/1119-0922 into main 2026-11-19 09:40:52 +00:00
Owner

Refs #130 — does not close it; the Dream Wall Pro is still absent from Ubiquiti's catalogue.

What was wrong

devices/ubiquiti/umr.json and devices/ubiquiti/umr-ultra.json — the two cellular gateways that answer this request's stated lab need (routing, NAT, DHCP, cellular WAN) — carried no sourceUrl at all: their notes quoted vendor figures with no URL behind them. On top of that the UMR's PoE passthrough port had no poe.budgetW, and engine/simulator.js opens its allocator with if (!dev.poeBudget) continue;, so the port was skipped rather than reported unknown: it could power nothing and show power inline could not say why.

Evidence, read 2026-11-19

surface result what it states
techspecs.ui.com/unifi/integrations/umr-us 200, 708,698 B "(2) GbE RJ45 ports, LTE Cat 4 radio, WiFi 4"; "(1) PoE input / (1) PoE output (Max. 10W, requires PoE+ switch)"; 9 W; PoE+ 48–54 V
dl.ui.com/ds/umr_ds.pdf 200, application/pdf, 597,924 B, 2 pp "(2) GbE RJ45 ports", "(1) PoE in", "(1) PoE output*", "*Requires a PoE+ switch" — no output wattage
store.ui.com/us/en/products/umr-us 307 → collection URL, 200 there, 585,616 B key feature: "PoE+ input required for PoE passthrough."
techspecs.ui.com/unifi/integrations/umr-ultra-us 200, 682,619 B "(2) FE RJ45 ports"; 5.7 W; USB-C 5 V/2 A or 4-pin ATX 9–30 V DC; −30 to 70 °C; Features table has no PoE row
store.ui.com/us/en/products/umr-ultra-us 307 → collection URL, 200 there, 587,964 B second vendor surface for the SKU

The UMR's own two documents disagree on the chassis only (datasheet 220.6 × 89.8 × 28.8 mm, 252/298 g against tech-spec 190 × 89.8 × 28.8 mm, 257/303 g). Ports, the 150 Mbps WiFi 4 rate and the 9 W draw are identical on both, so the row models those and nothing from the disagreement.

Changes

  • umr.json — cites all three surfaces; poe.budgetW: 10 (vendor's "Max. 10W", on the tech-spec page only); poeIn is 9 W instead of true (docs/DEVICE_SCHEMA.md:204 wants watts); capabilities gain poe-pd, poe-pse, 802.3at; aliases carry UMR-US.
  • umr-ultra.json — cites both surfaces; aliases carry UMR-Ultra-US.
  • research/ubiquiti-mobile-router-census.md — the census table and the retrieval traps.

Effect on the box, cabled to a 12.95 W 802.3af camera:

Available:10.0(w) Used:0.0(w) Remaining:10.0(w)
Interface  Admin  Oper  Draw     Powered device
rj45-2     auto   off   12.95 W  CAM1  (denied)
  rj45-2: PSE budget exhausted: 12.95 W requested, 10 W left

The 10 W ceiling is the vendor's, so refusing a 12.95 W class-0 device is the correct answer; what was missing was the number, not the policy.

Traps recorded so nobody re-walks them

  • The -us suffix is part of the slug on both hosts: techspecs.ui.com/unifi/integrations/umr answers the 609,911-byte front page (the silent fallback), and store.ui.com/us/en/products/umr is a 404.
  • /products/umr-ultra 307s to the internet-solutions category — a 200 once followed, but a miss, not a product page.
  • The Ultra has no datasheet: dl.ui.com/ds/umr-ultra_ds.pdf and .../umr-ultra-us_ds.pdf both return the 609,911-byte techspecs front page.
  • Neither surface numbers the PoE ports (one input, one output, no per-port assignment), so rj45-1 sinks and rj45-2 sources on the vendor's stated count, the zyxel/gs1900-24ep.json convention.

Gates

  • node scripts/syntax-check.js → 446 files, all OK
  • node scripts/audit-port-types.js → "No port contradicts its declared type."
  • node scripts/check-control-bytes.js → OK
  • node scripts/import-devices.js --dry-run → no umr/umr-ultra diagnostics (its two rejects are the pre-existing peplink/zte duplicates in research/incoming/)
  • node test/hardware-invariants.test.js → 26 passed, 0 failed
  • node test/poe-inference.test.js, test/poe.test.js, test/device-aliases.test.js, test/capability-vocabulary.test.js → 17 / 18 / 13 / 13 passed
  • node scripts/run-tests.js → 367 suites, 12,468 assertions, 0 failed
  • npm run regen:registry-doc → "The catalogue pages are current: 2,356 models"
Refs #130 — does not close it; the Dream Wall Pro is still absent from Ubiquiti's catalogue. ## What was wrong `devices/ubiquiti/umr.json` and `devices/ubiquiti/umr-ultra.json` — the two cellular gateways that answer this request's stated lab need (routing, NAT, DHCP, **cellular WAN**) — carried **no `sourceUrl` at all**: their `notes` quoted vendor figures with no URL behind them. On top of that the UMR's PoE passthrough port had **no `poe.budgetW`**, and `engine/simulator.js` opens its allocator with `if (!dev.poeBudget) continue;`, so the port was skipped rather than reported unknown: it could power nothing and `show power inline` could not say why. ## Evidence, read 2026-11-19 | surface | result | what it states | |---|---|---| | `techspecs.ui.com/unifi/integrations/umr-us` | 200, 708,698 B | "(2) GbE RJ45 ports, LTE Cat 4 radio, WiFi 4"; "(1) PoE input / (1) PoE output (Max. 10W, requires PoE+ switch)"; 9 W; PoE+ 48–54 V | | `dl.ui.com/ds/umr_ds.pdf` | 200, `application/pdf`, 597,924 B, 2 pp | "(2) GbE RJ45 ports", "(1) PoE in", "(1) PoE output*", "*Requires a PoE+ switch" — **no** output wattage | | `store.ui.com/us/en/products/umr-us` | 307 → collection URL, 200 there, 585,616 B | key feature: "PoE+ input required for PoE passthrough." | | `techspecs.ui.com/unifi/integrations/umr-ultra-us` | 200, 682,619 B | "(2) FE RJ45 ports"; 5.7 W; USB-C 5 V/2 A or 4-pin ATX 9–30 V DC; −30 to 70 °C; Features table has **no** PoE row | | `store.ui.com/us/en/products/umr-ultra-us` | 307 → collection URL, 200 there, 587,964 B | second vendor surface for the SKU | The UMR's own two documents disagree on the chassis only (datasheet 220.6 × 89.8 × 28.8 mm, 252/298 g against tech-spec 190 × 89.8 × 28.8 mm, 257/303 g). Ports, the 150 Mbps WiFi 4 rate and the 9 W draw are identical on both, so the row models those and nothing from the disagreement. ## Changes - `umr.json` — cites all three surfaces; `poe.budgetW: 10` (vendor's "Max. 10W", on the tech-spec page only); `poeIn` is **9 W** instead of `true` (`docs/DEVICE_SCHEMA.md:204` wants watts); capabilities gain `poe-pd`, `poe-pse`, `802.3at`; aliases carry `UMR-US`. - `umr-ultra.json` — cites both surfaces; aliases carry `UMR-Ultra-US`. - `research/ubiquiti-mobile-router-census.md` — the census table and the retrieval traps. Effect on the box, cabled to a 12.95 W 802.3af camera: ``` Available:10.0(w) Used:0.0(w) Remaining:10.0(w) Interface Admin Oper Draw Powered device rj45-2 auto off 12.95 W CAM1 (denied) rj45-2: PSE budget exhausted: 12.95 W requested, 10 W left ``` The 10 W ceiling is the vendor's, so refusing a 12.95 W class-0 device is the correct answer; what was missing was the number, not the policy. ## Traps recorded so nobody re-walks them - The **`-us` suffix is part of the slug** on both hosts: `techspecs.ui.com/unifi/integrations/umr` answers the 609,911-byte front page (the silent fallback), and `store.ui.com/us/en/products/umr` is a 404. - `/products/umr-ultra` **307s to the internet-solutions category** — a 200 once followed, but a miss, not a product page. - The Ultra has **no datasheet**: `dl.ui.com/ds/umr-ultra_ds.pdf` and `.../umr-ultra-us_ds.pdf` both return the 609,911-byte techspecs front page. - Neither surface numbers the PoE ports (one input, one output, no per-port assignment), so `rj45-1` sinks and `rj45-2` sources on the vendor's stated count, the `zyxel/gs1900-24ep.json` convention. ## Gates - `node scripts/syntax-check.js` → 446 files, all OK - `node scripts/audit-port-types.js` → "No port contradicts its declared type." - `node scripts/check-control-bytes.js` → OK - `node scripts/import-devices.js --dry-run` → no `umr`/`umr-ultra` diagnostics (its two rejects are the pre-existing peplink/zte duplicates in `research/incoming/`) - `node test/hardware-invariants.test.js` → 26 passed, 0 failed - `node test/poe-inference.test.js`, `test/poe.test.js`, `test/device-aliases.test.js`, `test/capability-vocabulary.test.js` → 17 / 18 / 13 / 13 passed - `node scripts/run-tests.js` → 367 suites, 12,468 assertions, 0 failed - `npm run regen:registry-doc` → "The catalogue pages are current: 2,356 models"
ubiquiti: cite both mobile-router rows and give the UMR its 10 W passthrough budget
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 8s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
3f8f912eaa
The two cellular gateways a Dream-Wall requester is otherwise handed carried no
sourceUrl at all, and the UMR's PoE output port had no budget - which
engine/simulator.js reads as 'sources nothing', so the passthrough was dead
with no explanation. 10 W and 9 W are both vendor-stated.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 09:33:27 +00:00
jaylouisw deleted branch catalogue/1119-0922 2026-11-19 09:40:53 +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!2128
No description provided.