ubiquiti: model the UniFi Dream Machine (UDM), the base console the catalogue skipped (#130) #2007

Merged
jaylouisw merged 1 commit from catalogue/1118-1656 into main 2026-11-18 17:09:31 +00:00
Owner

Refs #130 - does not close it: #130 asks for the Dream Wall Pro, which still has no vendor page anywhere.

This adds the one member of the Dream Machine console family the catalogue was missing: the base UDM (2019). The line was already modelled at UDM-Pro, UDM-SE, UDM-Pro-Max, UDM-Beast and the Dream Wall, so a lab asking for a console gateway had every variant but the original.

Source of the census - https://dl.ui.com/ds/udm_ds.pdf, HTTP 200, 747,030 B, application/pdf, read 2026-11-18, "Networking interface" row:

(4) LAN: GbE RJ45 ports
(1) WAN: GbE RJ45 port

No SFP, no PoE ports; Max. power consumption 26W on the same sheet. Modelled as WAN + LAN 1-LAN 4, all rj45 at 1G, no poe block (the unit sources none).

Why the tech-spec page is not the source. https://techspecs.ui.com/unifi/cloud-gateways/udm answers 200 at 608,032 B, but prints no networking-interface row - only Management interface: Ethernet, Bluetooth. Same host answers an unknown slug with a 200 home page (/udw-pro returns 609,911 B and the site root), so a 200 there is not evidence a spec table exists. Recorded in the spec's notes so the next pass does not read the page's silence as agreement.

Gates: syntax-check 419 files OK; audit-port-types no contradiction; audit-devices no hard defects; audit-poe-budget 0 budgets without a PSE port; hardware-invariants + spec-vs-description suites pass; regen-registry-doc -> 2,357 models / 29,726 sockets.

Nothing here is inferred from a sibling: the UDM's 5 ports are its own, which is the distinction the Pro request has been stuck on.

Refs #130 - does not close it: #130 asks for the Dream Wall **Pro**, which still has no vendor page anywhere. This adds the one member of the Dream Machine console family the catalogue was missing: the base **UDM** (2019). The line was already modelled at UDM-Pro, UDM-SE, UDM-Pro-Max, UDM-Beast and the Dream Wall, so a lab asking for a console gateway had every variant but the original. **Source of the census** - `https://dl.ui.com/ds/udm_ds.pdf`, HTTP 200, 747,030 B, `application/pdf`, read 2026-11-18, "Networking interface" row: ``` (4) LAN: GbE RJ45 ports (1) WAN: GbE RJ45 port ``` No SFP, no PoE ports; `Max. power consumption 26W` on the same sheet. Modelled as `WAN` + `LAN 1`-`LAN 4`, all `rj45` at 1G, no `poe` block (the unit sources none). **Why the tech-spec page is not the source.** `https://techspecs.ui.com/unifi/cloud-gateways/udm` answers 200 at 608,032 B, but prints no networking-interface row - only `Management interface: Ethernet, Bluetooth`. Same host answers an unknown slug with a 200 home page (`/udw-pro` returns 609,911 B and the site root), so a 200 there is not evidence a spec table exists. Recorded in the spec's `notes` so the next pass does not read the page's silence as agreement. **Gates:** `syntax-check` 419 files OK; `audit-port-types` no contradiction; `audit-devices` no hard defects; `audit-poe-budget` 0 budgets without a PSE port; `hardware-invariants` + `spec-vs-description` suites pass; `regen-registry-doc` -> 2,357 models / 29,726 sockets. Nothing here is inferred from a sibling: the UDM's 5 ports are its own, which is the distinction the Pro request has been stuck on.
ubiquiti: model the UniFi Dream Machine (UDM), the base console the catalogue skipped (#130)
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Arm auto-merge (pull_request) Successful in 31s
fc897cf8d6
The Dream Machine line is in the catalogue at five of its six published members -
UDM-Pro, UDM-SE, UDM-Pro-Max, UDM-Beast and the Dream Wall - but the base UDM,
the 2019 console the rest of the line descends from, was not there. #130 asks for
a "router/gateway node in a routed lab" and every real console in that family was
already modelled except this one.

Ports come from Ubiquiti's own datasheet, dl.ui.com/ds/udm_ds.pdf (HTTP 200,
747,030 B, application/pdf, read 2026-11-18), "Networking interface" row:
"(4) LAN: GbE RJ45 ports" and "(1) WAN: GbE RJ45 port". No SFP, no PoE ports,
max. power consumption 26 W - all three stated on that sheet.

The tech-spec page techspecs.ui.com/unifi/cloud-gateways/udm (200, 608,032 B) is
recorded in notes but is not the source of the counts: it prints no
networking-interface row at all, only "Management interface: Ethernet,
Bluetooth". That is worth knowing, because the same host answers unknown slugs
with a 200 home page, so a 200 there is not proof a spec table exists.

No PoE field, because the unit sources none - an empty array is a question, a
guessed one is a bug.

Gates: syntax-check (419 files), audit-port-types (no contradiction),
audit-devices (no hard defects), audit-poe-budget (0 budgets without a PSE port),
hardware-invariants + spec-vs-description suites pass, registry doc regenerated
(2,357 models / 29,726 sockets).
jaylouisw deleted branch catalogue/1118-1656 2026-11-18 17:09:33 +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!2007
No description provided.