devices(ubiquiti): the 5G Max modems offered no 5G medium to cable (refs #130) #2159

Merged
jaylouisw merged 1 commit from catalogue/1119-1322 into main 2026-11-19 13:40:50 +00:00
Owner

refs #130 (does not close it - the Dream Wall Pro is still blocked, see the issue)

Two Ubiquiti cellular modems declared their LTE/5G radio as wwan0 at 1G, so engine/media.js resolved the cage to [lte, lte-a] and the 5G NR medium was never offered. A lab asking for the cellular WAN in #130 could not cable either 5G Max as 5G.

row wwan0 before media offered wwan0 now media offered
u5g-max 1G lte, lte-a 3.4G lte, lte-a, 5g-sub6
u5g-max-outdoor 1G lte, lte-a 3.4G lte, lte-a, 5g-sub6
udr-5g-max (same radio, unchanged) 3.4G lte, lte-a, 5g-sub6 3.4G lte, lte-a, 5g-sub6

The figure is the vendor's, not a class ceiling: both pages print 5G NSA Downlink 3.4 Gbps / Uplink 560 Mbps, 5G SA 1.8 Gbps / 650 Mbps, 4G LTE 1.6 Gbps / 210 Mbps - the same table udr-5g-max was already cited for.

Sources read 2026-11-19 (crawler user-agent, text layer of the spec table):

Not touched: u5g stays at 100M. It is 5G RedCap and Ubiquiti publishes no RedCap rate, so the 5G NR medium is still not offered there - recorded in that row's notes rather than guessed at.

Gates: node scripts/syntax-check.js 453 files OK; node scripts/audit-port-types.js no contradiction; test/hardware-invariants.test.js 26/26; test/import-devices-capabilities.test.js pass (no capability moved); test/catalogue-hygiene.test.js and test/faceplate-catalogue.test.js pass; node scripts/regen-registry-doc.js - catalogue pages current (2,356 models, 29,716 sockets), no doc change.

refs #130 (does not close it - the Dream Wall Pro is still blocked, see the issue) Two Ubiquiti cellular modems declared their LTE/5G radio as `wwan0` at **1G**, so `engine/media.js` resolved the cage to `[lte, lte-a]` and the **5G NR medium was never offered**. A lab asking for the cellular WAN in #130 could not cable either 5G Max as 5G. | row | wwan0 before | media offered | wwan0 now | media offered | |---|---|---|---|---| | `u5g-max` | 1G | lte, lte-a | 3.4G | lte, lte-a, **5g-sub6** | | `u5g-max-outdoor` | 1G | lte, lte-a | 3.4G | lte, lte-a, **5g-sub6** | | `udr-5g-max` (same radio, unchanged) | 3.4G | lte, lte-a, 5g-sub6 | 3.4G | lte, lte-a, 5g-sub6 | The figure is the vendor's, not a class ceiling: both pages print **5G NSA Downlink 3.4 Gbps / Uplink 560 Mbps**, 5G SA 1.8 Gbps / 650 Mbps, 4G LTE 1.6 Gbps / 210 Mbps - the same table `udr-5g-max` was already cited for. Sources read 2026-11-19 (crawler user-agent, text layer of the spec table): - https://techspecs.ui.com/unifi/accessories/u5g-max - 200, 691,340 B (+ `/integrations/u5g-max` 200, 691,345 B - both slugs serve the page) - https://techspecs.ui.com/unifi/accessories/u5g-max-outdoor - 200, 690,570 B (+ `/integrations/u5g-max-outdoor` 200, 690,575 B) - https://techspecs.ui.com/unifi/integrations/udr-5g-max - the sibling row that already carried 3.4G **Not touched:** `u5g` stays at 100M. It is 5G **RedCap** and Ubiquiti publishes no RedCap rate, so the 5G NR medium is still not offered there - recorded in that row's notes rather than guessed at. Gates: `node scripts/syntax-check.js` 453 files OK; `node scripts/audit-port-types.js` no contradiction; `test/hardware-invariants.test.js` 26/26; `test/import-devices-capabilities.test.js` pass (no capability moved); `test/catalogue-hygiene.test.js` and `test/faceplate-catalogue.test.js` pass; `node scripts/regen-registry-doc.js` - catalogue pages current (2,356 models, 29,716 sockets), no doc change.
ubiquiti: the 5G Max modems offered no 5G medium to cable (refs #130)
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) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 3s
02d1aca070
u5g-max and u5g-max-outdoor declared wwan0 at 1G, so engine/media.js resolved the cellular cage to [lte, lte-a] and the 5G NR medium was never offered - while udr-5g-max, the same radio, carried 3.4G and offered 5g-sub6.

Both tech-spec pages print 5G NSA 3.4 Gbps down / 560 Mbps up, 5G SA 1.8/650, LTE 1.6/210. Modelled at the vendor 5G NSA downlink, the figure udr-5g-max already uses. U5G (RedCap) left at 100M: no vendor rate is published to cite.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 13:26:09 +00:00
jaylouisw deleted branch catalogue/1119-1322 2026-11-19 13:40:52 +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!2159
No description provided.