devices(ubiquiti): the Mobile Router Industrial sources 10 W it never declared, and sinks 12.5 W not 12.95 #2132

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

Refs #130.

The Dream Wall Pro that #130 asks for still has no Ubiquiti source: techspecs.ui.com/unifi/cloud-gateways/udw-pro lands on the 609,911-byte front page, store.ui.com/us/en/products/udw-pro is 404, the cloud-gateway index still carries only the udw card, and no dl.ui.com/ds spelling resolves. Nothing is modelled from the non-Pro UDW and the issue stays open.

What this pass fixed is the last row in the family a requester of that lab ("NAT, DHCP, VPN, cellular WAN") is actually handed: devices/ubiquiti/umr-industrial.json, the third and final mobile router. Both defects are the ones #2128 fixed on the UMR, one field further along.

field was vendor (tech-spec, 2026-11-19) now
poe.budgetW absent - simulator.js opens its allocator with if (!dev.poeBudget) continue;, so the PSE was skipped and show power inline said nothing "(1) PoE output (Max. 10W, requires PoE+ switch)" 10 W
eth0.poeIn 12.95 (the 802.3af class-0 ceiling, which no Ubiquiti page prints) "Max. Power Consumption 12.5W", "Power Method PoE+ (48-54V DC)" 12.5 W

Capabilities gain 802.3at (the vendor writes "PoE+" and never prints an IEEE number - zero 802.3 occurrences in 693,659 bytes - so the token is recorded as that standard's name, matching umr.json). Aliases gain the vendor SKU UMR-Industrial-US. Ports, speeds and radio rates did not move: 2x GbE RJ45 + LTE Cat 4 + WiFi 4 (2x2, 300 Mbps).

Sources read

URL result
https://techspecs.ui.com/unifi/integrations/umr-industrial-us 200, 693,659 B - Networking Interface, PoE Interface, Max. Power Consumption 12.5W, Power Method, MIMO 2x2 / 802.11n 300 Mbps
https://techspecs.ui.com/unifi/integrations/umr-industrial 200, same 693,659 B - the -us suffix is not required here, unlike the UMR
https://dl.ui.com/ds/umr-industrial_ds.pdf, .../umr-industrial-us_ds.pdf, .../umr_industrial_ds.pdf all 200 with the 609,911-byte techspecs front page - no datasheet, so 10 W is tech-spec-only
https://store.ui.com/us/en/products/umr-industrial-us 200 after redirect into its collection, 589,389 B

Traps recorded in research/ubiquiti-mobile-router-census.md: the missing datasheet above, and that neither surface numbers the PoE ports - only that there is one of each - so eth0 sinks and eth1 sources, the same stated-count convention as umr.json and devices/zyxel/gs1900-24ep.json.

Gates

node scripts/syntax-check.js                 Syntax-checked 447 files: all OK
node scripts/audit-port-types.js             No port contradicts its declared type.
node scripts/audit-poe-budget.js             silent PSEs 107 -> 106 (this row cleared)
node scripts/regen-registry-doc.js --check   2,356 models / 258 vendors - current
test/hardware-invariants.test.js             26 passed, 0 failed
test/poe-inference.test.js                   17 passed, 0 failed
test/poe-agreement.test.js                   17 passed, 0 failed
test/poe.test.js                             18 passed, 0 failed
test/import-devices-capabilities.test.js     34 passed, 0 failed
test/importer-roundtrip.test.js              26 passed, 0 failed
test/catalogue-hygiene.test.js               25 passed, 0 failed
test/capability-vocabulary.test.js           13 passed, 0 failed
test/request-queue.test.js                   32 passed, 0 failed

Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options - the whole census. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json), UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) or UniFi Mobile Router (devices/ubiquiti/umr.json) was meant.

Refs #130. The Dream Wall **Pro** that #130 asks for still has no Ubiquiti source: `techspecs.ui.com/unifi/cloud-gateways/udw-pro` lands on the 609,911-byte front page, `store.ui.com/us/en/products/udw-pro` is 404, the cloud-gateway index still carries only the `udw` card, and no `dl.ui.com/ds` spelling resolves. Nothing is modelled from the non-Pro UDW and the issue stays open. What this pass fixed is the last row in the family a requester of that lab (*"NAT, DHCP, VPN, cellular WAN"*) is actually handed: `devices/ubiquiti/umr-industrial.json`, the third and final mobile router. Both defects are the ones #2128 fixed on the UMR, one field further along. | field | was | vendor (tech-spec, 2026-11-19) | now | |---|---|---|---| | `poe.budgetW` | absent - `simulator.js` opens its allocator with `if (!dev.poeBudget) continue;`, so the PSE was skipped and `show power inline` said nothing | "(1) PoE output (Max. 10W, requires PoE+ switch)" | **10 W** | | `eth0.poeIn` | 12.95 (the 802.3af class-0 ceiling, which no Ubiquiti page prints) | "Max. Power Consumption **12.5W**", "Power Method **PoE+ (48-54V DC)**" | **12.5 W** | Capabilities gain `802.3at` (the vendor writes "PoE+" and never prints an IEEE number - zero `802.3` occurrences in 693,659 bytes - so the token is recorded as that standard's name, matching `umr.json`). Aliases gain the vendor SKU `UMR-Industrial-US`. Ports, speeds and radio rates did not move: 2x GbE RJ45 + LTE Cat 4 + WiFi 4 (2x2, 300 Mbps). ## Sources read | URL | result | |---|---| | `https://techspecs.ui.com/unifi/integrations/umr-industrial-us` | **200**, 693,659 B - Networking Interface, PoE Interface, Max. Power Consumption 12.5W, Power Method, MIMO 2x2 / 802.11n 300 Mbps | | `https://techspecs.ui.com/unifi/integrations/umr-industrial` | **200**, same 693,659 B - the `-us` suffix is *not* required here, unlike the UMR | | `https://dl.ui.com/ds/umr-industrial_ds.pdf`, `.../umr-industrial-us_ds.pdf`, `.../umr_industrial_ds.pdf` | all **200** with the **609,911-byte techspecs front page** - no datasheet, so 10 W is tech-spec-only | | `https://store.ui.com/us/en/products/umr-industrial-us` | 200 after redirect into its collection, 589,389 B | Traps recorded in `research/ubiquiti-mobile-router-census.md`: the missing datasheet above, and that neither surface numbers the PoE ports - only that there is one of each - so `eth0` sinks and `eth1` sources, the same stated-count convention as `umr.json` and `devices/zyxel/gs1900-24ep.json`. ## Gates ``` node scripts/syntax-check.js Syntax-checked 447 files: all OK node scripts/audit-port-types.js No port contradicts its declared type. node scripts/audit-poe-budget.js silent PSEs 107 -> 106 (this row cleared) node scripts/regen-registry-doc.js --check 2,356 models / 258 vendors - current test/hardware-invariants.test.js 26 passed, 0 failed test/poe-inference.test.js 17 passed, 0 failed test/poe-agreement.test.js 17 passed, 0 failed test/poe.test.js 18 passed, 0 failed test/import-devices-capabilities.test.js 34 passed, 0 failed test/importer-roundtrip.test.js 26 passed, 0 failed test/catalogue-hygiene.test.js 25 passed, 0 failed test/capability-vocabulary.test.js 13 passed, 0 failed test/request-queue.test.js 32 passed, 0 failed ``` **Still missing for the Pro, unchanged:** its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options - the whole census. **Unblock, unchanged:** any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming `UDW-PRO`, or the requester confirming that the UDW (`devices/ubiquiti/udw.json`), UDM-Pro (`devices/ubiquiti/UDM-Pro.json`), UDR-5G-Max (`devices/ubiquiti/udr-5g-max.json`) or UniFi Mobile Router (`devices/ubiquiti/umr.json`) was meant.
devices(ubiquiti): the Mobile Router Industrial sources 10 W it never declared, and sinks 12.5 W not 12.95
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Docker build (pull_request) Successful in 16s
CI / Arm auto-merge (pull_request) Successful in 4s
c569bbf0c5
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 09:57:20 +00:00
jaylouisw deleted branch catalogue/1119-0952 2026-11-19 10:11:08 +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!2132
No description provided.