devices(ubiquiti): the Dream consoles carry the access point they ship with (refs #130) #2199

Merged
jaylouisw merged 1 commit from catalogue/1119-1922 into main 2026-11-19 19:37:45 +00:00
Owner

Refs #130 (does not close it - the Pro's census is still unpublished, see the comment on the issue).

The defect. The UniFi Dream consoles are catalogued as gateways with Ethernet, SFP+ and PoE rows and no radios, although every one of the four ships with an integrated access point. In a lab that means you can cable a Dream Wall but cannot associate a phone, laptop or wireless client to it. Ubiquiti's own device database lists ACCESS_POINT beside GATEWAY and SWITCH in the UDW's deviceCapabilities (static.ui.com/fingerprint/ui/public.json, sku UDW, sysid ea2a), so the vendor is not ambiguous about what the box is.

The fix. radio0 (2.4 GHz), radio1 (5 GHz), radio2 (6 GHz) at each vendor page's throughput for that band, plus the wireless capability, on the four Dream consoles that state their band rates:

row radios added vendor rows source
udw 2 (300M / 2.4G) 2.4 GHz 300 Mbps 2x2, 5 GHz 2.4 Gbps 4x4, 802.11ax https://dl.ui.com/ds/udw_ds.pdf (200, 544,909 B, text layer) + https://techspecs.ui.com/unifi/cloud-gateways/udw (200, 704,702 B)
udr 2 (600M / 2.4G) 2.4 GHz 600 Mbps 4x4, 5 GHz 2.4 Gbps 4x4, 802.11ax https://dl.ui.com/ds/udr_ds.pdf (200, 771,202 B, text layer) + https://techspecs.ui.com/unifi/cloud-gateways/udr (200, 685,837 B)
udr7 3 (688M / 4.3G / 5.7G) 2.4 GHz 688 Mbps, 5 GHz 4.3 Gbps, 6 GHz 5.7 Gbps, all 2x2, 802.11be https://techspecs.ui.com/unifi/cloud-gateways/udr7 (200, 694,590 B)
udr-5g-max 3 (688M / 4.3G / 5.7G) same trio, 802.11be https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-max (200, 876,426 B)

bands is declared on each radio on purpose. derivePortHardware() in engine/media.js derives the band set from the rate alone, so a 2.4 Gbps 802.11ax radio would be credited with 2.4/5 and 6 GHz - a band neither Dream Wall nor Dream Router has - and a 4.3 Gbps 802.11be radio likewise. Declared bands wins over the inference.

Checked through the engine, not by eye (iPhone 16/wlan0 against the Dream Wall):

wlan0 <-> radio0  ok=true  wireless-2.4  300 Mbps      (iPhone 16 to UDW)
wlan0 <-> radio1  ok=true  wireless-5    1000 Mbps
wlan0 <-> sfp1    ok=false "A wireless radio cannot be cabled to a wired port."

udr-5g-max's note said the WiFi 7 radios were deliberately not modelled because no console row in the catalogue carried radios and one row alone would misrepresent the family; the whole Dream family now carries them, so that paragraph is replaced rather than left to contradict the spec.

Not touched. udm (base Dream Machine): its tech-spec page prints the WiFi section without throughput or MIMO rows, so no per-band rate can be traced - it stays wired-only. And nothing here is written from the non-Pro Dream Wall's numbers; #130 remains blocked on the Pro's own census.

docs/CONNECTORS.md regenerated (29,710 -> 29,720 sockets; the generated figure, not hand-edited). Research note: research/ubiquiti-dream-console-radios.md.

Gates. syntax-check 462 OK · audit-port-types clean · audit-devices no hard defects · hardware invariants 26 passed / 0 failed · run-tests 383 suites, 12,907 assertions, 0 failed · control-bytes clean · doc-citations clean · registry doc current (2,355 models).

Refs #130 (does not close it - the Pro's census is still unpublished, see the comment on the issue). **The defect.** The UniFi Dream consoles are catalogued as gateways with Ethernet, SFP+ and PoE rows and **no radios**, although every one of the four ships with an integrated access point. In a lab that means you can cable a Dream Wall but cannot associate a phone, laptop or wireless client to it. Ubiquiti's own device database lists `ACCESS_POINT` beside `GATEWAY` and `SWITCH` in the UDW's `deviceCapabilities` (`static.ui.com/fingerprint/ui/public.json`, sku UDW, sysid `ea2a`), so the vendor is not ambiguous about what the box is. **The fix.** `radio0` (2.4 GHz), `radio1` (5 GHz), `radio2` (6 GHz) at each vendor page's throughput for that band, plus the `wireless` capability, on the four Dream consoles that state their band rates: | row | radios added | vendor rows | source | |---|---|---|---| | `udw` | 2 (300M / 2.4G) | 2.4 GHz 300 Mbps 2x2, 5 GHz 2.4 Gbps 4x4, 802.11ax | <https://dl.ui.com/ds/udw_ds.pdf> (200, 544,909 B, text layer) + <https://techspecs.ui.com/unifi/cloud-gateways/udw> (200, 704,702 B) | | `udr` | 2 (600M / 2.4G) | 2.4 GHz 600 Mbps 4x4, 5 GHz 2.4 Gbps 4x4, 802.11ax | <https://dl.ui.com/ds/udr_ds.pdf> (200, 771,202 B, text layer) + <https://techspecs.ui.com/unifi/cloud-gateways/udr> (200, 685,837 B) | | `udr7` | 3 (688M / 4.3G / 5.7G) | 2.4 GHz 688 Mbps, 5 GHz 4.3 Gbps, 6 GHz 5.7 Gbps, all 2x2, 802.11be | <https://techspecs.ui.com/unifi/cloud-gateways/udr7> (200, 694,590 B) | | `udr-5g-max` | 3 (688M / 4.3G / 5.7G) | same trio, 802.11be | <https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-max> (200, 876,426 B) | `bands` is declared on each radio on purpose. `derivePortHardware()` in `engine/media.js` derives the band set from the rate alone, so a 2.4 Gbps 802.11ax radio would be credited with 2.4/5 **and 6 GHz** - a band neither Dream Wall nor Dream Router has - and a 4.3 Gbps 802.11be radio likewise. Declared `bands` wins over the inference. Checked through the engine, not by eye (`iPhone 16/wlan0` against the Dream Wall): ``` wlan0 <-> radio0 ok=true wireless-2.4 300 Mbps (iPhone 16 to UDW) wlan0 <-> radio1 ok=true wireless-5 1000 Mbps wlan0 <-> sfp1 ok=false "A wireless radio cannot be cabled to a wired port." ``` `udr-5g-max`'s note said the WiFi 7 radios were deliberately not modelled because no console row in the catalogue carried radios and one row alone would misrepresent the family; the whole Dream family now carries them, so that paragraph is replaced rather than left to contradict the spec. **Not touched.** `udm` (base Dream Machine): its tech-spec page prints the WiFi section without throughput or MIMO rows, so no per-band rate can be traced - it stays wired-only. And nothing here is written from the non-Pro Dream Wall's numbers; #130 remains blocked on the Pro's own census. `docs/CONNECTORS.md` regenerated (29,710 -> 29,720 sockets; the generated figure, not hand-edited). Research note: `research/ubiquiti-dream-console-radios.md`. **Gates.** syntax-check 462 OK · audit-port-types clean · audit-devices no hard defects · hardware invariants 26 passed / 0 failed · run-tests 383 suites, 12,907 assertions, 0 failed · control-bytes clean · doc-citations clean · registry doc current (2,355 models).
devices(ubiquiti): the Dream consoles carry the access point they ship with (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Arm auto-merge (pull_request) Successful in 3s
faaf16c2e0
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 19:30:36 +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!2199
No description provided.