research(ubiquiti): two more vendor surfaces list no Dream Wall Pro — ItemList + support KB (#130) #2084

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

Refs #130

Two Ubiquiti hosts that no earlier pass read; both enumerate products by name, both answer the Pro with nothing, and both answered a control.

  1. https://ui.com/cloud-gateways — 200, 446,725 B — carries a schema.org ItemList naming 14 cloud gateways with their tech-spec URLs: items 4 and 6 are Dream Machine Pro Max and Dream Machine Pro, item 13 is Dream Wall -> /udw. udw-pro and Dream Wall Pro occur 0 times. Caveat: curated 14 of the techspecs grid's 16 (udr, ux absent), so corroborative, not exhaustive.

  2. https://help.ui.com/api/v2/help_center/articles/search.json (Zendesk, unauth) for dream wall pro / udw-pro / udw: 200 at 728,119 / 719,384 / 364,696 B (counts 33/105/13), 73 rows, 50 unique articles — zero occurrences of Dream Wall Pro, UDW-PRO, UDWPRO. The box appears only as Dream Wall (UDW). Control: query=udm-pro returns 1,737,208 B and 100 of 118 rows carrying UDM-PRO 39x and Dream Machine Pro 18x, so the index does hold Pro-suffixed console names.

Trap recorded: ui.com/robots.txt declares https://ui.com/sitemap.xml; it is real (200, 8,712 B, 81 locs) but indexes sections, not SKUs (zero dream), so it must not be cited as a negative either way.

Incidental corroboration, no spec change: the Recovery Mode article says "Connect to the Dream Wall via Port 18, not Port 1" — consistent with 17 LAN + 1 WAN RJ45 in devices/ubiquiti/udw.json (20 interfaces with the two SFP+).

Still missing for the Pro: RJ45/SFP+ counts and rates, PoE budget and per-port maxima, drive bays, WAN options. Nothing is modelled from the non-Pro's numbers.

Gates: syntax-check 435 files OK; audit-port-types "No port contradicts its declared type"; test:hardware 26 passed, 0 failed; check-canonical-urls OK.

Refs #130 Two Ubiquiti hosts that no earlier pass read; both enumerate products by name, both answer the Pro with nothing, and both answered a control. 1. `https://ui.com/cloud-gateways` — 200, 446,725 B — carries a schema.org `ItemList` naming 14 cloud gateways with their tech-spec URLs: items 4 and 6 are `Dream Machine Pro Max` and `Dream Machine Pro`, item 13 is `Dream Wall` -> `/udw`. `udw-pro` and `Dream Wall Pro` occur 0 times. Caveat: curated 14 of the techspecs grid's 16 (`udr`, `ux` absent), so corroborative, not exhaustive. 2. `https://help.ui.com/api/v2/help_center/articles/search.json` (Zendesk, unauth) for `dream wall pro` / `udw-pro` / `udw`: 200 at 728,119 / 719,384 / 364,696 B (counts 33/105/13), 73 rows, 50 unique articles — zero occurrences of `Dream Wall Pro`, `UDW-PRO`, `UDWPRO`. The box appears only as `Dream Wall (UDW)`. Control: `query=udm-pro` returns 1,737,208 B and 100 of 118 rows carrying `UDM-PRO` 39x and `Dream Machine Pro` 18x, so the index does hold Pro-suffixed console names. Trap recorded: `ui.com/robots.txt` declares `https://ui.com/sitemap.xml`; it is real (200, 8,712 B, 81 locs) but indexes sections, not SKUs (zero `dream`), so it must not be cited as a negative either way. Incidental corroboration, no spec change: the Recovery Mode article says "Connect to the Dream Wall via Port 18, not Port 1" — consistent with 17 LAN + 1 WAN RJ45 in `devices/ubiquiti/udw.json` (20 interfaces with the two SFP+). Still missing for the Pro: RJ45/SFP+ counts and rates, PoE budget and per-port maxima, drive bays, WAN options. Nothing is modelled from the non-Pro's numbers. Gates: `syntax-check` 435 files OK; `audit-port-types` "No port contradicts its declared type"; `test:hardware` 26 passed, 0 failed; `check-canonical-urls` OK.
research(ubiquiti): the gateways ItemList and the support KB list no Dream Wall Pro (#130)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 4s
674375f4b4
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 04:00:30 +00:00
jaylouisw deleted branch catalogue/1119-0352 2026-11-19 04:01: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!2084
No description provided.