research(ubiquiti): the firmware index enumerates 17 Dream platforms and has no UDW-PRO #2062

Merged
jaylouisw merged 1 commit from catalogue/1119-0052 into main 2026-11-19 01:08:50 +00:00
Owner

Refs #130 - record only, the request is not answered and must stay open.

Eleven passes on this thread read product pages, datasheets, the store tree and the grantee
list. None read the index the update daemon on the device itself polls, and that is the one
surface where a model code cannot be edited away.

The instrument. https://fw-update.ubnt.com/api/firmware is the release index, keyed by
platform code, and the code names the binary: the UDW 6.0.17 release carries
/data/unifi-dream/2d04-UDW-6.0.17-...bin. Filter is eq on platform, case-insensitive.
The default page size is 25, so a query without limit=1000 undercounts (UDW reads 25
instead of 27); every number below was taken at limit=1000.

The census. product~~unifi-dream: HTTP 200, 340 releases across 17 platform codes -
UDM 27, UDMPRO 27, UDMPROSE 40, UDMPROMAX 20, UDR 36, UDR5G 9, UDR7 17,
UDRULT 22, UDW 27, UX 15, UXMAX 15, UCGF 17, UCGMAX 19, UCGA6AD 10,
EFGCORE 8, UDMENT 21, UDMEA4C 10.

UDW: 27 releases, 2022-05-07 to 2026-11-10, latest v6.0.17+7bcad58 - the start matching
the May 2022 SWX-UDW grant, the end nine days before this run.

No UDWPRO. UDWPRO, UDW-PRO, UDWPROMAX, UDW2, UDWSE, UDWMAX each return the
96-byte 0-release envelope - byte-identical to the nonsense control ZZZZ, so a zero is a
valid empty answer, not a failing query. The controls that make the absence mean something
are in the same family: UDMPRO 65, UDMPROSE 40, UDMPROMAX 20, UXMAX 15. Ubiquiti
gives Pro variants their own platform code even when two boxes are the same class of console,
so a shipped Pro Dream Wall would be a row here.

Caveat, on the record. This closes "is there a Pro platform?", not "how many ports would
it have?". A rebadged variant sharing the parent mainboard could hide under the UDW code,
and no firmware index publishes RJ45 or SFP+ counts - so the port census still has to come
from a Ubiquiti document.

What would unblock it: unchanged - a Ubiquiti page, datasheet, quick-start guide or FCC
exhibit naming UDW-PRO's ports and PoE budget, or the requester confirming they meant the
UDW (catalogued at devices/ubiquiti/udw.json). No spec was added.

Gates: syntax-check 432 files OK; audit-port-types no contradiction; hardware-invariants
26 passed; request-queue 32 passed; regen-registry-doc --check current; check-control-bytes
clean.

scripts/ubiquiti-firmware-index.js is the reusable probe (--platform, --family,
--product); research/ubiquiti-firmware-platform-census.md is the full record.

Refs #130 - record only, the request is not answered and must stay open. Eleven passes on this thread read product pages, datasheets, the store tree and the grantee list. None read the index the update daemon on the device itself polls, and that is the one surface where a model code cannot be edited away. **The instrument.** `https://fw-update.ubnt.com/api/firmware` is the release index, keyed by *platform code*, and the code names the binary: the `UDW` 6.0.17 release carries `/data/unifi-dream/2d04-UDW-6.0.17-...bin`. Filter is `eq` on `platform`, case-insensitive. The default page size is 25, so a query without `limit=1000` undercounts (`UDW` reads 25 instead of 27); every number below was taken at `limit=1000`. **The census.** `product~~unifi-dream`: HTTP 200, **340 releases across 17 platform codes** - `UDM` 27, `UDMPRO` 27, `UDMPROSE` 40, `UDMPROMAX` 20, `UDR` 36, `UDR5G` 9, `UDR7` 17, `UDRULT` 22, `UDW` 27, `UX` 15, `UXMAX` 15, `UCGF` 17, `UCGMAX` 19, `UCGA6AD` 10, `EFGCORE` 8, `UDMENT` 21, `UDMEA4C` 10. `UDW`: 27 releases, 2022-05-07 to 2026-11-10, latest `v6.0.17+7bcad58` - the start matching the May 2022 `SWX-UDW` grant, the end nine days before this run. **No `UDWPRO`.** `UDWPRO`, `UDW-PRO`, `UDWPROMAX`, `UDW2`, `UDWSE`, `UDWMAX` each return the 96-byte 0-release envelope - byte-identical to the nonsense control `ZZZZ`, so a zero is a valid empty answer, not a failing query. The controls that make the absence mean something are in the same family: `UDMPRO` 65, `UDMPROSE` 40, `UDMPROMAX` 20, `UXMAX` 15. Ubiquiti gives Pro variants their own platform code even when two boxes are the same class of console, so a shipped Pro Dream Wall would be a row here. **Caveat, on the record.** This closes "is there a Pro platform?", not "how many ports would it have?". A rebadged variant sharing the parent mainboard could hide under the `UDW` code, and no firmware index publishes RJ45 or SFP+ counts - so the port census still has to come from a Ubiquiti document. **What would unblock it:** unchanged - a Ubiquiti page, datasheet, quick-start guide or FCC exhibit naming UDW-PRO's ports and PoE budget, or the requester confirming they meant the `UDW` (catalogued at `devices/ubiquiti/udw.json`). No spec was added. Gates: `syntax-check` 432 files OK; `audit-port-types` no contradiction; `hardware-invariants` 26 passed; `request-queue` 32 passed; `regen-registry-doc --check` current; `check-control-bytes` clean. `scripts/ubiquiti-firmware-index.js` is the reusable probe (`--platform`, `--family`, `--product`); `research/ubiquiti-firmware-platform-census.md` is the full record.
research(ubiquiti): the firmware index enumerates 17 Dream platforms and has no UDW-PRO
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 6s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 2s
e2c7e40220
Ubiquiti's own release index (fw-update.ubnt.com/api/firmware) is keyed by platform
code, and the code names the binary. Product unifi-dream: 340 releases across 17
platform codes, including UDMPRO, UDMPROSE, UDMPROMAX and UXMAX as separate codes.
UDW: 27 releases, 2022-05-07 to 2026-11-10. UDWPRO and every other Pro spelling: the
96-byte 0-release envelope, same as the ZZZZ control.

Adds scripts/ubiquiti-firmware-index.js and research/ubiquiti-firmware-platform-census.md.
Refs #130 - the request is not answered and stays open.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 01:00:35 +00:00
jaylouisw deleted branch catalogue/1119-0052 2026-11-19 01:08:51 +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!2062
No description provided.