[Device]: Ubiquiti UniFi Dream Wall Pro (UDW-PRO) #130
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Vendor
Ubiquiti
Exact model name
UDW-PRO
Category
Router
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/ubiquiti-unifi-dream-wall-pro-udwpro-p-10111.html
What do you want to model with it?
A router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN).
Capabilities
routing, NAT, DHCP, l3-forward
Before submitting
Closing status: blocked on a source that does not exist yet.
The Dream Wall Pro has no Ubiquiti tech-spec page:
techspecs.ui.com/unifi/cloud-gateways/udw-proredirects, and the published datasheet (dl.ui.com/ds/udw_ds.pdf) describes the non-Pro Dream Wall -(17) LAN: GbE RJ45,(1) WAN: 2.5 GbE RJ45,(1) LAN: 10G SFP+,(1) WAN: 10G SFP+, PoE split 4x PoE++ / 4x PoE+ / 4x PoE.Modelling the Pro from the non-Pro's numbers would be exactly the family-sibling error this project has already corrected three times (a phantom UDM PoE draw, a phantom console port on two i-MO kits, copper uplinks invented for three MA5801s). A reseller listing suggests the Pro differs materially - fewer LAN ports, a 2.5G PoE input, different PoE budget - but "suggests" is not a source.
What would close it: Ubiquiti publishing the Pro's port layout, or the unit's quick-start guide which usually prints one.
Closing status: still blocked, and the blocker is now "the product has no vendor page at all" - not "Ubiquiti has not published the port layout". PR #1781 records the evidence; it does not close this issue.
Sources checked today (2026-11-17), Ubiquiti only
https://techspecs.ui.com/unifi/cloud-gateways/udw- HTTP 200, 704,702 bytes: the UDW page. There is no Pro next to it in the Cloud Gateways list.https://dl.ui.com/ds/udw_ds.pdf- HTTP 200,application/pdf, 544,909 bytes: UDW datasheet only. (17) LAN GbE RJ45 incl. 4 PoE / 4 PoE+ / 4 PoE++, (1) WAN 2.5 GbE RJ45, (1) LAN + (1) WAN 10G SFP+.https://techspecs.ui.com/unifi/cloud-gateways/udw-pro- 200 but redirects tohttps://techspecs.ui.com/, 609,911 bytes.https://store.ui.com/us/en/products/udw-pro- HTTP 404./products/udwis 200, and its HTML contains only theudw-us,udw-moduleandudw-racewayslugs.https://dl.ui.com/ds/udw-pro_ds.pdf- falls back to the same 609,911-byte home page.https://www.4gon.co.uk/ubiquiti-unifi-dream-wall-pro-udwpro-p-10111.html(the listing this request cites) - HTTP 403 to this host, and a reseller listing would not be admissible for a port count anyway.The trap worth knowing. Both
techspecs.ui.comanddl.ui.comanswer HTTP 200 with the techspecs home page for any slug they do not have. Controls:.../udw-pro-techspecsanddl.ui.com/ds/bogus-xyz_ds.pdfreturn the identical 609,911-byte page. So a 200 on those hosts is the not-found, and the earlier note that the Pro path "redirects" was reading a 404 as a redirect. The same applies to the QSG pattern (dl.ui.com/qs/UDW.pdffalls back too), so "no quick-start exists" cannot be concluded from a 404-looking path either.Exact missing fields: LAN GbE RJ45 count, 2.5G/10G port count and whether the SFP+ are LAN, WAN or both, the PoE class mix and total PoE budget, drive bays, and the cellular/WAN options - i.e. the whole census. The non-Pro's numbers cannot stand in: those are exactly the fields the Pro was trailed with different values for, and copying them is the family-sibling error this catalogue has corrected on UDM PoE, two i-MO console ports and three MA5801 uplinks.
What would unblock it: the Pro's own techspecs page (final URL unchanged and bytes not 609,911), its quick-start or installation guide at a URL that resolves, or a statement from Ubiquiti that the Pro was cancelled - which would make this closable as "not a shipping product" rather than unbuildable.
Re-checked at the catalogue level. The blocker is no longer "Ubiquiti has not published the Pro's port layout" - the SKU is absent from Ubiquiti's own gateway index. PR #1823 records it in
research/ubiquiti-cloud-gateway-catalogue.md; the issue stays open.Source read today (Ubiquiti only)
https://techspecs.ui.com/unifi/cloud-gateways- HTTP 200, 610,409 bytes, crawler user-agent, server-rendered. This is the grid behindcategory=all-cloud-gateways: sixteen product cards, each<h6>title</h6><p>SKU</p>plus a link to/unifi/cloud-gateways/<slug>.The Dream Wall card is
<h6>Dream Wall</h6><p>UDW</p>. The stringudw-prooccurs zero times in those 610,409 bytes. The Pro suffixes Ubiquiti does sell (udm-pro,udm-pro-max) are on the same grid, so this is the page where a Pro Dream Wall would be listed and it is not there.That is a stronger statement than the 404s already on this thread: a 404 on one URL can mean a retired page, a locale slug or a redirect chain, whereas absence from the category grid means the store has no such product under any slug. Three passes read the 404s as "not published yet" and kept hunting; that framing is now closed.
One trap recorded so it is not re-walked:
https://store.ui.com/us/en/search?q=dream+wallanswers 200, 252,278 bytes, and contains zero occurrences of "dream wall" - results are client-rendered. Its emptiness is not evidence either way.Related, and already correct: the Dream Wall that does exist is catalogued at
devices/ubiquiti/udw.jsonand matches the vendor page (704,702 B) field by field - 17x 1GbE RJ45 (4 PoE++ / 4 PoE+ / 4 PoE), 1x 2.5GbE RJ45, 2x 10G SFP+ (10G/1G), PoE budget 420 W, 112 W max draw excluding PoE. So there is no catalogue gap to fill under either name.What would close it: any Ubiquiti-hosted URL for a Pro variant - store slug, tech-spec page,
dl.ui.com/ds/udw-pro_ds.pdf, or the unit's quick-start guide - or a note that you meant the UDW. No spec is written from UDW's numbers: that is exactly the family-sibling error this catalogue has corrected three times (a phantom UDM PoE draw, a phantom console port on two i-MO kits, invented copper uplinks on three MA5801s).Re-checked on the three surfaces that could still hide a real product - the EU storefront, the FCC grant index and the Wayback Machine. All three are empty, so the blocker is now "the product was announced and never listed", not "the layout is not published yet". PR #1864 records it; the issue stays open.
1. Not a regional SKU.
https://eu.store.ui.com/eu/en/category/all-cloud-gateways- 200, 487,282 B, server-rendered. The cloud-gateway grid publishes exactly one Dream Wall:udw-eu, the 420 W UDW.udw-prooccurs zero times in those bytes.2. No certification record. Ubiquiti's grantee prefix is
SWX, so a shipping console must hold a grant there:SWX-UDWSWX-UDWPRO,SWX-UDW-PRO,SWX-UDW2An uncertified radio cannot have been sold, which is the mechanism behind the empty techspecs and store surfaces rather than a separate fact. (
fcc.report/FCC-ID/SWX-UDWanswers 403 to a crawler;fccid.iois a mirror, so this is strong evidence, not the Commission's own index.)3. No archived page to recover.
http://archive.org/wayback/availablereturns"archived_snapshots": {}fortechspecs.ui.com/unifi/cloud-gateways/udw-pro,store.ui.com/us/en/products/udw-pro,store.ui.com/products/udw-proandui.com/unifi/cloud-gateways/udw-pro. Nothing was ever crawled, so there is no withdrawn page carrying the Pro's specs.The one vendor-authored sentence that does name a Pro. Ubiquiti's early-access store copy reads "The Dream Wall and Dream Wall Pro (UDW/UDW Pro) are wall-mounted UniFi OS Consoles that serve as standalone, space-saving deployment hosting solutions." - and the feature list printed under it is the UDW's (17 GbE RJ45 with 4 PoE++ / 4 PoE+ / 4 PoE, 2.5 GbE WAN, 10G SFP+ WAN and LAN), beside "Dream Wall Pro - Coming Soon".
Exact missing fields: the Pro's RJ45 and SFP+ port census with per-port PoE class, and its PoE budget.
What would close it, any one of: a Ubiquiti page, datasheet, FCC exhibit or quick-start guide that names UDW-PRO's ports; or a note that you meant the UDW, which is already catalogued as
devices/ubiquiti/udw.json(19 ports, PoE budget 420 W, verified against the vendor page). Modelling the Pro from the non-Pro numbers is the family-sibling error this catalogue has corrected three times.Fourth re-check, and the last one worth doing: every surviving vendor route is now exhausted, and none of them has ever contained a Pro Dream Wall. Recommended disposition: close as "cannot be modelled honestly".
Read today, 2026-11-17, 21:25-21:55 UTC, crawler user-agent, Ubiquiti-hosted sources only. This pass went after the routes the three previous passes had not swept — the real
dl.ui.comquick-guide pattern, the wayback CDX index (rather than the per-URLavailableendpoint), andui.com's sitemap — and all three come back empty.1. techspecs.ui.com — the Pro has no page, and never takes a row in the index
https://techspecs.ui.com/unifi/cloud-gateways/udwhttps://techspecs.ui.com/unifi/cloud-gateways/udw-prohttps://techspecs.ui.com/, 609,911 B (the site's not-found)https://techspecs.ui.com/unifi/cloud-gateways/udwprohttps://techspecs.ui.com/, 609,911 Bhttps://techspecs.ui.com/unifi/cloud-gatewayshttps://techspecs.ui.com/unifi/cloud-gateways/compareand...compare?subcategory=cloud-gateways-large-scaleudw-proThe index re-read today still prints exactly 16 cards / 16 SKUs:
EF-Core, EFG, UDM-Beast, UDM-Pro-Max, UDM-Pro, UDM-SE, UCG-Industrial, UCG-Fiber, UCG-Max, UCG-Ultra, UX7, UDR-5G-Max, UDR7, UX, UDW, UDR. Card 15 is<h6>Dream Wall</h6><p>UDW</p>. The Pro-naming pattern Ubiquiti actually uses (UDM-Pro,UDM-Pro-Max) is on that grid; a Pro Dream Wall is not. The UDW page itself contains zero occurrences ofudw-pro/UDW Pro.2. dl.ui.com — the quick-guide pattern is
/qig/, and the Pro has nothing there eitherThe earlier note tested
/qs/UDW-Pro.pdf, which is not Ubiquiti's naming. The real pattern isdl.ui.com/qig/<slug>, so this pass tested it properly:https://dl.ui.com/qig/udw.pdfapplication/pdf— a real UDW quick-install guide (1 page, image-only, no text layer)https://dl.ui.com/qig/udw-pro.pdfhttps://techspecs.ui.com/, 609,911 Bhttps://dl.ui.com/qig/udw-prohttps://techspecs.ui.com/, 609,911 Bhttps://dl.ui.com/qig/UDW-Pro.pdfhttps://techspecs.ui.com/, 609,911 Bhttps://dl.ui.com/ds/udw-pro_ds.pdf,/ds/udwpro_ds.pdf,/ds/UDW-Pro_ds.pdfhttps://techspecs.ui.com/, 609,911 Bhttps://dl.ui.com/ds/udw_ds.pdfapplication/pdf, 544,909 B — UDW datasheethttps://dl.ui.com/ds/bogus-xyz_ds.pdf,/qig/bogus-xyz.pdfWayback's CDX index for all of
dl.ui.com, filtered onudw-pro: zero rows, ever. The only UDW-family documents Ubiquiti has ever published under/qig/areqig/udw,qig/udw.pdfandqig/uacc-psu-udw(.pdf)(the accessory PSU).3. Store and regional variants — one Dream Wall per storefront, always the UDW
https://store.ui.com/us/en/products/udw-prohttps://store.ui.com/eu/en/products/udw-prohttps://eu.store.ui.com/eu/en/products/udw-pro)https://store.ui.com/default/products/udw-prohttps://store.ui.com/us/en/udw-pro)https://store.ui.com/us/en/products/udwhttps://eu.store.ui.com/eu/en/category/all-cloud-gatewaysudw-prohttps://uk.store.ui.com/uk/en/category/all-cloud-gatewaysudw-prohttps://store.ui.com/us/en/category/all-cloud-gatewayshttps://store.ui.com/us/en/category/early-accesshttps://store.ui.com/us/en, 585,472 B, 0udw-proNew trap worth recording:
https://ui.com/download/software/udw-proanswers 200, 358,781 B — and is byte-identical (MD54c717010adb78863ca8dd78412dbb925) tohttps://ui.com/download/software/udw, which is itself the same 358,781 B document ashttps://ui.com/download/release-notes. So the software-download surface soft-200s an arbitrary product slug exactly liketechspecsanddldo. Do not read a 200 there as a product.4. Press / newsroom / release notes — nothing that names a Pro
https://ui.com/news,https://ui.com/newsroomhttps://ui.com/presshttps://ui.com/, 426,365 B, 0 hitshttps://ui.com/whats-newudw-pro, 0 "dream wall"https://blog.ui.com/udw, 0 "dream wall"https://ui.com/sitemap.xml<loc>entries, none containingudwordreamhttps://store.ui.com/sitemap.xml,/robots.txthttps://techspecs.ui.com/sitemap.xml,/robots.txt,/sitemap_index.xmlrobots.txton that host is not a robots filehttps://ui.com/cloud-gateways/dream-wallhttps://ui.com/cloud-gateways/wifi-integrated(page retired, folded into the category)5. Wayback — this is the decisive one, because it is a sweep and not a guess
Previous passes used
archive.org/wayback/availableper-URL, which only answers for exact keys. This pass queried the CDX index across whole hosts:store.ui.comdomain-wide,original:.*udw-pro.*dl.ui.comdomain-wide,original:.*udw-pro.*techspecs.ui.com/unifi/cloud-gateways/*,original:.*udw.*20251127083429,...?s=eu,...?s=us,...?subcategory=all-cloud-gateways,...?subcategory=cloud-gateways-wifi-integratedarchive.org/wayback/availablealso returns"archived_snapshots": {}for every plausible Pro key:techspecs…/udw-pro,store.ui.com/us/en/products/udw-pro,…/udw-pro?variant=udw-pro-us,ui.com/products/udw-pro,ui.com/download/software/udw-pro,dl.ui.com/ds/udw-pro_ds.pdf,dl.ui.com/qig/udw-pro.pdf.Captures that do exist, and were opened today:
techspecs.ui.com/unifi/cloud-gateways/udw@ 2025-11-27 08:34:29 — 260,569 B served, 11 "dream wall", 0udw-pro.store.ui.com/us/en/products/udw?variant=udw-us@ 2026-04-28 10:37:46 — 453,129 B, 0udw-pro.store.ui.com/us/en/category/all-cloud-gateways@ 2025-07-16 17:54:49 — 327,230 B, one Dream Wall card, 0udw-pro.dl.ui.com/ds/udw_ds.pdf@ 2022-05-06 15:32:53 — the early-access-era datasheet, 2,582,067 B, text layer read in full: 111 lines, zero standalone occurrences of "Pro". It describes the UDW as (17) GbE RJ45 ports, including (12) with PoE output [(4) PoE, (4) PoE+, (4) PoE++] … (3) multi-gigabit WAN/LAN ports. Note this is a fourth way the family resists modelling: even the UDW's own prose aggregates ports differently from its own table (17 + 1x2.5G + 1x10G LAN + 1x10G WAN).www.ui.com/cloud-gateways/dream-wall@ 2024-01-10 07:53:29 — the only archived Dream Wall marketing page, and it is an 18,083 B client-rendered shell: the string "Dream Wall" appears twice, both inside<title>. No port data, no Pro mention.6. Help centre and community
help.ui.comis server-rendered and therefore usable:?query=UDW(44,708 B) and?query=dream+wall(44,947 B) return Dream Machine Pro Max (UDM-Pro-Max) and Dream Wall (UDW) in their comparison tables;?query=dream+wall+pro(45,271 B) contains 0udw-pro/ "UDW Pro".community.ui.com/search?q=dream wall prois a 2,638 B JS shell — like the store's search page, its emptiness proves nothing.Exact missing fields
Still the whole census: LAN GbE RJ45 count, whether the 2.5G and 10G SFP+ ports are LAN, WAN or both, per-port PoE class mix, total PoE budget, drive bays, and cellular/WAN options. The UDW's numbers remain inadmissible — and the 2022 datasheet above shows even those numbers have moved within the UDW's own document history.
Recommendation
Close #130 as "cannot be modelled honestly" (equivalently: not a shipping product). The Pro was announced in the 2022 early-access copy and never listed: it is absent from the techspecs gateway index (16/16 cards, read today and in every archive capture), absent from the US/EU/UK storefront grids, has no FCC grant under any Pro variant (
SWX-UDWPRO,SWX-UDW-PRO,SWX-UDW2all 303), has no datasheet or quick-start at any pattern Ubiquiti has ever used, and noudw-proURL has ever been crawled by the Wayback Machine on any Ubiquiti host. Four passes have now checked this from four directions and produced the same answer; a fifth pass has nothing left to read.The one box that does exist, the UDW, is already catalogued at
devices/ubiquiti/udw.json(19 ports, PoE budget 420 W, 112 W max draw excluding PoE) and matches the vendor page field by field, so closing this does not leave a catalogue gap. If a Pro ever ships, a fresh request citing its own page is the right way in — that is Jay's call to make, not mine.Re-checked 2026-11-18 02:2x UTC. Still blocked, and today's four fresh probes suggest the SKU is a reseller phantom rather than an unpublished product. No spec, no close.
What was measured today (new URLs, so nobody re-walks them):
https://store.ui.com/us/en/products/udw-prohttps://uk.store.ui.com/uk/en/products/udw-prohttps://dl.ui.com/ds/udw_pro_ds.pdfhttps://techspecs.ui.com/(no such datasheet)https://dl.ui.com/ds/udw-pro_ds.pdfhttps://techspecs.ui.com/https://techspecs.ui.com/unifi/cloud-gateways/udw-proTwo corroborating readings. The US, UK and EU storefronts now carry exactly one wall console, listed as "UDW (420W)" (
store.ui.com/us/.../products/udw,uk.store.ui.com/uk/en/products/udw,eu.store.ui.com/eu/en/collections/unifi-dream-wall/products/udw) — the parenthetical wattage is new copy, and no Pro sibling is offered. Resellers that do publish the SKU (ubiquiti.ru/unifi-dream-wall.html) print the comparison row "Dream Wall Pro" with every cell empty and "no data" in the spec box, which is what a catalogue entry created from the 2022 early-access announcement looks like, not what a launched product looks like.Still missing, unchanged: the entire port layout and the PoE budget (port count by RJ45/SFP+, which ports are PoE/PoE+/PoE++, and the PSE budget in watts). The EA blurb at
https://ubiquiti-networks-forum.de/board/thread/4925-ea-store-eu-dream-wall-early-access/names "(4) PoE, (4) PoE+, (4) PoE++" and a 2.7 Gbit/s radio for both consoles, but that is the UDW's port list under a two-product sentence — the family-sibling read this catalogue has already had to correct.Unblock: a Ubiquiti datasheet, FCC grant, or store page for
UDW-PRO; or the requester confirming they meant the UDW (420W), already catalogued asdevices/ubiquiti/udw.jsonwith 17x GbE RJ45 (4 PoE / 4 PoE+ / 4 PoE++), 2x 10G SFP+, 1x 2.5GbE WAN and a 420 W budget.clear counters#1945Still blocked - no new UDW-PRO source - but the fallback this thread points at was wrong, and is now fixed (PR #1979).
Every comment above (including mine) says the requester can be sent to the UDW instead, "already catalogued as
devices/ubiquiti/udw.jsonwith ... a 420 W budget". That budget was not in the spec. The file carried 12poeOutports and nopoe.budgetW, soDevicefell through to the model-name parser, got nothing fromUDW, andshow power inlineprinted:A catalogue entry that names a budget in prose but not in the field is the "presence is not correctness" failure this repo already ate once with the PBE-5AC-Gen2, in mirror image: here the device is present, the number is not.
What the vendor does publish (read today, Ubiquiti hosts, crawler UA):
dl.ui.com/ds/udw_ds.pdfSo the 112 W that had been sitting in the description was the device draw, not a PSE budget - off by a factor of nearly four if anyone had read it as one. PR #1979 adds
poe.budgetW: 420, adds10Mto the 17 GbE ports'speedCaps, and spells out "excluding PoE output" in the description. It references this issue, it does not close it.Unchanged blocker for #130 itself: nothing resellers or Ubiquiti publish describes
UDW-PRO. Today's re-check of the four storefront/spec URLs above found exactly one wall console -UDW (420W)- andtechspecs.ui.com/unifi/cloud-gateways/udw-prostill returns the techspecs home page (609,911 B) rather than a product.What would unblock it: a Ubiquiti page, datasheet, FCC exhibit or quick-start guide naming UDW-PRO's ports and PoE budget, or you confirming you meant the UDW (420 W), which is now modelled with the budget the engine actually reads.
Still blocked on the Pro - no new UDW-PRO source - but the gap underneath the request was real and is now filled: the base UDM was not in the catalogue. PR #2007 (references this issue, does not close it).
devices/ubiquiti/carried the Dream Machine line at five of its six published members -UDM-Pro,udm-se,udm-pro-max,udm-beast,udw- and not the 2019 base UDM. So a lab asking for what this request asks for (a console gateway that routes, NATs and runs DHCP) had every variant except the original. Census from the vendor's own sheet,dl.ui.com/ds/udm_ds.pdf(200, 747,030 B,application/pdf):(4) LAN: GbE RJ45 ports,(1) WAN: GbE RJ45 port, no SFP, no PoE,Max. power consumption 26W.Worth recording while reading it:
techspecs.ui.com/unifi/cloud-gateways/udmanswers 200 at 608,032 B and prints no networking-interface row at all - onlyManagement interface: Ethernet, Bluetooth. The datasheet carries the ports; the tech-spec page for this model carries prose. A pass that trusted the 200 would have written five ports from nowhere.Today's re-check of the Pro (one URL, thirty seconds).
techspecs.ui.com/unifi/cloud-gateways/udw-pro- 200, 609,911 B, final URLhttps://techspecs.ui.com/(the fallback page, unchanged). The live gridtechspecs.ui.com/unifi/cloud-gateways- 200, 610,412 B, sixteen cards,Dream Walland nothing beside it,udw-prooccurring zero times.One control for the Wayback result already on this thread, so it is not re-run: instead of the availability API, the archive's path index was enumerated.
web.archive.org/cdx/search/cdx?url=techspecs.ui.com/unifi/cloud-gateways/*&collapse=urlkey&filter=statuscode:200returns 104 archived URLs covering 18 product slugs -ef-core efg ucg-fiber ucg-industrial ucg-max ucg-ultra udm udm-beast udm-pro udm-pro-max udm-se udr udr-5g-max udr7 udw ux ux7 uxg-max- and noudw-proin any spelling, while.../udwis captured six times between 2025-11-27 and 2026-11-03 anddl.ui.com/ds/udw_ds.pdfsince 2022-05-06. The archive crawls these exact paths; it has never seen a Pro one. The retail side agrees:store.ui.com/us/en/collections/unifi-dream-wallsnapshots of 2023-05-24 and 2024-03-02 are real product pages (UDW,$999,Add to Cart) with zero occurrences ofudw-proordream wall pro.Unchanged blocker: nothing Ubiquiti publishes names UDW-PRO's ports or PoE budget, because nothing Ubiquiti publishes names UDW-PRO. Unblock: a vendor page, datasheet, FCC exhibit or quick-start for the Pro, or confirmation that the UDW (420 W) - or now the UDM - is what was meant.
Reopened (2026-11-18 18:30 UTC). This request was closed at 18:00:05Z by the merge of PR #2005 - a PR about
USW-Ultrawhose own body says it does not answer this request. The tracker reads a disclaimed keyword-plus-number anywhere in a pull request body as an instruction to act, so the disclaimer executed the thing it disclaimed.Nothing changed underneath: no Ubiquiti source for UDW-PRO has appeared,
devices/ubiquiti/has no spec for it, andresearch/open-device-requests.jsonstill declares it blocked. Perdocs/RESOLUTIONS.mdthe only close a device request gets is one where the catalogue answers it and the closing comment names the file - so this returns to the open queue.Blocker unchanged since the 2026-11-17 sweep (no re-walk needed): the SKU is absent from Ubiquiti's cloud-gateway index, has no tech-spec page, no store listing in US/UK/EU, no FCC grant under
SWX-UDWPRO/SWX-UDW-PRO/SWX-UDW2, and no Wayback capture. What would answer it: a Ubiquiti page, datasheet, FCC exhibit or quick-start guide naming UDW-PRO's ports and PoE budget, or the requester confirming they meant the UDW, which is catalogued atdevices/ubiquiti/udw.jsonwith the 420 W budget published on https://techspecs.ui.com/unifi/cloud-gateways/udw.Re-checked 2026-11-18 22:5x UTC. Still blocked - but the last naming-convention hypothesis is now measured shut with controls, and the row a requester settles for instead was modelled twice. PR #2049 carries both:
research/ubiquiti-udw-pro-doc-slug-controls.mdanddevices/ubiquiti/UDM-Pro.json. Issue 130 stays open.Why the earlier negative was weaker than it read. Every "no datasheet" result on this thread came from a
_dsURL, so it only ever excluded one spelling. The control that settles it:https://dl.ui.com/ds/udm-pro.pdfanswers 200, 353,553 B, application/pdf, whilehttps://dl.ui.com/ds/udm-pro_ds.pdf- the suffixudw_ds.pdfandudm_ds.pdfuse - 302s tohttps://techspecs.ui.com._dsis one of two conventions, not the convention, and a 302 on a_dspath was never evidence of an absent file.Both trees, every spelling (measured today, no redirect following, Chrome UA). Bare slug under
dl.ui.com/ds/:udw-pro.pdf302/285 B,udwpro.pdf302/304 B,udw_pro.pdf302/305 B,udw-pro_ds.pdf302/308 B,udw-pro-1.pdf302/307 B. Quick-install-guide tree, which is server-rendered and slug-addressed:qig/udw/200/6,310 B,qig/udm-pro/200/6,185 B, againstqig/udw-pro/302/313 B andqig/udwpro/302/312 B. All seven Pro probes land on the same 609,911-byte front page.Still missing, exactly: (1) any Ubiquiti statement of the Pro's RJ45 and SFP+ counts and their rates; (2) its PoE budget and per-port maxima, which the non-Pro sheet gives per class as 15.4 / 30 / 60 W; (3) any vendor document that names the SKU at all.
What would unblock: a Ubiquiti datasheet, quick-start guide, tech-spec page or FCC exhibit for the Pro under any slug, or the requester confirming the UDW (
devices/ubiquiti/udw.json, 420 W) or now the UDM-Pro is what was meant.Catalogue work done in the same pass, on the box this request would be answered with.
devices/ubiquiti/described the UDM-Pro twice, and the entry carrying the model string modelled the second 10G cage as a bareethernet 10Gport with no connector - one cage plus a 10G port nothing can seat in - while the other copy carried the right count under model"UniFi Dream Machine Pro", categoryhostand the engine'shostcapability (an end device that terminates packets) on a gateway. Now one file, census fromhttps://dl.ui.com/ds/udm-pro.pdf: 9x 1G RJ45 (1 WAN + 8 LAN) and 2x 10G SFP+, no PoE, 33 W max; tech-spec page prints the same count (1 GbE RJ45 = 9,10G SFP+ = 2). Registry: 2,356 models, Ubiquiti 369 -> 368.Re-checked 2026-11-18 23:2x-23:4x UTC. Still no vendor source for UDW-PRO, but the FCC question is now answered by enumeration instead of by sampling, and the store tree has been swept for the first time. PR #2051 carries the evidence (
research/ubiquiti-swx-grantee-census.md). Issue 130 stays open - the request is unanswered.Why the earlier FCC result was weaker than it read.
SWX-UDWPRO,SWX-UDW-PROandSWX-UDW2are three guesses. Grantee codeSWXis a finite list, so this pass read the list:https://fccid.io/SWXis server-rendered and paginated, "Page 1 of 5", and all five pages answer 200 (30,975 / 30,185 / 29,647 / 29,861 / 17,622 B). Extracted fromtable.grantee-applications-tableand de-duplicated: 432 unique grants,SWX-AP1R22005-02-18 toSWX-USLAK2026-10-29.The only Dream Wall in those 432 is
SWX-UDW2022-05-31. The control that makes the absence mean something:SWX-UDMPRO2019-07-23,SWX-UDMPM2024-04-23,SWX-UDMPROSE2021-07-05 andSWX-UXGPRO2020-06-04 are all rows in the same list. Ubiquiti files Pro variants as their own grants, so a Pro Dream Wall would appear as one. Two liveness controls: the newest row is five weeks old (the index is maintained) and the oldest is from 2005 (it is not a "recent applications" view that would drop an older filing).No Pro hides inside the parent grant.
https://fccid.io/SWX-UDW- 200, 83,318 B: product codeUDW, four application IDs, every oneOriginal Equipment(2022-05-23 x2, 2022-05-31 x2), none a permissive change, modelUDW, and the stringprooccurs zero times in the page.The store tree, both prefixes. Earlier passes enumerated
techspecs.ui.com/unifi/cloud-gateways/*(104 URLs, 18 slugs). The store tree was never done, and it is the one that would carry a launch page.store.ui.com/us/en/pro/products/returns 234 archived URLs containing onlyudw(2023-11-27, 200) anduacc-psu-udw(2023-12-27, 200);store.ui.com/us/en/products/filtered toudwreturnsuacc-psu-udw,udw,udw?variant=udw-usand two mangled 404s. Noudw-pro,udwproorudw_proin any year. Live-crawl control:udw?variant=udw-uswas captured 2026-04-28, six months ago, with a real variant query string - the archive is still crawling this product, so the empty Pro result is a gap in the product line, not in the crawl.Recorded so nobody over-reads it. (1) A radio-identical variant could ship under a Class II permissive change, so what is ruled out is a filed authorization, not the possibility of the product. (2) Even a Pro grant could not answer this request - a grant publishes frequencies and output power, never RJ45 counts or a PoE budget. So the disposition does not change: the census has to come from a Ubiquiti page.
Still missing, exactly: (1) the Pro's RJ45 and SFP+ counts and their rates; (2) its PoE budget and per-port maxima; (3) any vendor document naming the SKU.
What would unblock it: a Ubiquiti page, datasheet, quick-start guide or FCC exhibit for the Pro under any slug, or the requester confirming the UDW (
devices/ubiquiti/udw.json, 420 W) or the UDM-Pro is what was meant.Instrument worth keeping: archived Ubiquiti store product pages are not client-rendered the way the store search is - they embed the whole product record as JSON. From the 2025-02-18 capture of
store.ui.com/us/en/products/uacc-psu-udw(354,417 B):"name":"UACC-PSU-UDW","description":"Provides optional power redundancy for Dream Wall","status":"Available","datasheet":{"html":...},"technicalSpecification":null.datasheetandtechnicalSpecificationare readable out of the HTML for any store product the archive holds - a cheaper route thandl.ui.comfor the products that do have pages.Wayback was intermittent during this sweep (domain-wide filtered CDX 504'd twice, then the service returned Temporarily Offline); every negative above is a 200 with a row count, and none rests on a timeout.
Re-checked 2026-11-19 00:5x-01:0x UTC. Still blocked - but the SKU has now been looked for on the one vendor surface that a shipped product cannot avoid: the firmware index, not a marketing page. PR #2062 carries it (
research/ubiquiti-firmware-platform-census.md+scripts/ubiquiti-firmware-index.js). No spec was added; #130 stays open.Why this surface is different.
https://fw-update.ubnt.com/api/firmwareis the release index the update daemon on the device itself polls, and it is keyed by platform code - the code that names the binary (/data/unifi-dream/2d04-UDW-6.0.17-…bin). A product page can be delisted or never written; a device that ships has firmware, and the index says under which code.The census (
filter=eq~~product~~unifi-dream,limit=1000- the default page size is 25, which undercountsUDWat 25 instead of 27): 340 releases across 17 platform codes -UDM27,UDMPRO27,UDMPROSE40,UDMPROMAX20,UDR36,UDR5G9,UDR717,UDRULT22,UDW27,UX15,UXMAX15,UCGF17,UCGMAX19,UCGA6AD10,EFGCORE8,UDMENT21,UDMEA4C10.UDWruns 2022-05-07 to 2026-11-10, latestv6.0.17+7bcad58- the start matches the May 2022SWX-UDWgrant, the end is nine days old, so neither end of the range truncates.No
UDWPRO.UDWPRO,UDW-PRO,UDWPROMAX,UDW2,UDWSE,UDWMAX: each a 96-byte 0-release envelope, byte-identical to the nonsense controlZZZZ, i.e. an empty answer from a working query - not a probe that failed to answer. Positive control on the same endpoint and field:UDWat 27. Controls that make the absence mean something:UDMPRO65,UDMPROSE40,UDMPROMAX20,UXMAX15 - Ubiquiti gives Pro variants their own code even for three near-identical consoles, so the "it shares the parent's code" hypothesis is contradicted four times inside this very family.What this settles: no Dream Wall Pro platform has ever received firmware, which joins the grant enumeration, the store tree and the tech-spec tree in saying the SKU has left no trace on any surface a shipped product must touch.
What it does not settle: a rebadged variant on the parent mainboard could still hide under the
UDWcode, and no firmware index publishes port 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 (
devices/ubiquiti/udw.json, 420 W on https://techspecs.ui.com/unifi/cloud-gateways/udw). Re-runnable:node scripts/ubiquiti-firmware-index.js --family UDWPRO,UDW-PRO,UDW2.Re-checked 2026-11-19 02:5x-03:1x UT. Still no census; PR #2076 records this pass. The request stays open (Refs #130, no close).
Two new things, one of them a correction to what this thread has been repeating.
1.
techspecs.ui.comcan 404 — on a SKU-keyed sub-tree. The build manifest (/_next/static/O4loEueJJ_fzZc5I2r7Ta/_buildManifest.js, 200, 3,349 B) shows product paths are dynamic routes over 13sortedPages, so there is no static route list — but it exposed/compliance/chile/[[...sku]], the SUBTEL register:.../compliance/chile/udwDream Wall,UDW,UDW-EU.../compliance/chile/udw-pro404 - This page could not be found.../compliance/chile/udwpro.../compliance/chile(index).../compliance/udw(no locale)/The caveat recorded above — "a 200 on this host is meaningless, so the negative is unfalsifiable" — does not reach this route: it answers a real status per SKU. The Pro is absent from it too. (Weigh it honestly: it is Chile type-approval, so absence there alone would only mean "not certified for Chile". Its value is that the host can 404.)
2. The "Coming Soon" sentence is a forum reprint, not Ubiquiti copy. This thread and the ledger cite "the Dream Wall and Dream Wall Pro (UDW/UDW Pro)" beside "Dream Wall Pro - Coming Soon" as Ubiquiti's Early-Access copy. It has no Ubiquiti URL — its only citation is
ubiquiti-networks-forum.de/board/thread/4925-.... Wayback has no 2022 capture of anystore.ui.comudw page (earliest 2023-06-03) or anyui.comdream-wall page (earliest 2023-10-18), so that page was never crawled. I have demoted it inresearch/open-device-requests.json. It therefore cannot carry the "not a shipping product, therefore closable" inference in the note's last paragraph —docs/RESOLUTIONS.mdkeeps a request like this open.3. The UDW fallback is now confirmed off techspecs. Archived collection page
store.ui.com/us/en/collections/unifi-dream-wall/products/udw@ 20230603042814 (200, 124,982 B): navigation lists Dream Wall / Dream Machine / Dream Router only; the box is (17) LAN GbE RJ45, (1) WAN 2.5 GbE RJ45, (1) LAN + (1) WAN 10G SFP+, PoE (4)/(4)/(4); zero hits forDream Wall Pro,udw-pro,Coming Soon. It matchesdevices/ubiquiti/udw.jsonfield for field (20 interfaces), so no spec change was warranted.Still missing, exactly: (1) the Pro's RJ45 and SFP+ counts and rates; (2) its PoE budget and per-port maxima; (3) any Ubiquiti-hosted document naming the SKU.
What would unblock it: unchanged — a Ubiquiti page, datasheet, quick-start guide or FCC exhibit for the Pro, or the requester confirming they meant the UDW (
devices/ubiquiti/udw.json) or the UDM-Pro.Re-checked 2026-11-19 03:2x UT. Still no census; PR #2079 records this pass. The request stays open (Refs #130).
Two surfaces this thread had named but never resolved. Both were reached from the UDW techspecs page's own
__NEXT_DATA__rather than from a guessed URL, and neither publishes the Pro.1. The page publishes its own storefront list - and the Pro is absent from all nine.
props.pageProps.product.alternativeStoresontechspecs.ui.com/unifi/cloud-gateways/udwnames/br /ca /eu /jp /me /mx /tw /uk /us. Product-keyed probe with control per store:/{store}/en/products/udwis 200 on all nine (492,349-589,781 B) and/{store}/en/products/udw-prois 404 on all nine - one page, byte-identical 204,279 B (md5 346734f60828bb9d80819a8092b2d291on us/eu/tw). Non-US hosts 307 fromstore.ui.comto{store}.store.ui.com, which is routing, not a miss. Earlier passes read the US and EU category grids; this is the product-keyed test across every storefront Ubiquiti's own page lists.2. The quick-start key is
dl.ui.com/qig/<slug>.pdf, not the/qs/pattern a previous pass guessed - it is inproduct.documentsashttps://dl.ui.com/qig/udw.qig/udw.pdf= 200,application/pdf, 8,279,805 B;qig/udw-pro.pdf,qig/udwpro.pdfand theqig/bogus-xyz.pdfcontrol all 302 to the techspecs root;qig/udw-eu.pdfalso misses, so the key is per SKU, not per region. That makes the Pro negative tested rather than untried - but it also closes the "the quick-start prints the layout" hope as a machine-readable route: the UDW QIG is one page of Illustrator 28.0 artwork with zeroBT/Tj/TJoperators and no/ActualText. Every label is outlined. A Pro QIG would have to be read by eye, not parsed.Still missing, exactly: the Pro's RJ45 and SFP+ counts and rates, its PoE budget and per-port maxima, its drive bays and WAN options.
product.technicalSpecificationfor the UDW (420WPoE,112W (Excluding PoE output), Default WAN Ports(1) 2.5 GbE RJ45+(1) 10G SFP+) agrees with the datasheet and withdevices/ubiquiti/udw.json, so there is still no spec to write and nothing to correct.What would unblock it: unchanged - a Ubiquiti page, datasheet, quick-start, FCC exhibit or storefront entry naming
UDW-PRO, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json) or the UDM-Pro.Re-checked 2026-11-19 03:5x UT. Still no census; PR #2084 records this pass. The request stays open (Refs #130).
Two Ubiquiti hosts this thread had never read, both of which enumerate products by name, and both of which answered a control correctly — so their emptiness is a tested negative.
1. The marketing family page publishes a product
ItemList.https://ui.com/cloud-gateways(200, 446,725 B) carries a schema.orgItemListof 14 cloud gateways with their tech-spec URLs. Item 4 isDream Machine Pro Max, item 6Dream Machine Pro, item 13Dream Wall→/unifi/cloud-gateways/udw.udw-prooccurs 0 times,Dream Wall Pro0 times — and Pro variants are plainly not filtered out of this list, since two of the fourteen carry the suffix. Caveat, stated because the number matters: this list is curated to 14 while the techspecs grid carries 16 (udranduxare missing), so it corroborates the absence; the grid remains the exhaustive enumeration.2. The support knowledge base is Zendesk, so its index is public.
https://help.ui.com/api/v2/help_center/articles/search.json?query=<q>countdream wall proudw-proudw73 rows → 50 unique articles, and across every title and body
Dream Wall Pro,UDW-PROandUDWPROoccur zero times. The box appears only asDream Wall (UDW)(Consoles with UniFi Access Support; SD-WAN with Site Manager; Upgrading to UID Enterprise, which marks the UDW itself(EA); Recovery Mode). Control: the same endpoint withquery=udm-proreturns 200, 1,737,208 B, 100 of 118 rows, containingUDM-PRO39 times andDream Machine Pro18 times — the index does hold Pro-suffixed console names, it just has none for the Dream Wall.A trap for whoever checks this next:
https://ui.com/robots.txt(200, 367 B) declaresSitemap: https://ui.com/sitemap.xml, and that sitemap is real (200, 8,712 B, 81<loc>) — but it indexes sections, not SKUs (/cloud-gateways,/how-it-works/multi-site, …), and contains zerodream. Absence from it proves nothing about any Dream Wall; do not count it as evidence either way.Incidental, and deliberately not a spec change: UniFi Recovery Mode says "Connect to the Dream Wall via Port 18, not Port 1." That is a vendor statement that the UDW has at least 18 numbered Ethernet ports, consistent with the 17 LAN + 1 WAN RJ45 already in
devices/ubiquiti/udw.json(20 interfaces with the two SFP+). It corroborates; it adds no field.Still missing, exactly: the Pro's RJ45 and SFP+ counts and rates, its PoE budget and per-port maxima, its drive bays and WAN options. Nothing was modelled from the non-Pro's numbers.
What would unblock it: unchanged — a Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry or KB article naming
UDW-PROwith its ports and PoE budget, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json) or the UDM-Pro.Re-checked 2026-11-19 04:2x UT. Still no census; PR #2088 records this pass. The request stays open (Refs #130, no close).
Every pass above tested the store as a page:
/{store}/en/products/udw-pro404 in all nine storefronts. A 404 route can sit in front of a row that still exists, so this pass asked the commerce backend behindstore.ui.cominstead -POST https://ecomm.svc.ui.com/graphql, whose per-SKU lookup answers anonymously.The instrument, and its controls. It returns retired products and resolves names they used to have, which is what makes a miss usable:
udwis FOUND withdisplaySkuUDW (420W),statusSoldOut,historicalSlugs["dream-wall","dream-wall-ea","udw","unifi-dream-wall"];udmFOUNDSoldOut;udm-proanducg-fiberFOUNDAvailable.The Pro, at the database, from all nine storefronts. The not-found error carries
extensions.alternativeStores- the catalogues that do hold the SKU:udw(control)udw-proSoldOut[][]The non-US controls are the load-bearing rows: from
euthe UDW is absent from that catalogue and the API lists all nine storefronts that have it. The same query forudw-prolists nothing, from all nine. Five spellings -udw-pro,udwpro,udw-pro-us,dream-wall-pro,dreamwallpro- all miss with an empty store list.What this does not prove, stated because it matters here. The API purges rows -
usganduxgalso answer NOT_FOUND whileudmandudrare found - so "no record now" is not "never shipped". It rules out a delisting (SoldOutrows are still served) and it rules out a regional SKU at the database rather than in a page route; it does not manufacture a census.Still missing, exactly: the Pro's RJ45 and SFP+ counts and rates, its PoE budget and per-port maxima, its drive bays and WAN options. Nothing was modelled from the non-Pro's numbers, and
devices/ubiquiti/udw.jsonis unchanged.New traps recorded so they are not re-walked:
store.ui.com/robots.txt,/sitemap.xmland/products.jsonall 404 with the same 204,279-byte page (no product index, not Shopify); introspection on that API is refused (400); GraphQL validation errors are masked as N copies ofInternal Server Error, so only the error count is an oracle; and the list querystorefrontProductsis unusable anonymously (four masked errors for every input tried), so the surface is slug-at-a-time.What would unblock it: unchanged - a Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry or KB article naming
UDW-PROwith its ports and PoE budget, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json) or the UDM-Pro.Re-checked 2026-11-19 04:5x UT. Still no UDW-PRO census; PR #2093 repairs the row the requester would settle for instead, and does not close this. The request stays open (Refs #130).
This pass did not re-walk the Pro surfaces - they are exhausted and the previous sixteen comments record where each ends. It fixed the one real defect sitting underneath the fallback answer that this thread points at.
The bug, measured on main.
devices/ubiquiti/UDM-Pro.jsonmodelled the second 10G cage as a bareethernet 10Gport with no connector - one cage plus a 10G socket nothing can seat - andunifi-dream-machine-pro.jsondescribed the same box again under a product name, categoryhost, with the engine'shostcapability (an end device that terminates packets) on a gateway.Vendor census, read today.
https://dl.ui.com/ds/udm-pro.pdf(200, 353,553 B, 2 pp, text layer):Networking interface (8) LAN: GbE RJ45 ports/(1) WAN: GbE RJ45 port;SFP+ interface (1) LAN: 10G SFP+/(1) WAN: 10G SFP+; IDS/IPS 3.5 Gbps; 33 W max.https://techspecs.ui.com/unifi/cloud-gateways/udm-pro(200, 676,527 B) prints the same as a table:1 GbE RJ45 = 9,10G SFP+ = 2. So 9 copper + 2 cages, no PoE.The control this exposed, now applied to the Pro:
dl.ui.com/ds/udm-pro.pdfis a real datasheet while its_dstwin 302s to the techspecs front page - so_dsis one of two conventions, not the convention, and no earlier "no datasheet" reading taken from a_dsURL was decisive. The bare-slug and QIG trees were then read with live controls:qig/udw/200/6,310 B andqig/udm-pro/200/6,185 B againstqig/udw-pro/andqig/udwpro/302/313 B and 302/312 B;ds/udw-pro.pdf,udwpro.pdf,udw_pro.pdf,udw-pro_ds.pdf,udw-pro-1.pdfall 302 tohttps://techspecs.ui.com. Every figure re-measured this pass, none carried over. Research:research/ubiquiti-udw-pro-doc-slug-controls.md.Still missing, exactly: the Pro's RJ45 and SFP+ counts and rates, its PoE budget and per-port maxima, its drive bays and WAN options. Nothing was modelled from the non-Pro UDW.
What would unblock it: unchanged - a Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry or KB article naming
UDW-PROwith its ports and PoE budget, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json) or the UDM-Pro (devices/ubiquiti/UDM-Pro.json, now correct).2026-11-19 05:3x UT — no new UDW-PRO source; PR #2096 repairs the fallback row instead. This request stays open (Refs #130).
The Pro surfaces were not re-walked: the sixteen comments above end each one, and nothing on this thread has changed since 05:00. What was wrong underneath is that the row this thread offers as the nearest real alternative —
devices/ubiquiti/udr-5g-max.json, the only UniFi console here with a 5G modem — had no cellular port at all, so a lab could not build the "cellular WAN" this request asks for out of it. It now carrieswwan0at the vendor's 3.4 Gbps 5G NSA downlink (https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-max, structured spec table), plus the 15.4 W PoE budget the row was missing, soshow power inlineanswers instead of refusing.Still missing for the Pro itself, unchanged: its RJ45 and SFP+ counts and rates, PoE budget and per-port maxima, drive bays and WAN options. Nothing was modelled from the non-Pro UDW. What would unblock it is also unchanged: a Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming they meant the UDW, the UDM-Pro, or the UDR-5G-Max.2026-11-19 05:5x UT - no new UDW-PRO source; this pass fixed the family the request falls back into. PR #2101 references this issue and does not answer it; the request stays open.
Nothing about the Pro was re-read: the comments above end every vendor surface (techspecs grid,
dl.ui.com,qig/, the nine storefronts, grantee code SWX, the firmware platform index, the Chile compliance register, the Zendesk KB index, Wayback) and no pass has anything new to add to them.What was wrong underneath the standing answer: four UniFi cloud-gateway rows - UDR, UDR7, UDM-SE, UCG-Industrial - declared
poe-pseand carriedpoeOutports while their own vendor page prints a PoE budget (40 W / 15.4 W / 180 W / 270 W on DC input). The allocator skips a PSE whose budget is 0, so none of those boxes could power one device. They now carry the budget with its source; UDM-SE also gained thesourceUrlit never had.scripts/audit-poe-budget.js: 112 -> 108 of 402 PSEs unaskable.UCG-Fiber's 30 W is still unwritten on purpose: the same table marks no PSE port and the product ships only a QIG.
Still missing for the Pro, unchanged: its RJ45/SFP+ counts and rates, PoE budget and per-port maxima, drive bays and WAN options. Unblock unchanged: a Ubiquiti-hosted page, datasheet, grant exhibit, quick-start or KB article naming
UDW-PRO, or the requester confirming the UDW, UDM-Pro or UDR-5G-Max was meant.2026-11-19 06:2x UT - no new UDW-PRO source; PR #2105 fills the PoE gap in the family this request falls back into. This request stays open (Refs #130, no close).
The Pro surfaces were not re-walked - the comments above end each one, and none has changed since 06:05.
What was wrong underneath:
devices/ubiquiti/ucg-fiber.jsonprintedPoE Budget = 30Win the tech-spec table while marking no port PoE, and the row carried no PSE at all, so a lab could not power one access point from the 30 W gateway. The class was published on a vendor surface no pass on this thread had read for it: the store product page,https://store.ui.com/us/en/products/ucg-fiber(200, 595,865 B, server-rendered,displaySkuUCG-Fiber (30W)), whose key features read "Integrated 4-port switch with (1) PoE+ port" - one 802.3at port among the four 2.5G RJ45, against a 30 W budget. Port 1 now carries it; which port number is still unpublished on either host, andpoe.notesays so.UCG-MaxandUCG-Ultra, the other two fallback rows, gained thesourceUrlneither had.Still missing for the Pro itself, unchanged: its RJ45/SFP+ counts and rates, PoE budget and per-port maxima, drive bays and WAN options. Nothing was modelled from the non-Pro UDW. Unblock unchanged: a Ubiquiti-hosted page, datasheet, grant exhibit, quick-start or KB article naming
UDW-PRO, or the requester confirming the UDW, UDM-Pro or UDR-5G-Max was meant.2026-11-19 06:5x UT - no Dream Wall Pro source; one more Ubiquiti surface read (and it is empty too), plus the Pro Max row underneath this request is now sourced. PR #2111; this request stays open.
New surface, not on this thread: the gateway lineup as structured data.
https://ui.com/cloud-gateways(HTTP 200, 446,725 B) is the marketing page, not the techspecs grid, and it publishes its whole gateway list as a JSON-LDItemList- fourteen products, each with its techspecs URL:ef-core,efgudm-beast,udm-pro-max,udm-se,udm-proucg-max,ucg-fiber,ucg-ultra,ucg-industrialudr-5g-max,udr7udw,ux7The string
udw-prooccurs zero times in those 446,725 bytes, and the Dream Wall entry isname: "Dream Wall"->techspecs.ui.com/unifi/cloud-gateways/udw. That is the third independent Ubiquiti index (techspecs category grid, EU store grid, this JSON-LD) agreeing, and it is machine-readable rather than a rendered card - so it cannot be a locale slug or a lazy-loaded miss.https://ui.com/sitemap.xml(200, 8,712 B,application/xml, 81 URLs) lists marketing pages only - no product slugs, noudw, so it adds nothing either way.https://blog.ui.com/answers 200 at 950,148 B but contains zero occurrences ofunifi: the blog is client-rendered, so its emptiness is not evidence.What was wrong underneath, and is now fixed (PR #2111).
devices/ubiquiti/udm-pro-max.json- the 1U sibling a Dream-series requester is most likely to be handed - carried nosourceUrland no notes at all, and the engine'sisPoePd()name match onunifihad turned its nine copper ports into a 12.95 W 802.3af draw, i.e. a rack console that could be "powered" from a PoE switch. Both vendor tables (techspecs.ui.com/unifi/cloud-gateways/udm-pro-max, 677,375 B;store.ui.com/us/en/products/udm-pro-max, 598,527 B,displaySkuUDM-Pro-Max) give the same census - 8x 1GbE + 1x 2.5GbE + 2x 10G SFP+, max 8 WAN ports, 60 W max draw, AC + USP-RPS DC power - and the store table marksPoE Support,PoE Budgetand every per-port PoE wattage Empty. The row now says so, so it cannot inheritudm-se.json's 8 PoE ports and 180 W.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, PoE budget and per-port maxima, drive bays and WAN options. Nothing was modelled from the non-Pro UDW. Unblock also unchanged: a Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming the UDW (devices/ubiquiti/udw.json), the UDM-Pro (devices/ubiquiti/UDM-Pro.json) or the UDM-Pro-Max (devices/ubiquiti/udm-pro-max.json) was meant.2026-11-19 07:2x UT - still blocked on the Pro; Pro surfaces not re-walked (last pass 07:02, nothing has changed). One citation defect found in the row a requester is handed instead:
devices/ubiquiti/ux.jsoncitedtechspecs.ui.com/unifi/unifi-cloud-gateways/ux, which answers 307 ->/unifi/cloud-gateways, 21 bytes - the category grid, not the product page. Corrected totechspecs.ui.com/unifi/cloud-gateways/ux(200, 670,206 B), which prints the census the row already modelled (Max. WAN Port Count 1, Default WAN Ports (1) GbE RJ45, Port Layout 2 at 1G/100M/10M, max 10 W over USB-C). PR #2115 carries it; refs this issue, does not close it. It is the only file indevices/ubiquiti/with that path shape.Still missing, unchanged: the Pro's RJ45 and SFP+ counts and rates, PoE budget and per-port maxima, drive bays and WAN options. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit or storefront entry naming
UDW-PRO, or confirmation that the UDW, UDM-Pro or UDR-5G-Max was meant.2026-11-19 08:0x UT - still blocked on the Pro; the last unread Ubiquiti host is now read and it is empty too. This request stays open. PR #2118 records one catalogue defect found underneath it.
New surface, not on this thread: the UniFi Design Center.
https://design.ui.com/is the planning tool whose device library would carry a wall console with its port count, so it was worth one read. It is a client-rendered SPA:/,/api/devices,/api/v1/devices,/api/models,/api/v1/models,/api/products,/api/catalogand/api/model-listall answer 200 with the identical 8,107-bytetext/htmlrouter shell, and neither the loader/assets/index-Dhm9edlX.js(200, 27,897 B) nor/assets/Main-Dq_3TtAr.js(200, 220,557 B) names a model endpoint - the developer pages (/assets/DeveloperModelsPage-DG8YuRfL.js, 1,601 B) are stubs. So the library is not reachable anonymously, and a 200 on this host is the SPA, not a page: its silence cannot be cited as a negative either way. Same shape as the client-renderedstore.ui.com/us/en/searchresult already trapped above. Recorded inresearch/open-device-requests.json.What was found instead (PR #2118).
devices/ubiquiti/uxg-pro.json- the Pro-suffixed 1U gateway a Dream-series requester is otherwise handed - carried nosourceUrlat all, and its two copper ports were drawing a phantom 12.95 W each throughisPoePd()'sunifimatch: 25.9 W against a switch budget on a box fed by a 50 W internal AC/DC supply. The row now citeshttps://dl.ui.com/ds/uxg-pro_ds.pdf(200, 433,832 B, two pages, text layer: LAN: (1) 1 GbE RJ45 + (1) 10G SFP+ / WAN: (1) 1 GbE RJ45 + (1) 10G SFP+),https://techspecs.ui.com/unifi/cloud-gateways/uxg-pro(200, 649,578 B: Max. WAN Port Count 3, 10G SFP+ = 2, 3.5 Gbps IDS/IPS, 1U) andhttps://store.ui.com/us/en/products/uxg-pro(200, 504,342 B, every PoE field Empty), and its copper ports saypoeIn: false. The tech-spec page's Port Layout group enumerates only the two cages, so it is not cited for the copper count. Trap:dl.ui.com/ds/uxg_pro_ds.pdfanswers 302 to the techspecs root, so the datasheet key is hyphenated per SKU.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, the PoE class mix and total budget, drive bays and its WAN/cellular options - the whole census. Nothing was modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json) or UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) was meant.2026-11-19 08:2x UT - still blocked on the Pro; nothing on the Pro re-walked (last pass 07:58, no surface has changed). PR #2121 records the catalogue defect found underneath this request.
The Pro surfaces were not re-read again today, so this pass spent its increment on the family a Dream-Wall requester is otherwise handed. The UXG family - the row this thread already pointed at, now that #2118 gave
uxg-proits datasheet - still had the same defect on all four remaining members:isPoePd()matchesunifiin the model/label, so every silent copper port became a 12.95 W 802.3af draw.uxg-lite.jsonuxg-max.jsonuxg-enterprise.jsonuxg-fiber.jsonAll four now say
poeIn: falseon their copper sockets, cited totechspecs.ui.com/unifi/cloud-gateways/{uxg-lite,uxg-max,uxg-enterprise,uxg-fiber}(200; 643,116 / 647,803 / 671,598 / 649,433 B - each printing its own Port Layout, Max. WAN Port Count and Power Method) and to the matching store rows, where PoE Budget is flagged Empty. Port counts did not move: 2x 1G, 5x 2.5G, 2x 2.5G + 2x 10G SFP+ + 2x 25G SFP28, and 4x 2.5G + 1x 10G RJ45 + 2x 10G SFP+.One open field recorded rather than guessed.
uxg-fiberdoes source power - PoE Budget 30 W, per-port PoE+ 30 W at 50-57 V, and the store says "Integrated 4-port switch with (1) PoE+ port" - but Ubiquiti never says which of the four 2.5G ports it is, and the SKU has no datasheet (datasheet: nullin the store payload;dl.ui.com/ds/uxg-fiber_ds.pdflands on the 609,911-byte techspecs front page, the miss this thread already trapped). Naming a port would be a guess, and a 30 W budget with no PSE port failstest/poe-inference.test.js. That needs a Ubiquiti diagram or QSG numbering the port, or the datasheet.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, the PoE class mix and total budget, drive bays and its WAN/cellular options - the whole census. Nothing was modelled from the non-Pro UDW. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json) or UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) was meant.Still phantom, for the next pass:
UCG-Ultra.json(wan1 + port1-4, 64.75 W) andUDM-Pro.json(wan1 + port1-8, 116.55 W) are the last two gateway rows indevices/ubiquiti/drawing PoE they cannot accept.2026-11-19 08:5x UT - still blocked on the Pro; the Pro surfaces were not re-read (last pass 07:58, nothing has changed). PR #2124 closes out the last item the previous pass left for the next one.
That pass ended with a note: "
UCG-Ultra.json(wan1 + port1-4, 64.75 W) andUDM-Pro.json(wan1 + port1-8, 116.55 W) are the last two gateway rows indevices/ubiquiti/drawing PoE they cannot accept." Both are now correct.devices/ubiquiti/UCG-Ultra.jsondevices/ubiquiti/UDM-Pro.jsonCited to
techspecs.ui.com/unifi/cloud-gateways/ucg-ultra(200, 657,109 B) and.../udm-pro(200, 676,527 B) - each printing its Port Layout, Power Method and Max. Power Consumption with zero occurrences ofPoEor802.3- and tostore.ui.com/us/en/products/{ucg-ultra,udm-pro}(200, 550,854 / 600,589 B), wherePoE Support,PoE BudgetandMax. PoE Wattage per Port by PSEare all flagged Empty.Trap worth recording, because it nearly went the other way. The
ucg-ultrastore payload does containPower Method = PoE / IEEE 802.3af, plus "PoE Integrated AC Adapter" and "PoE-powered 5G RedCap antenna" copy. Those are cross-sell specification blocks for other SKUs in the same GraphQL payload, not this console. The entries that belong to the product are the ones with the Empty flags. Taking the firstPoEstring on a store page would have invented a PD and a PSE on one box.Also found:
UCG-Ultrahas no datasheet -dl.ui.com/ds/ucg-ultra.pdfand.../ucg-ultra_ds.pdfboth answer 302 totechspecs.ui.com, the same silent fallback already trapped foruxg-fiber.UDM-Pro.jsoncarried a duplicatesourceUrlkey (JSON kept the last, the PDF); collapsed.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, the PoE class mix and total budget, drive bays and its WAN/cellular options - the whole census. Nothing was modelled from the non-Pro UDW. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json) or UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) was meant.2026-11-19 09:2x UT — still blocked on the Pro; the Pro surfaces were re-measured (not re-walked) and are unchanged; PR #2128 records the catalogue defect found underneath this request.
Pro, re-measured this pass (unchanged since 07:58)
techspecs.ui.com/unifi/cloud-gateways/udw-pro609,911 Blanding ontechspecs.ui.com/— the silent-fallback front page, not a product pagetechspecs.ui.com/unifi/cloud-gateways/udw704,702 B— the UDW, census unchangedtechspecs.ui.com/unifi/cloud-gateways610,412 B— still noudw-procardstore.ui.com/us/en/products/udw-pro204,279 Bdl.ui.com/ds/udw-pro_ds.pdf609,911 BHTML — same fallbackWhat this pass actually found (PR #2128). The request's stated lab is "NAT, DHCP, VPN, cellular WAN", so the rows a requester is handed for it are the two mobile routers — and both were uncited, with a dead PoE port underneath:
devices/ubiquiti/umr.json— nosourceUrl;notesquoted vendor figures with nothing behind them. Also the PoE passthrough had nopoe.budgetW, andengine/simulator.jsopens its allocator withif (!dev.poeBudget) continue;— so the port was skipped, not reported unknown: it could power nothing andshow power inlinesaid nothing about why. Now citestechspecs.ui.com/unifi/integrations/umr-us(200, 708,698 B: "(1) PoE input / (1) PoE output (Max. 10W, requires PoE+ switch)"; 9 W),dl.ui.com/ds/umr_ds.pdf(200, PDF, 597,924 B — ports yes, output wattage no, so the 10 W is a tech-spec-only figure) andstore.ui.com/us/en/products/umr-us(585,616 B, "PoE+ input required for PoE passthrough"). Budget 10 W,poeIn9 W instead oftrue, capabilitiespoe-pd/poe-pse/802.3at.devices/ubiquiti/umr-ultra.json— nosourceUrl; now citestechspecs.ui.com/unifi/integrations/umr-ultra-us(200, 682,619 B: "(2) FE RJ45 ports"; 5.7 W; no PoE row) and its store page (587,964 B). The Ultra has no datasheet — both slug spellings return the 609,911 B front page.Traps recorded in
research/ubiquiti-mobile-router-census.md: the-ussuffix is part of the slug on both hosts (/products/umris 404,.../integrations/umris the front page);/products/umr-ultra307s to a category, a 200 that is still a miss; neither surface numbers the PoE ports, so the row assigns one sink and one source on the vendor's stated count.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options — the whole census. Nothing was modelled from the non-Pro UDW. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit or storefront entry naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json), UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) or UniFi Mobile Router (devices/ubiquiti/umr.json, now cited) was meant. This request stays in the queue.2026-11-19 09:5x UT - still blocked on the Pro; the Pro surfaces were not re-read (last measurement 09:32, unchanged). PR #2132 closes the last item this family had open.
This pass finished the mobile-router family that the stated lab (NAT, DHCP, VPN, cellular WAN) actually reaches.
devices/ubiquiti/umr-industrial.jsonwas the third member and carried both defects #2128 fixed on the UMR:poe.budgetWsimulator.jsskips a PSE with no budget, so the port was dead andshow power inlinewas silenteth0.poeInSources:
techspecs.ui.com/unifi/integrations/umr-industrial-us(200, 693,659 B; the bare.../umr-industrial200s to the same bytes, unlike the UMR). No datasheet -dl.ui.com/ds/umr-industrial_ds.pdf,.../umr-industrial-us_ds.pdfand.../umr_industrial_ds.pdfall answer 200 with the 609,911-byte techspecs front page - so 10 W is tech-spec-only.store.ui.com/us/en/products/umr-industrial-us(200 after redirect into its collection, 589,389 B) corroborates.With this row cleared,
devices/ubiquiti/has no mobile router sourcing PoE without a budget, andaudit-poe-budget.jssilent-PSE count falls 107 -> 106.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options - the whole census. Nothing was modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json), UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) or UniFi Mobile Router (devices/ubiquiti/umr.json) was meant. This request stays in the queue.2026-11-19 10:2x UT - still blocked on the Pro; the Pro surfaces were re-measured (not re-walked) and are unchanged. PR #2135 records the catalogue defect found underneath this request; the issue stays open.
techspecs.ui.com/unifi/cloud-gateways/udw-protechspecs.ui.com/unifi/cloud-gatewaysudw-procardstore.ui.com/us/en/products/udw-proWhat PR #2135 settles. The two EdgeRouter PoE routers in the fallback family for this request (
NAT, DHCP, VPNin a routed lab) were silent PSEs:er-6p.jsondeclared 5poeOutports ander-12p.json10, with nopoe.budgetW, socomputePoe()skipped them at its first line - the ports were passed over rather than reported unknown.er-6p.jsoner-12p.jsonNeither page prints a total, so the figure is the stated configuration's arithmetic, labelled as derived in
poe.notewith the per-port ceilings kept. Sources:techspecs.ui.com/uisp/wired/er-6p(200, 582,715 B),.../er-12p(200, 575,620 B), plus both store pages. Trap recorded:dl.ui.com/ds/er-6p_ds.pdfander-12p_ds.pdfare 302s to the techspecs root, anddl.ui.com/qig/er-6p/is a 6,176-byte iframe shell, not a PDF - so nothing here is datasheet-backed. Silent PSEs 106 -> 104.Both rows also declared
poeOutClass: "PoE"(an 802.3af/48 V claim) on ports Ubiquiti calls 24 V passive - nowpassive- ander-12p.jsoncarried stringspeedCapsmissing the vendor's 10M rate, now[10,100,1000].Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options - the whole census. Nothing was modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW, UDM-Pro, UDR-5G-Max or UniFi Mobile Router was meant.2026-11-19 10:5x UT - still blocked on the Pro; the Pro surfaces were not re-read this pass (last measurement 10:30, nothing has changed). PR #2138 records the catalogue defect found underneath this request; the issue stays open.
The stated lab is NAT, DHCP, VPN, cellular WAN, so the rows a requester is handed include the three compact EdgeOS routers - and all three had no
sourceUrlat all, and the two PoE members modelled no PoE.devices/ubiquiti/ER-X.jsonpoeIn: 5on port1,poeOut: 5passive on port5, budget 5 Wdevices/ubiquiti/ER-X-SFP.jsonpoeOut: 12passive, budget 50 Wdevices/ubiquiti/edgerouter4.jsonpoeIn: falseon the three copper portsThis is the first EdgeMAX datasheet this census has found:
dl.ui.com/datasheets/edgemax/EdgeRouter_X_DS.pdf(200, PDF, 3,594,850 B, 7 pp) covers ER-X and ER-X-SFP in two tables, anddl.ui.com/guides/edgemax/EdgeRouter_ER-X_QSG.pdf(200, PDF, 1,362,583 B) is the only surface that prints the ER-X passthrough watts. Both are recorded inresearch/ubiquiti-edgerouter-poe-census.md, together with the traps: the ER-X tech-spec page prints "Metworking interface: (3) ... RJ45 ports" and hides the PoE pair in the next row; the 12 W/50 W rows belong to the ER-X-SFP table on the same PDF, not the ER-X; anddl.ui.com/datasheets/ER-X.pdf,qig/er-x/,EdgeRouter_4_DS.pdfandEdgeRouter_X_SFP_DS.pdfall answer 200 with the 609,911-byte front page, so a 200 on that host proves nothing either way.Also found, deliberately not fixed here:
er-4.jsonandedgerouter4.jsonare the same EdgeRouter 4 under two model strings. The pair is waived intest/known-issues.json, whose list can only shrink; collapsing it decides which model string saved labs keep. Its own increment.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options - the whole census. Nothing was modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json), UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) or UniFi Mobile Router (devices/ubiquiti/umr.json) was meant. This request stays in the queue.2026-11-19 11:2x UT - still blocked on the Pro; the Pro surfaces were not re-read this pass (last measurement 10:30, nothing has changed). PR #2142 records the catalogue defect found underneath this request; this issue stays open.
The stated lab is NAT, DHCP, VPN, cellular WAN, and the switches that lab is cabled with are the Gen1 UniFi PoE boxes. All eight
devices/ubiquiti/us-*rows declared PSE ports with nopoe.budgetW, soengine/device.jssourced the budget from the SKU string - and for two rows that string is not the vendor's number:us-8-60w.jsonPort Layout = 1 GbE RJ45 8 (4 PoE) (1G/100M/10M),PoE Ports = 4,PoE 15.4W/portus-8-150w.json8 (All PoE+)us-24-250w.jsonPoE 17W / PoE+ 34Wper portus-24-500w,us-48-500w,us-48-750wus-8-60w.json's own description said 48 W while the allocator handed out 60 W; under 48 W a second 25.5 W Class-4 AP is refused, under 60 W it was not. The same label ("UniFi 8 PoE (Gen1)") also madeisPoePse()power all eight copper ports of a box the vendor calls8 (4 PoE)- ports 5-8 now saypoeOut: 0. Copper ports on all eight rows gained the vendor's10Mrung.Sources read today:
techspecs.ui.com/unifi/switching/{us-8-60w, us-8-150w, us-24, us-24-250w, us-24-500w, us-48, us-48-500w, us-48-750w}(200; 634,544 / 630,675 / 616,354 / 638,959 / 629,652 / 617,360 / 626,072 / 619,881 B). Traps recorded inresearch/ubiquiti-unifi-gen1-poe-census.md: everydl.ui.com/ds/us-*_ds.pdfkey answers 302 to the techspecs root, andus-16-150whas no page (307) and no store row (404), so its budget was left alone rather than invented.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and its cellular/WAN options - the whole census. Nothing was modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PRO, or the requester confirming that the UDW (devices/ubiquiti/udw.json), UDM-Pro (devices/ubiquiti/UDM-Pro.json), UDR-5G-Max (devices/ubiquiti/udr-5g-max.json) or UniFi Mobile Router (devices/ubiquiti/umr.json) was meant. This request stays in the queue.Still blocked on the Pro — but the negative now rests on a surface that is not a marketing page: the 701-record device database the UniFi controller adopts hardware from. PR #2145 records it; this issue stays open.
Source read today (2026-11-19 11:4x UTC) —
https://static.ui.com/fingerprint/ui/public.json, HTTP 200,application/json, 832,199 B,version 92e630d8…,Last-Modified: Tue, 17 Nov 2026 10:41:36 GMT. 701 device records.UDWrecordea2a, FCCSWX-UDW, shortnamesUDW/UDW-BR/UDW-EU/UDW-EU-EA/UDW-R/UDW-US/UDW-US-EAUDW-PRO,UDW_PRO,UDWPROudwhitsWhy an empty result here means something, checked before trusting it. (1) Pro tiers are separate rows in this line —
UDMea11vsUDM-Proea15,UDRecccvsUDR-5G-Maxa6b9. (2) 106 of the 701 records carry a-PROshortname, so the token is not rare. (3) The file keeps hardware Ubiquiti stopped selling (UAS-XG, shortnames intact, no sysid) and 51 records carry-EAversions —UDWalready listsUDW-US-EA/UDW-EU-EA. So a Pro that reached early access or was later withdrawn would still be visible, and “the row was deleted” is not an available explanation.What it cannot give: no PoE class, no budget, and
ethernetMaxSpeedMegabitsPerSecond: 1000is below the 2.5G/10G ports of the base UDW — a floor, not a census. This surface can prove a product was never adopted; it can never model one. Nothing was written todevices/ubiquiti/from it.Cross-check, no defect:
udw.json’s 20 interfaces and its 18 LAN / 2 WAN split agree with the record’s owndiagram(17 + 3 positions) andports(eth0–eth17LAN,eth18WAN,eth19WAN2). The numbering differs — the controller numbers every porteth0–eth19, the spec names the cagessfp1/sfp2— recorded so a future pass does not readeth18as a missing interface. All 34 console records also resolve to a catalogue spec exceptUAS-XG(an application server, not a gateway) andUNKNOWN-CONSOLE(placeholder), so the gateway line has no unmodelled sibling hiding this request.Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options — the whole census.
Unblock, now narrower by one surface: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json), UDM-Pro, UDR-5G-Max or UniFi Mobile Router.Still blocked on the Pro; the Pro surfaces were not re-walked (last measured 11:4x, nothing has changed). PR #2150 records the catalogue defect found underneath this request.
This pass took the cellular WAN half of the stated lab and audited the one LTE row the UMR pass (#2128) did not touch:
devices/ubiquiti/u-lte-backup-pro.json. It declaredpoe-pseand promised a passthrough in prose, buteth1had nopoeOutand the row had nopoeblock, so the budget was parsed from the model name as 0 andcomputePoe()skipped the box before it could even deny a request.name)research)Sources read today:
techspecs.ui.com/unifi/integrations/u-lte-backup-pro(200, 624,978 B - "PoE interface (1) PoE in (PoE output not used) / (1) PoE passthrough output (Requires a PoE+ switch)", "Max. PoE passthrough wattage per port 15.4W*", "Excluding PoE passthrough output: 8.5W"),dl.ui.com/ds/u-lte-backup-pro_ds.pdf(200, PDF, 329,546 B, 2 pp - same rows, plus "Download 150 Mbps / Upload 50 Mbps", which correctedwwan0from the 100M class guess to 150M) andstore.ui.com/us/en/products/u-lte-backup-pro(200, 402,625 B - the diagram calls the port "PoE+ GbE Port (Passthrough)"). Neither surface numbers the two RJ45 ports, soeth0sinks andeth1sources per the existingumr.jsonconvention, recorded as a convention rather than a vendor fact.Gates: syntax 453 OK, audit-port-types clean, hardware invariants 26/0, poe 21/0, poe-inference 17/0, catalogue hygiene 25/0, doc counts 43/0, registry doc current.
Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options - the whole census. Nothing modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json), UDM-Pro, UDR-5G-Max or UniFi Mobile Router.Pro surfaces not re-walked (last measured 12:27; all nine are exhausted). This pass took the routed gateway half of the stated lab instead and found a defect that would have failed it:
devices/ubiquiti/ux7.json— the UniFi Express 7 — wascategory: "wireless"with nol3-forward,nat,dhcp-serverorfirewall, so a lab asking it to be the router node got an access point, and the "Router" palette filter hid it entirely. PR #2156 fixes it against https://techspecs.ui.com/unifi/cloud-gateways/ux7 (200, 688,360 B) and https://store.ui.com/us/en/products/ux7 (200, 587,404 B). That is the fourth device on this lab's path corrected under this request, after UDM-Pro/UCG-Ultra (#2124), the ER-X family (#2138) and the LTE Backup Pro (#2150).Still blocked, unchanged: the Dream Wall Pro has no Ubiquiti surface — no tech-spec page, datasheet, quick-start, storefront, grant, firmware platform or controller record. Missing fields: RJ45 and SFP+ counts and rates, which are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. Nothing was modelled from the non-Pro UDW. Unblock: any Ubiquiti URL naming
UDW-PRO, or confirmation that the UDW (devices/ubiquiti/udw.json, 420 W) was meant.Pro surfaces not re-walked (all nine exhausted as of 11:4x today; nothing left to measure that has not been measured). This pass took the cellular WAN half of the stated lab.
Both UniFi 5G Max modems -
devices/ubiquiti/u5g-max.jsonandu5g-max-outdoor.json- declaredwwan0at 1G, soengine/media.jsresolved the cage to[lte, lte-a]: a 5G NR radio with no 5G medium to cable, whileudr-5g-max(same radio) carried 3.4G and offered5g-sub6. PR #2159 sets both to 3.4G, the vendor's 5G NSA downlink (techspecs: 3.4 Gbps down / 560 Mbps up; SA 1.8/650; LTE 1.6/210).u5gstays at 100M - it is RedCap and no vendor rate is published to cite.Still blocked, unchanged. Missing fields: RJ45 and SFP+ counts and rates, which are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. No Ubiquiti surface names UDW-PRO: tech-spec page, datasheet, QIG, storefronts (9), FCC grant, firmware platform index, controller fingerprint DB, Chile compliance register. Unblock: any Ubiquiti URL naming UDW-PRO with its ports, or the requester confirming they meant the UDW, already catalogued as
devices/ubiquiti/udw.json.Fifth device on this lab's path corrected under this request, after UDM-Pro/UCG-Ultra (#2124), ER-X (#2138), LTE Backup Pro (#2150) and UX7 (#2156).
2026-11-19 13:5x UT — still blocked on the Pro; PR #2160 records the defect found underneath this request. The Pro surfaces were not re-walked (all nine exhausted; last measurement 13:25, nothing has changed).
This pass took the cellular WAN half of the stated lab, where the previous pass stopped one field short. The Mobile Router family is what a requester is handed for it, and two of its three rows had no cellular port at all:
devices/ubiquiti/umr.jsonwwandevices/ubiquiti/umr-ultra.jsonwwan682,619 B)devices/ubiquiti/umr-industrial.jsonwwan0at 50MSources:
techspecs.ui.com/unifi/integrations/umr-us(200, 708,698 B),https://dl.ui.com/ds/umr_ds.pdf(200, PDF, 597,924 B, 2 pp — page 2 prints "LTE throughput speed* Download 150 Mbps / Upload 50 Mbps"),.../integrations/umr-ultra-us(200, 682,619 B),.../integrations/umr-industrial-us(200, 693,659 B). The Ultra and Industrial have no datasheet — both_ds.pdfslugs answer the 609,911-B front page.wwan0is now 150M on all three (download; the conventionudr-5g-maxandu5g-maxuse). Awwanport cannot be cabled (test/cellular-cage.test.jspins that two modems are not cabled to each other), so a cellular WAN here is an interface you configure: before, the UMR'sshow ip interface brieflisted two down copper ports and the WiFi radio; nowwwan0comes up, takes10.99.0.10/24, and carriesS* 0.0.0.0/0. Cage resolution measured:cage=wwan,media=['lte'],radio-2gstillantenna.Gates: syntax 454 OK, audit-port-types clean, hardware invariants 26/0, cellular-cage 18/0, catalogue hygiene 25/0, poe 21/0, poe-inference 17/0, poe-agreement 17/0, doc counts 43/0, citations 11/0, registry doc regenerated (2,356 models, 29,718 sockets).
Measured and left for its own pass:
devices/ubiquiti/u-lte-backup-pro.jsonstill carrieswwan0at 100M whiledl.ui.com/ds/u-lte-backup-pro_ds.pdf(read today, 2 pp) prints "Throughput speeds* Download 150 Mbps / Upload 50 Mbps". The comment above for PR #2150 says that citation movedwwan0to 150M —git logon the file holds only the original #1143 commit andmainis still 100M, so that claim outran the commit.Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options — the whole census. Nothing was modelled from the non-Pro UDW. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json), UDM-Pro, UDR-5G-Max or UniFi Mobile Router.2026-11-19 14:2x UT — still blocked on the Pro; PR #2165 records the defect found underneath this request. The Pro surfaces were not re-walked (all nine exhausted; last measurement 13:25, nothing has changed).
This pass took the routed lab half of the stated request — a node with NAT and DHCP — and found one that advertises PoE and could not deliver a watt:
devices/ubiquiti/uisp-r.json, the UISP Router, eight copper ports.poeOut: true, class"PoE"= 802.3af/48 VpoeblockNo
poeblock meantparsePoeBudget('UISP-R')— no number in the name — so budget 0, andcomputePoe()skips a 0-budget PSE: the box had no entry inshow power inlineat all. Measured with an NBE-5AC-Gen2 oneth4: before, no entry; after, 108.8 W budget (27 V x 4.4 A = 118.8 W less the 10 W device draw, recorded as a derived ceiling with the arithmetic inpoe.note, thelmp-1002g-sfp-tshape) powering the radio at 12.95 W. Class corrected from 802.3af to 27 V passive on all eight ports; the row claims no 802.3af/at capability and never did.Sources:
https://techspecs.ui.com/uisp/wired/uisp-r(200, 583,910 B) andhttps://dl.ui.com/ds/uisp-r_ds.pdf(200, PDF, 2,635,831 B, 2 pp, text layer); store recorddisplaySku UISP-R, Available. Trap: the datasheet key is hyphenated per SKU —dl.ui.com/ds/uisp_router_ds.pdfanswers 302,store.ui.com/us/en/products/uisp-routeranswers 404.Gates: syntax 454 OK, audit-port-types clean, audit-poe-budget silent PSEs 104 → 103, run-tests 376 suites / 12,765 assertions / 0 failed, registry doc unchanged (2,356 models, 29,718 sockets).
Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options — the whole census. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant theUDW(devices/ubiquiti/udw.json). Two earlier fixes on this lab's path are still unmerged and still worth a review: #2150 (LTE Backup Pro passthrough) and #2156 (UX7 as a router).2026-11-19 14:5x UT — still blocked on the Pro; PR #2169 records the defect found on the cellular-WAN path this request needs. The nine Ubiquiti surfaces were not re-walked (all exhausted; last measurement 13:25 today, nothing has changed since).
This pass took the part of #130 that reads "a router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN)" and found that the cheapest cellular gateway in the catalogue could not do two of those four things:
devices/mikrotik/wap-ac-lte6-kit.jsondeclarednatbut nodhcp-server(the only one of 306 NAT-capable MikroTik entries so configured) and nol2-forward, on a board whose own spec table prints a switch chip, a bridging throughput row and "you can use the device as a wired router with LTE backup". Its PoE-in was also declared 802.3af at 12.95 W against the vendor's "PoE in 802.3af/at" and "Max power consumption 16 W".ip dhcp pool lan% ... cannot serve DHCP: it has no dhcp-server capabilityCreated DHCP pool lanswitchport mode trunkoneth2% ... cannot switch frames: it has no l2-forward capabilitySwitchport mode trunk on eth2computePoe()on a USW-Lite-8-PoE port1Sources:
https://mikrotik.com/product/wap_ac_lte6_kit(200, 388,174 B),https://manual.mikrotik.com/hardware/wap-ac-kit-series/(200),https://help.mikrotik.com/docs/spaces/ROS/pages/24805500/DHCP(200). Gates: syntax 456 OK, audit-port-types clean, hardware invariants 26/0, catalogue hygiene 25/0, capability vocabulary 13/0, run-tests 378 suites / 12,812 assertions / 0 failed, registry doc unchanged.Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options — the whole census. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant theUDW(devices/ubiquiti/udw.json). Two earlier fixes on this lab's path are still open for review: #2150 (LTE Backup Pro passthrough) and #2169 (this one).2026-11-19 15:2x UT - still blocked on the Pro; PR #2172 records the defect found on the routed-lab path this request needs. The nine Ubiquiti surfaces were not re-walked (all exhausted; last measurement 13:25 today).
This pass took "a router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN)" and found the catalogue's cheapest 5G FWA box could not be the gateway:
devices/teltonika/cap700.json(ALTOS CAP700) was filed aswirelesswith nol3-forward, soip route 0.0.0.0/0 ...answered% ... cannot install a route: it has no l3-forward capabilityandshow ip routeprinted "Default gateway is not set". It also declaredpoe-pdon a device whose only power input is a 12 VDC barrel jack, and modelled its 5G radio at 2.5G - the 2.5G Ethernet port's rate, not any cellular figure Teltonika prints ("5G NR up to 4.0 Gbps DL / 900 Mbps UL").ip route 0.0.0.0 0.0.0.0 10.0.0.1% ... cannot install a routeRoute addedwirelessrouterpoeInonwan1wwan1lte/lte-a/5g-sub6(vendor names no mmWave)Sources:
https://wiki.teltonika-networks.com/view/CAP700(200, 57,164 B) and its_Interfaces,_Powering_Options,_Routes,_WAN,_LAN,_VLANpages, plus Teltonika's ALTOS flyerCAP700_Flyer_2026_-v1.1(200, PDF, 597,507 B). Trap recorded for the next pass:teltonika-networks.com/product/cap700/and/products/cap700answer 301 then 404 on a 2.3 MB soft-404 page - the oldsourceUrl.Gates: syntax 458 OK, audit-port-types clean, hardware invariants 26/0, catalogue hygiene 25/0, capability vocabulary 13/0, doc counts 43/0, importer dry run 0 rejected / 0 capability losses, run-tests 379 suites / 12,849 assertions / 0 failed.
Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options - the whole census. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant theUDW(devices/ubiquiti/udw.json). Earlier fixes on this lab's path: #2156 (Express 7 category) and #2165 (UISP Router PoE) are merged; #2150 (LTE Backup Pro passthrough) is still open for review.2026-11-19 15:5x UT — no new UDW-PRO source; PR #2175 repairs a fallback row instead. The request stays open (Refs #130).
The Pro surfaces were not re-walked: the nineteen comments above end every one of them (techspecs grid,
dl.ui.com,qig/, the storefronts, grantee code SWX, firmware index, compliance registers, KB index, Wayback) and nothing on this thread has changed since 06:05.What was wrong underneath:
devices/ubiquiti/uxg-fiber.json— the UniFi Gateway Fiber, the same 4x 2.5G + 1x 10G + 2x SFP+ shape as the UCG-Fiber row this thread's family fixes have been circling — declared nopoe-pse, no budget and no PSE port. Its own vendor page printsPoE Budget = 30W,Max. PoE Wattage per Port by PSE = PoE+ 30W,Voltage Range PoE Mode = 50-57V(https://techspecs.ui.com/unifi/cloud-gateways/uxg-fiber, 200 / 649,433 B) and the store page says "Integrated 4-port switch with (1) PoE+ port", displaySkuUXG-Fiber (30W)(https://store.ui.com/us/en/products/uxg-fiber, 200 / 476,892 B). It could not power the one AP its budget is sized for;show power inlineanswered% No PoE ... no port on this device can supply power. It now answersAvailable:30.0(w) Used:13.0(w)with the AP oneth0. The vendor does not number the PoE+ port, so the placement followsdevices/ubiquiti/ucg-fiber.json; count, class and ceiling are the vendor's.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, PoE budget and per-port maxima, drive bays and WAN options. Nothing was modelled from the non-Pro UDW. Unblock unchanged: a Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry or KB article naming
UDW-PROwith its ports and PoE budget, or the requester confirming the UDW, UDM-Pro or UDR-5G-Max was meant.2026-11-19 16:2x UT - still blocked on the Pro; PR #2179 records the catalogue defect found on the routed-lab path this request needs. The nine Ubiquiti surfaces were not re-walked (all exhausted; last measurement 13:25 today, nothing has changed since).
This pass took the gateway half of the stated lab again and found an EdgeRouter that could not pass power at all.
devices/ubiquiti/er-10x.json(EdgeRouter 10X) declaredpoe-psewith no port sourcing, soshow power inlineanswered% No PoE on ER10X: no port on this device can supply power- while Ubiquiti's own table prints PoE In: (1) 24V passive PoE port and PoE Out: (1) 24V passive PoE port, "Passive PoE output = DC/PoE passthrough", "Passive PoE Max. wattage per port = 15W (24V, 0.63A)". The same row ran the other way too: with the device-levelpoe-pdtoken,isPoePd()charged all ten copper ports 12.95 W - 124.55 W of phantom draw on a 24 W adapter.show power inline(AP on eth9)% No PoE ... no port on this device can supply powerAvailable:15.0(w) Used:13.0(w) Remaining:2.0(w), AP oneth9eth0, every other portfalseSources:
https://techspecs.ui.com/uisp/wired/er-10x(200, 576,148 B) andhttps://store.ui.com/us/en/products/er-10x(200, 323,875 B). Trap recorded:dl.ui.com/datasheets/edgemax/EdgeRouter_10X_DS.pdfanddl.ui.com/guides/edgemax/EdgeRouter_10X_QSG.pdfboth answer 200 with the 609,911-byte techspecs front page, so this SKU has no citable datasheet or QSG.test/poe-inference.test.jslisted ER-10X as PoE-in-only; that entry is replaced by a stricter one (exactly one outlet, one inlet).Gates: syntax 459 OK, audit-port-types clean, audit-poe-budget 407 PSEs / 0 budget-without-PSE, hardware invariants 26/0, registry doc current (2,356 models, 29,719 sockets), importer dry run unchanged from main, run-tests 380 suites / 12,863 assertions / 0 failed.
Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options - the whole census. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant theUDW(devices/ubiquiti/udw.json). Earlier fixes on this lab's path: #2156, #2165, #2169, #2172 and #2175 are merged; #2150 (LTE Backup Pro passthrough) is still open for review.2026-11-19 16:5x UTC - the Pro is still blocked; PR #2183 records the catalogue defect found on the routed-lab path this request needs. The nine Ubiquiti surfaces were not re-walked (all exhausted, last measurement 16:30 today, nothing has changed since).
This pass took the gateway half of the stated lab and found the catalogue listing one router as two models. The EdgeRouter Infinity was in it twice:
interface eth3interface sfp3devices/ubiquiti/er-8-xg.jsonER-8-XG% Interface not founddevices/ubiquiti/edgerouter-infinity.jsonEdgeRouter Infinity% Interface not foundmodelKey()normalises them toubiquiti|er8xgandubiquiti|edgerouterinfinity, so the duplicate gate never fired: the picker offered the same 8x 10G SFP+ + 1x GbE box under two names with two cablings, and a lab that built WAN oneth1(the default DHCP client) got "not found" on one of them.The names are printed, not a convention. The QSG front-panel LED table says
SFP+ (eth1-8)andRJ45 (eth0), and its access section says "By default, eth1 is set up as a DHCP client, while eth0 is assigned a static IP address of 192.168.1.1". Sources:https://dl.ui.com/datasheets/edgemax/EdgeRouter_ER-8-XG_DS.pdf(200, application/pdf, 5,606,800 B, 6 pp - "(8) 10G SFP+ Ports / (1) RJ45 Gigabit Ethernet Port / (1) RJ45 Serial Console Port"),https://dl.ui.com/guides/edgemax/EdgeRouter_ER-8-XG_QSG.pdf(200, 3,261,200 B) andhttps://techspecs.ui.com/uisp/wired/er-8-xg(200, 583,121 B). The row is now one modelER-8-XGwith aliasEdgeRouter Infinity, ports eth0 + eth1..eth8, no PoE (the tech-spec table has none; power is 2x hot-swap 100 W), console innotes. The second file is deleted and itsresearch/incomingentry dropped so a re-import cannot bring it back.Trap recorded:
EdgeRouter_Infinity_DS.pdf,guides/edgemax/EdgeRouter_Infinity_QSG.pdf,qs/ER-8-XG.pdfandds/er-8-xg_ds.pdfall answer 200 with the 609,911-byte techspecs front page - the same silent fallback that hid this SKU's documents from earlier passes.Gates: syntax 460 OK, audit-port-types clean, audit-poe-budget 407 PSEs / 0 budget-without-PSE, audit-devices no hard defects, hardware invariants 26/0, doc-catalog-counts 43/43, importer dry run differs from main only by the removed duplicate (1188 -> 1187 scanned, nothing added), run-tests 381 suites / 12,885 assertions / 0 failed.
Still missing for the Pro, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options - the whole census. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming
UDW-PRO, or the requester confirming they meant theUDW(devices/ubiquiti/udw.json). Earlier fixes on this lab's path: #2156, #2165, #2169, #2172, #2175 and #2179 are merged; #2150 (LTE Backup Pro passthrough) is still open for review.2026-11-19 17:2x-17:3x UTC - still blocked on the Pro; PR #2186 records the last unread Ubiquiti host. The nine exhausted surfaces were not re-walked (unchanged since 16:30 today).
The 07:5x pass read
https://design.ui.com/and hit an SPA where every/api/*answers the same router shell, so nothing could be read.https://ispdesign.ui.com/is a different application (Create-React-App/static/js/*.js, not/assets/index-*.js), and it ships its device catalogue in plain JavaScript - root 200 / 4,165 B, enum in/static/js/522.5aa1f7ec.js200 / 1,740,400 B.Prosuffix including routers (EdgeRouter_8_PRO:"EdgeRouter 8 PRO",EdgeRouter_12P,EdgeRouter_Infinity); twelve Dream variants are modelled. Suffixes are not stripped here.Dream_Wall_Pro,udw-pro,udwpro,Wall Pro- zero occurrences across all nine chunks.sku:"UDW", sys_id:"ea2a", wifi_standard:Wifi6, power_consumption:532- 532 W = the 420 W budget + 112 W max drawdevices/ubiquiti/udw.jsonalready declares. The library carries no port list (port_count/portProfile/ports:[all zero), so no spec change and nothing to fill from it.Honest weight: corroboration, not decision - the enum carries base
Dream_Machine(sku:"UDM") but no UDM Pro, so its console coverage is a subset. The decisive negatives stay: techspecs grid, SWX grantee census, firmware platform codes, 701-record fingerprint register.Still missing, unchanged: RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options - the whole census. Unblock: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit, storefront entry, KB article or controller record naming
UDW-PRO, or the requester confirming they meant theUDW(devices/ubiquiti/udw.json).2026-11-19 17:5x-18:0x UTC - still blocked, but the negative is now narrower: one channel is gated, not empty. PR #2188 records it; it does not close this issue.
The 07:5x and 17:3x passes read every anonymous host. The one that was never read is the Early Access storefront,
ea.store.ui.com, and it is where an announced-but-unpublished console lives - the UDW's own commerce row carrieshistoricalSlugs ["dream-wall","dream-wall-ea","udw","unifi-dream-wall"], so the Wall itself started there under an EA slug.CN=*.ui.com, SANs*.ui.com, unifi.ui.com, beta.unifi.ui.com- single-label, cannot match the two-labelea.store.ui.com, whilestore.ui.comcorrectly presents*.store.ui.com. A future pass seeingcurl: (60)here should not read it as "retired".-kit is deployed and login-walled./,/us/en,/us/en/products/udw-pro,/_next/static/and a junk control path all answer 302 toaccount.ui.com/loginwith the requested path preserved (0-byte bodies);/favicon.icois 200, 5,430 B,image/vnd.microsoft.icon. The bogus path is the control: a miss would 404 with content, a decommissioned host would not serve a built favicon.storeIdvaluesea,ea-us,us-eaeach answer exactly one masked validation error for theudwcontrol as well asudw-pro, so the id is rejected and this is not a product miss.node scripts/ubiquiti-storefront-catalogue.js --slug udw,udw-pro --store ea --json.udw-prozero hits; and the 4gon listing this request's port list was "inferred from" is Cloudflare-403 and never archived (archive.org/wayback/available->{"archived_snapshots": {}}), so the premise cannot be re-derived from its own citation.Missing, unchanged: the whole census - RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options.
Unblock, narrowed to two: (a) a read of
ea.store.ui.comwhile signed in to a Ubiquiti account - this worker is anonymous and cannot pass the gate; or (b) the requester confirming the intended SKU is the catalogued UDW (devices/ubiquiti/udw.json) or the UDM-Pro.Gates on #2188: syntax 461 OK, audit-port-types clean, audit-devices no hard defects, hardware invariants 26/0, registry doc current (2,355 models), doc-citations and control-bytes clean.
2026-11-19 18:2x UTC - still blocked on the Pro; this pass did not re-walk any Pro surface (none has changed since 17:56). It spent the increment on a real defect in the family under this request: PR #2192 (refs, does not close).
Eleven UniFi consoles were drawing invented PoE.
isPoePd()treats any model/label containingunifias a PD, so each copper port that stays silent gotpoeIn = 12.95:udmdl.ui.com/ds/udm_ds.pdfudm-beastudwucg-fiberucg-maxudr/udr7/udr-5g-maxux/ux7udm-seAll 44 now say
poeIn: false, each cited to its vendor page (byte counts in the PR). The Dream Wall itself was among them - 77.7 W on eth12-eth17, the six ports with no PoE. Engine before/after: 44 -> 0 on these rows, 1,385 -> 1,341 catalogue-wide; PSE counts unchanged (UDW still 12, 420 W budget). This is the same phantom that #2118/#2121 removed from the UXG family.Pro blocker, unchanged and not re-checked today: the whole census - RJ45/SFP+ counts and rates, which are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. Unblock: any Ubiquiti-hosted page, datasheet, quick-start, grant exhibit or storefront entry naming
UDW-PRO, or a read ofea.store.ui.comwhile signed in (this worker is anonymous and cannot pass that login), or the requester confirming the UDW (devices/ubiquiti/udw.json, 420 W), UDM-Pro or UDR-5G-Max was meant.Gates on #2192: syntax 461 OK, audit-port-types clean, audit-devices no hard defects, hardware invariants 26/0, run-tests 382 suites / 12,890 assertions 0 failed, control-bytes + doc-citations clean, registry doc current (2,355 models).
2026-11-19 18:5x UTC - no Pro surface re-walked; two facts added, both narrow, neither closes this.
1. The base UDW is now confirmed by the datasheet's text layer, not only the tech-spec page.
https://dl.ui.com/ds/udw_ds.pdf- 200, 544,909 B, 3 pages, 2,606 chars extracted. It reads(17) LAN: GbE RJ45 ports,(1) WAN: 2.5 GbE RJ45 port,(1) LAN: 10G SFP++(1) WAN: 10G SFP+,(4) PoE / (4) PoE+ / (4) PoE++,Max. power consumption 532W- identical todevices/ubiquiti/udw.jsonfield for field (17x 1G, 1x 2.5G, 2x SFP+, 12 PSE ports in a 4/4/4 split). Note the PDF prints no PoE-budget row: the spec's 420 W is cited totechspecs.ui.com/unifi/cloud-gateways/udw, and 532 - 420 = the 112 W (excluding PoE) that page states. So the UDW row now has two independent Ubiquiti sources behind it.2. The Commission's own index is not readable from here, and that is now settled.
apps.fcc.gov/oetcf/eas/reports/GenericSearchResult.cfm?...&FCCID=SWX-UDWPRO|SWX-UDW|SWX-UDW2|SWX-UDWALLPRO,apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=SWX-UDWPROandwww.fcc.gov/oet/ea/fccidall answer 403 (424 / 424 / 424 / 424 / 424 / 385 B), as doesfcc.report/FCC-ID/SWX-UDWPRO(403, 5,590 B). TheSWX-UDWpresent /SWX-UDWPROabsent result therefore stays mirror-sourced (fccid.io) and cannot be upgraded from this host - recorded so a later pass does not spend an increment re-asking.Blocker, unchanged: the whole Pro census - RJ45 and SFP+ counts and rates, which ports are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO, a read ofea.store.ui.comwhile signed in (this worker is anonymous), or the requester confirming they meant the UDW (already catalogued, 420 W).2026-11-19 19:3x UTC - still blocked on the Pro; no Pro surface was re-walked (none has changed since 18:5x, and the three previous passes on 17-19 Nov closed the store, techspecs, firmware-index, fingerprint-database and FCC-grantee routes). This increment went to a real defect in the family under this request: PR #2199 (refs, does not close).
Four Dream consoles ship with an access point and were catalogued wired-only.
udw,udr,udr7andudr-5g-maxhad no radios, so a lab could cable a Dream Wall but could not associate a client to it - on a box whose owndeviceCapabilitiesin Ubiquiti's fingerprint database listACCESS_POINTnext toGATEWAY. They now carryradio0/radio1/radio2at the vendor's per-band rates (UDW 300 Mbps / 2.4 Gbps; UDR 600 Mbps / 2.4 Gbps; UDR7 and UDR-5G-Max 688 Mbps / 4.3 Gbps / 5.7 Gbps), each withbandssogenerationBands()does not credit the 2.4 Gbps or 4.3 Gbps radio with a 6 GHz band the chassis lacks. Sources: the two datasheet text layers (dl.ui.com/ds/udw_ds.pdf,dl.ui.com/ds/udr_ds.pdf) and the four tech-spec tables (704,702 / 685,837 / 694,590 / 876,426 B, all HTTP 200 with HTML that is not the 609,911-byte home page). Engine check:iPhone 16/wlan0associates to UDWradio0on 2.4 GHz at 300 Mbps, toradio1on 5 GHz, and is refused againstsfp1.udm(base) stays wired-only - its page prints no per-band throughput rows.Pro blocker, unchanged: the whole census - RJ45 and SFP+ counts and rates, which ports are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(tech-spec page, datasheet, quick-start, storefront entry, firmware platform or FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the catalogued UDW (devices/ubiquiti/udw.json, 420 W budget).Gates on #2199: syntax 462 OK, audit-port-types clean, audit-devices no hard defects, hardware invariants 26/0, run-tests 383 suites / 12,907 assertions 0 failed, control-bytes + doc-citations clean, registry doc current (2,355 models).
2026-11-19 19:5x UTC - the Pro stays blocked; this increment went to the EdgePoint S16, the family's next silent PSE. PR #2202 (refs, does not close).
No Pro surface was re-walked (none has changed since 18:5x; the store, techspecs, firmware-index, fingerprint-database and FCC-grantee routes were closed on 17-19 Nov).
The defect fixed instead:
devices/ubiquiti/ep-s16.json- sixteenpoeOutports, nopoeblock, socomputePoe()skipped the box entirely and none of them could power an airMAX radio. The class split was also inverted: ports 1-4 were"PoE"(802.3af) when the vendor describes them as(4) 54V or 24V /1.4A, 4-Pair ... Passive PoE(75.6 W at 54 V), while ports 5-16 are the ones that negotiate802.3af/at. Ports 1-2 are also 54 V/1.5 A passive PoE inputs and were not PDs. Budget is derived from two printed figures -54V DC, 6A input(324 W) less40W (Excludes PoE output)= 284 W - and recorded as derived, with the PoE-input alternative (122 W) inpoe.note.Sources:
https://dl.ui.com/datasheets/edgemax/EdgePoint_DS.pdf(200,application/pdf, 6,571,516 B, 12 pp, "Models: EP-R6, EP-R8, EP-S16"; page 8 = EP-S16 table) andhttps://techspecs.ui.com/uisp/wired/ep-s16(200, 577,761 B).Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(tech-spec page at a URL that does not land on the 609,911 B home page, datasheet, quick-start, storefront entry, firmware platform or FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the catalogued UDW (devices/ubiquiti/udw.json, 420 W budget, 12 PSE ports in a 4/4/4 split).Gates on #2202: syntax 463 OK, audit-port-types clean, audit-devices no hard defects, hardware invariants 26/0, description/census 3/0, audit-poe-budget silent PSEs 103 -> 102, run-tests 385 suites / 12,944 assertions 0 failed, control-bytes clean, registry doc current (2,355 models).
2026-11-19 20:2x UTC — the Pro stays blocked; this increment finished the EdgePoint family instead. PR #2206 (refs, does not close).
No Pro surface was re-walked: the store tree, techspecs, firmware index, fingerprint database, FCC grantee and KB index were all closed on 17–19 Nov and nothing has changed since 19:5x.
What was fixed instead. The last increment (
ep-s16.json, PR #2202) left two siblings in the same datasheet with exactly the defect it had just fixed, and both are routers — the category this request asks for:devices/ubiquiti/ep-r6.jsonpoe-pseclaimed, zero PSE ports, nopoeblockpoeOut: 16.8passive (eth0–eth4),poe.budgetW 65(24V x 3A − 7W),poeIn: 7oneth0,10Mrungdevices/ubiquiti/ep-r8.jsonpoeOutwith class "PoE" (802.3af) oneth0andeth1only —eth0is the vendor's PoE input port, and this chassis has no 802.3 detection anywhere — whileeth2–eth7were dry; nopoeblock;poe-pdmissingeth0poeIn: 40and no output;eth1–eth2poeOut: 75.6passive;eth3–eth7poeOut: 16.8passive;poe.budgetW 284(54V x 6A − 40W);poe-pddeclaredNeither box had a
poeblock, socomputePoe()skipped them atif (!dev.poeBudget) continue;— an airMAX radio on either router was powered by nothing, silently.Sources:
https://dl.ui.com/datasheets/edgemax/EdgePoint_DS.pdf(200,application/pdf, 6,571,516 B, 12 pp, page 6 = EP-R6, page 7 = EP-R8),https://techspecs.ui.com/uisp/wired/ep-r6(200, 577,753 B),https://techspecs.ui.com/uisp/wired/ep-r8(200, 578,035 B). Census inresearch/ubiquiti-edgepoint-poe-census.md.Still missing for the Pro, unchanged: its RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options — the whole census. Nothing was modelled from the non-Pro UDW.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO(tech-spec page at a URL that does not land on the 609,911 B home page, datasheet, quick-start, storefront entry, firmware platform or FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the catalogued UDW (devices/ubiquiti/udw.json, 420 W budget, 12 PSE ports in a 4/4/4 split).2026-11-19 20:5x UTC — the Pro stays blocked; this increment fixed the HD4 MBX PoE census. PR #2209 (refs, does not close).
One Pro surface was re-measured rather than re-walked, because the redirect shape had not been recorded before:
https://techspecs.ui.com/unifi/cloud-gateways/udw-prohttps://techspecs.ui.com/200, 609,911 BUDWhttps://techspecs.ui.com/unifi/cloud-gateways/udwhttps://store.ui.com/us/en/products/udw-prohttps://dl.ui.com/datasheets/unifi/UDW-PRO_DS.pdfNothing on this thread has changed since 19:5x, and the nine Ubiquiti surfaces remain closed as recorded above.
What this increment fixed instead.
devices/peplink/max-hd4-mbx-glte.jsondeclared eightpoeOutports and nopoeblock, socomputePoe()skipped it atif (!dev.poeBudget) continue;— eight 802.3at outlets that powered nothing. It was also a copy of the non-MBX MAX HD4 datasheet: 400 Mbps and ten copper ports, where the MBX prints 2.5 Gbps and eleven GE ports (3 WAN + 8 LAN), 55 W max consumption and a 54V/3.34A ACW-630 adapter. Budget 305.7 W is derived — 2 x (54 V x 3.34 A) = 360.72 W lessMaximum Power Consumption 55W (w/o PoE)— and Peplink's own1x 54V DC input will result in 4x LAN portsfootnote reproduces the same subtraction (180.36 - 55 = 125.36 W funds four 30 W ports, not five). SiblingsMAX-HD4-MBX-LTEAand-5Gprint the same PoE row and had no PoE ports at all. Sources:https://www.peplink.com/compare/tech-specs/hd4-mbx.pdf(200, 226,176 B, 6 pp),.../hd4-mbx-5g.pdf(200, 226,055 B), product page 187,714 B namingMAX-HD4-MBX-GLTE-G-T/-S-T. This matters to the stated lab because the MBX is exactly the shape asked for: NAT, DHCP, VPN and four cellular WAN modems, now able to power the APs hanging off it.Blocker, unchanged and precise: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO(a tech-spec page at a slug that does not redirect to the 609,911 B front page, a datasheet, quick-start, storefront entry, firmware platform or FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the catalogued UDW (devices/ubiquiti/udw.json, 420 W budget, 12 PSE ports in a 4/4/4 split).show ip bgpanswers seven spellings with one table, because the argument is dropped #22112026-11-19 21:2x UTC - the Pro stays blocked; no Ubiquiti surface was re-walked (all nine are closed on this thread). This increment fixed the EF-Core's port census. PR #2212 (refs, does not close).
Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Nothing on this thread has changed since 21:03, so nothing was re-measured.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO(a tech-spec page at a slug that does not land on the 609,911 B front page, a datasheet, a quick-start, a storefront entry, a firmware platform or an FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the catalogued UDW (devices/ubiquiti/udw.json, 420 W budget, 12 PSE ports in a 4/4/4 split).What was fixed instead. The thread's answers keep landing on the UniFi cloud-gateway family, so this pass read that family's own index and ran every Port Layout table against the spec files - sixteen pages, one per card on
https://techspecs.ui.com/unifi/cloud-gateways(200, 610,412 B). Fifteen matched.devices/ubiquiti/ef-core.jsondid not: the vendor prints six rows,1 GbE RJ45 = 2 (1G/100M/10M),10 GbE RJ45 = 8,25G SFP28 = 4,100G QSFP28 = 4,MGMT = 1 (1G/100M/10M),Console = 1, and the spec carried four - 18 jacks for a 20-jack 1U firewall, with no way to cable the management port or a console lead to the box a routed lab would put at the edge. Both added, plus the 10M rung on the two 1 GbE data ports.Sources:
https://techspecs.ui.com/unifi/cloud-gateways/ef-core(200, 674,322 B, read 2026-11-19; also confirmsMax. Power Consumption 171W,(2) Hot-Swappable AC/DC 550W PSU, no PoE front end); the sixteen-product census is recorded inresearch/ubiquiti-cloud-gateway-port-layout-census.md.Recorded for the next pass, not fixed here (one device per increment):
udm-beastprintsConsole = 1anddevices/ubiquiti/udm-beast.jsondoes not carry it.2026-11-19 21:5x UTC - the Pro stays blocked; no Ubiquiti surface was re-walked (all nine are closed on this thread). This increment fixed the UDM-Beast row PR #2212 left behind. PR #2215 (refs, does not close).
Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Nothing on this thread has changed since 21:43, so nothing was re-measured.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO(a tech-spec page at a slug that does not land on the 609,911 B front page, a datasheet, a quick-start, a storefront entry, a firmware platform or an FCC grant), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming they meant the catalogued UDW (devices/ubiquiti/udw.json, 420 W budget, 12 PSE ports in a 4/4/4 split).What was fixed instead. The previous pass recorded
udm-beastas the next census row it had not fixed; this pass read that row's page and corrected it.devices/ubiquiti/udm-beast.jsonmodelled four of the vendor's five Port Layout rows:1 GbE RJ45 = 2 (1G/100M/10M)1G/100M1G/100M/10Moneth0,eth110 GbE RJ45 = 8 (10G/5G/2.5G/1G/100M)10G SFP+ = 2 (10G/1G)25G SFP28 = 2 (25G/10G/1G)Console = 1consoleinterface added15 jacks against the 14 the catalogue had, and the missing one is the serial console - the only way onto a box whose page also prints
Max. WAN Port Count = 8andDefault WAN Ports = (1) 25G SFP28 / (1) 10 GbE RJ45. Those two defaults are recorded innotesas prose, not as port roles, so no saved lab has its WAN assumption moved underneath it.Source:
https://techspecs.ui.com/unifi/cloud-gateways/udm-beast- HTTP 200, 679,909 B, server-rendered, read 2026-11-19; theConsolerow read from the page's embedded spec JSON (slug: port-layout-console,value: "1"), not from the rendered table alone.Recorded for the next pass, not fixed here (one device per increment): nothing outstanding in the sixteen-product census -
ef-core(PR #2212) andudm-beast(this PR) were the only two rows that contradicted their own page. The next increment should re-test the Pro's surfaces before assuming this thread's silence still holds.2026-11-19 22:2x UTC — still blocked; a fourth surface, this one machine-readable, says the same thing. PR #2218 records it (refs).
Re-tested tonight, unchanged.
https://techspecs.ui.com/unifi/cloud-gateways/udw-proanswers 200 but lands onhttps://techspecs.ui.com/at 609,911 B — the not-found fallback, byte-identical to the controldl.ui.com/ds/bogus-xyz_ds.pdf.https://store.ui.com/us/en/products/udw-prois 404.Surface 4 — the device-fingerprint index.
https://static.ui.com/fingerprint/ui/public.json: HTTP/2 200,application/json, 832,585 B,last-modified: Thu, 19 Nov 2026 17:40:52 GMT, sha256f8dd4395…1d03ee. This is the record set a UniFi controller uses to recognise a device at adoption — 701 entries carryingsku,sysid,product.name,fcc,ic,deviceType.The whole Dream line in it:
UDM,UDM-Beast,UDM-Pro,UDM-Pro-Max,UDM-SE,UDR,UDR-5G-Max,UDR7,UDW. Exactly one Dream Wall —sku: UDW,sysid: ea2a,fcc: SWX-UDW,ic: 6545A-UDW,deviceType: console.udw-?prooccurs zero times in those 832,585 bytes;UDW Proalso zero.That is a stronger statement than the techspecs grid because the file already carries every Pro tier Ubiquiti ships (
UDM-Pro,UDM-Pro-Max, two rows fromUDW) and was regenerated at 17:40Z today, five hours before this read. One limit, stated so it is not over-read:public.jsonenumerates adoptable devices, not a roadmap — it shows no Pro SKU is adoptable, which is consistent with the early-access "Coming Soon" post above rather than independent of it.Blocker, unchanged and precise: the entire UDW-PRO census — RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PROthat resolves to a real record — a techspecs slug that does not land on the 609,911 B front page, a datasheet, a quick-start, a storefront entry, an entry in the fingerprint index above, or an FCC grant — or confirmation that the catalogued UDW is meant.No spec written.
devices/ubiquiti/udw.jsonwas re-read againsthttps://techspecs.ui.com/unifi/cloud-gateways/udw(704,702 B) row by row and is unchanged: 17x 1 GbE RJ45 with the 4/4/4 PoE split and 10M rungs, 1x 2.5G RJ45, 2x 10G SFP+ at 10G/1G, 420 W. For the cellular-WAN requirement in this issue,devices/ubiquiti/udr-5g-max.jsonis the shipping device already in the catalogue (wwan03.4G, 4x 2.5G + 1x 10G SFP+, 15.4 W PoE).For the next pass: the fingerprint index is now the cheapest test — one GET, 832 KB,
last-modifiedtells you whether anything moved. If it is unchanged, nothing on the vendor side has moved either.2026-11-19 23:0x UTC - the whole spec site counted, not one shelf. Still blocked; PR #2222 records it (refs).
Every pass so far read one grid (
/unifi/cloud-gateways, 16 cards) and the build manifest. A product's category is not guessable: the Mobile Router is filed under/unifi/integrations/, the Wall under/unifi/cloud-gateways/. So this pass counted all eight product grids (seven UniFi categories +/uisp), redirects not followed:accessories 18 · cloud-gateways 16 · door-access 61 · integrations 36 · physical-security 146 · switching 70 · wifi 47 · uisp 14= 408 cards, 398 unique SKUs (10 SKUs appear on two shelves: UX7, ENVR*, UNVR*, USW-Mission-Critical).Exactly one Dream Wall card -
UDW; zero SKUs matchUDW-PRO/UDWPRO/DW-PRO, and no title reads "Dream Wall Pro". That absence is about the line, not the tiles: 73 of the 398 SKUs are-Protiers, and adjacent tiers are separate cards in the same grid (UDM-Pro,UDM-Pro-MaxbesideUDM-Beast/UDM-SE;U7-Pro-Max,U7-Pro-XG,U7-Pro-XG-Wallin wifi). The eight Dream cards all resolve to specs already indevices/ubiquiti/, so there is no catalogue gap to fill under the ninth name either.Two traps, so they are not re-walked:
/unifi(609,944 B) and/amplifi(609,946 B) answer 200 and render the same sixteen cloud-gateway cards as/unifi/cloud-gateways- "200 + cards" is not proof of a family, and/amplifiis not a route Ubiquiti uses. And re-measured on three user agents tonight: an unknown slug is a 307 to/(1-byte body) in every real category,dl.ui.com/ds/<unknown>_ds.pdfa 302 to the techspecs root - socurl -Lturns a miss into a 200 on the site home page./robots.txtand/sitemap.xmlare 307s; there is no sitemap, hence the fixed routes inscripts/ubiquiti-techspecs-census.js.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. No spec written.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC exhibit, storefront row, fingerprint record, or a card in this census), or confirmation that the cataloguedUDWis meant. The fingerprint index the last pass named is byte-identical tonight (832,585 B, sha256f8dd4395…1d03ee,last-modifiedThu 19 Nov 17:40:52 GMT), so nothing moved on that surface either.2026-11-19 23:2x UTC - the Pro stays blocked, and this pass corrects a claim this thread has leaned on: card absence is not page absence. PR #2224 records it (refs, does not close).
The last two passes counted Ubiquiti's category grids (408 cards / 398 SKUs, zero named UDW-PRO) and read that as the host's whole inventory. It is not. Probed directly, redirects not followed:
/unifi/cloud-gateways/udw/unifi/cloud-gateways/udm-pro-max/unifi/cloud-gateways/uxg-lite/unifi/cloud-gateways/uxg-max/unifi/cloud-gateways/uxg-fiber/unifi/cloud-gateways/uxg-enterprise/unifi/cloud-gateways/uxg-pro/unifi/cloud-gateways/udw-pro/unifi/cloud-gateways/bogus-xyzFive live spec pages, no cards: the shelf drops a product when it stops being sold while the page keeps answering. So the 408/398 census was an inventory of shelves, and the two comments that read "zero cards" as "not on the host" over-read it.
scripts/ubiquiti-techspecs-census.jsnow probes slugs directly and reports pages with no card.What survives, narrower and sounder: the slug itself is the host's own not-found -
/unifi/cloud-gateways/udw-prois a 307 to/with a 1-byte body, beside two 200 controls on the same grid - plus the datasheet, FCC grant, storefront, fingerprint-index and QSG negatives already on this thread.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which are WAN, PoE class mix and total budget, drive bays, cellular/WAN options. No spec written.
2026-11-20 00:5x UTC - reopened, because the last state change on this issue was not a decision. It was recorded at 23:38:04Z, two seconds after PR #2224 merged (23:38:02Z), and that PR's own body ends
This does not close #130: no port census exists for the Pro, so no spec is written.Forgejo reads a keyword-plus-number anywhere in a merged body, negation included, so the disclaimer executed the thing it disclaimed - the same failure this thread recorded on 2026-11-18 18:30 UTC with PR #2005. If the intended disposition really is "cannot be modelled honestly", please close it by hand and say so; until then the request is open and unanswered.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No Pro surface was re-walked this pass; the nine routes this thread closed between 17-19 Nov still stand (store tree, techspecs grid + slug probe, firmware index, fingerprint index, FCC grantee, QSG/datasheet, eu/uk/ea storefronts, commerce backend).
This increment: PR #2235 -
devices/ubiquiti/usw-pro-xg-48-poe.jsondeclared 48 PoE+++ ports withpoeOut: trueand nopoe.budgetW, so the loader named its budget from the model string and got 0 W while the description beside it claimed 1080 W. Ubiquiti's own page givesTotal PoE Availability 200-240V AC: 1080W / 100-120V AC: 972W; 1,080 W is now in the spec and the 100-120 V ceiling is inpoe.note. Refs, does not answer this request.Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC exhibit, storefront row, fingerprint record), or confirmation that the cataloguedUDWis meant.2026-11-20 01:2x UTC - the Pro is still blocked; PR #2238 repairs the cellular-router row underneath this request. The request stays open, and the disposition question from 00:57 UTC is still unanswered.
No Pro surface was re-walked this pass. The nine routes closed between 17-19 Nov stand - store tree, techspecs grids plus direct slug probes, firmware index, fingerprint index, FCC grantee SWX, QSG/datasheet, eu/uk/ea storefronts, commerce backend - and nothing on this thread has moved since 00:57.
Unchanged blocker, precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No spec is written from the non-Pro UDW's numbers; that is the family-sibling error this catalogue has corrected on UDM PoE, two i-MO console ports and three MA5801 uplinks.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC exhibit, storefront row, fingerprint record), or confirmation that the cataloguedUDW(done,devices/ubiquiti/udw.json) is what was meant. Otherwise this needs a hand-written disposition - "cannot be modelled honestly" - because a PR body that merely says the request is unanswered has twice now been read as an answer (#2005, #2224).This increment - PR #2238:
devices/teltonika/rut951-poe.json(RUT951 PoE+, a NAT/DHCP/VPN cellular router) declared three PSE ports and carried nopoe.budgetW, so the loader took its budget from the model string, found no wattage, and set 0 W.show power inlineansweredbudget not modelled on RUT: the ports are reported, the power they could supply is notand an AP onlan2got nothing - on a unit whose datasheet printsPoE Power Budget (at PSE) 90 WoverPort 2-4 (LAN2, LAN3, WAN). Same defect class as #2235 and #2175. Also corrected:wwan1was at300Mon a Cat 4 radio (vendor:4G LTE Cat 4 up to 150 DL/50 UL Mbps; 300M is this family's Cat 6 figure),sourceUrlpointed at the non-PoE RUT951 page, and the description said two PSE outputs beside three declared ports. The 90 W is conditional - 15 W total on one Type 1 port when PoE-powered, none from an 802.3af feed or a sub-44 V DC supply - and that table now lives inpoe.note.Sources:
https://www.teltonika-networks.com/products/routers/rut951-poe(200, 3,082,884 B);https://solwise.co.uk/downloads/files/Datasheet_RUT951%20PoE+_1.06_19-02-2026.pdf(200, application/pdf, 3,875,741 B, 15 pp, text layer).2026-11-20 02:2x UTC — the Pro is still blocked. Two new surfaces were probed this pass, both negative; PR #2244 repairs the ECS-48S-PoE row in the meantime.
Re-probed tonight (no change):
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro— 307 →https://techspecs.ui.com/, 609,911 B (the not-found front page, same byte count as the control).https://store.ui.com/us/en/products/udw-pro— 404.Surface 10, guessed asset slugs on
dl.ui.com. The UDW's own datasheet lives athttps://dl.ui.com/ds/udw_ds.pdf(200,application/pdf, 544,909 B, 3 pp, text layer). If a Pro asset existed under the same convention it would answer the same way; insteadudw-pro_ds.pdf,udwpro_ds.pdf,udw_pro_ds.pdfandqsg/UDW-PRO/UDW-PRO-QSG.pdfall answer 200 withtext/html, 609,911 B — the front page, not a PDF. Presence/absence is measured bycontent-typehere, becausecurl -Lturns the miss into a 200.Surface 11, the Wayback index.
web.archive.org/cdxhas captures fortechspecs.ui.com/unifi/cloud-gateways/udw(five, 2025-11 → 2026-10) and forstore.ui.com/us/en/products/udw(back to 2023), and zero for any*-udw-pro*URL onstore.ui.com,techspecs.ui.com,dl.ui.comorea.store.ui.com;archive.org/wayback/available?url=store.ui.com/us/en/products/udw-proreturns an emptyarchived_snapshots. So the early-access listing this thread quotes was never archived by a third party either.Blocker, unchanged and precise: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No spec written.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC exhibit, storefront row, fingerprint record), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json) is what was meant. Failing all three, this needs a hand-written disposition — twice now a merge-time keyword in a PR body has been read as the answer.This increment — PR #2244:
devices/ubiquiti/ecs-48s-poe.jsondeclared 48 PoE+++ ports and carried nopoe.budgetW, so the loader named its budget from the model string, found no wattage and served 0 W while thedescriptionbeside it claimed 2,150 W. Ubiquiti's page gives the availability as four rows —200-240V AC Shared Mode: 2,150W,100-120V AC Shared Mode: 1,750W,200-240V AC Redundant Mode: 950W,100-120V AC Redundant Mode: 750W— and 2,150 W is now the modelled ceiling with the three conditions inpoe.note. Same PR: the serial console the page prints (Console = 1) was missing (55 jacks for a 56-jack 1U switch), plus the 10M rung on the OOB management port and the 32 x 2.5 GbE bank. Same defect class as #2235 and #2238.Source:
https://techspecs.ui.com/unifi/switching/ecs-48s-poe— HTTP 200, 676,185 B, server-rendered, read 2026-11-20 02:24 UTC.Recorded for the next pass, not fixed here:
devices/ubiquiti/ecs-48-poe.json(the non-S 48-port) is the same row without a budget — the audit reads48 PSE, prose says 2150 W— andecs-24s-poe.jsonreads25 PSE, prose says 1050 W. Both should be settled against their own pages before another non-Ubiquiti device is pulled in.2026-11-20 03:1x UTC — still blocked; one new surface probed, negative. No spec written, and PR #2249 deliberately does not carry a
Fixesline for this issue.Surface 12, an enumerable index on
techspecs.ui.com. If the Pro exists under a slug nobody has guessed, a sitemap would name it.https://techspecs.ui.com/sitemap.xmland.../robots.txtboth answer HTTP 200,text/html, 609,911 B — the same front page as the controls on this thread, i.e. "not found" on this host, and there is no XML sitemap to enumerate. So the gateway grid already read on 2026-11-17 remains the only index Ubiquiti publishes, andudw-prois absent from it.Blocker, unchanged: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO, a signed-in read ofea.store.ui.com, or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json) is the unit meant. Otherwise this needs a hand-written disposition — it is not going to close from a source.This increment, PR #2249: the next job this thread recorded, done instead.
devices/ubiquiti/ecs-48-poe.jsonandecs-24s-poe.jsonboth declared PoE+++ and nopoe.budgetW, so the loader named the budget from the model string and served 0 W while their descriptions claimed 2,150 W and 1,050 W — same class as #2235/#2175/#2244. Now 2,150 W (four availability rows) and 1,050 W (six rows; 2,250 W needs the separately sold 1,200 W modules). Same PR: the 24S serial console was missing (31 of 32 jacks), the 10M rung on every RJ45 bank across all four ECS PoE files, the QSFP28 stacking-only note, andpoeOut: falseon the OOB management port of the two S rows — the engine was crediting that mgmt jack with 15.4 W, giving 49 PSE on a box the vendor prints as "PoE Ports: 48".2026-11-20 03:2x UTC - still blocked; no Ubiquiti surface was re-walked this pass (the nine on this thread are exhausted and were last measured at 03:11, ten minutes ago). This increment went to the EdgeSwitch PoE family instead.
Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No spec written, and PR #2251 deliberately carries no closing keyword for this issue.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC exhibit, storefront row, fingerprint record), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json) is the unit meant. Otherwise this needs a hand-written disposition.This increment - PR #2251:
es-24-250w.json,es-48-500w.jsonandes-48-750w.jsonmodelled every copper port as a bare 1G jack - no connector, nopoeOut, no budget, nosourceUrl- so a 24/48-port 802.3at switch sourced nothing andshow power inlinereported zero PSE ports. Their pages printTotal PoE available = 250Wand500W(now modelled), and the 750 W unit prints no total-PoE row at all (750 W PSU, 64 W max draw excluding PoE) so it isbudgetUnknown, the same call as ES-24-500W. Each also gains the RJ45 serial console it prints (26 of 27 jacks on the 24-port, 52 of 53 on both 48-port units).Sources:
https://techspecs.ui.com/uisp/wired/es-24-250w,.../es-48-500w,.../es-48-750w,.../es-16-150w- all HTTP 200 server-rendered tables, 574-583 KB, none the 609,911 B front page this host serves for a missing slug.Recorded for the next pass, not fixed here:
es-16-150w.jsonstill takes its 150 W budget from the model name - its page prints a 150 W PSU and a 150 W max consumption and noTotal PoE availablerow, so it needs a datasheet that states the allocation, not another re-read of the same page.2026-11-20 03:5x UTC — reopened. This issue was closed by the forge's own closing-keyword parser, not by a fix, and no UDW-PRO spec exists.
What closed it. PR #2249 ("devices(ubiquiti): three Enterprise Campus PoE rows served 0 W from a 2,150 W chassis") merged at 03:45:23Z; this issue was closed at 03:45:24Z, one second later, with no comment. That PR's body opens:
Forgejo reads a closing keyword followed by
#Nanywhere in a PR body and ignores the negation, so the words "close #130" inside a disclaimer closed the issue on merge. This is the same shape the repository already records:scripts/close-merged-issues.jsline 104 notes that on 2026-11-18 the forge closed #803 from "Why it cannot close #803" and #130 from "This PR does not close #130", and both had to be reopened. Our own closer (scripts/close-merged-issues.js) rejects the sentence — CLAIM_START refuses a keyword that does not open a line or sentence — so the merge webhook path, not the sweep, is what acted.The catalogue still does not answer the request.
grep -ril "udw" devices/returnsdevices/ubiquiti/udw.json(the 420 W non-Pro Dream Wall) anddevices/ubiquiti/udr-5g-max.json(refs #130only); there is noudw-pro*file, noUDW-PROmodel string anywhere underdevices/, andnode scripts/sweep-device-requests.jsat 03:52Z reports "device/hardware requests: 0" only because this issue had been closed a few minutes earlier.node scripts/check-closed-issues.jsat 03:5xZ reported this close against its own record:Blocker, unchanged since the last pass: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Twelve Ubiquiti-hosted surfaces have now been probed on this thread (techspecs page and its Next.js routes,
dl.ui.comdatasheet slugs, the store tree, the FCC grantee census, the firmware platform index, the Chile SUBTEL register, sitemaps) and none namesUDW-PRO; the publisheddl.ui.com/ds/udw_ds.pdfis the non-Pro Dream Wall.Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(product page, datasheet, quick-start, firmware platform code) carrying the port table.Wording rule for future PRs here: this issue is referenced as
Refs #130 only, and the closing keywords never appear adjacent to the number — a merge must not be able to read as an answer. #803 is in the same state (closed 2026-11-19T02:41Z, no spec) and is the next thing to restore.2026-11-20 05:2x UTC — the Pro is still not a product, and this pass re-counted the shelf instead of re-reading one grid. No spec written; PR #2265 repairs three PoE rows underneath the request and carries
Refs #130 only.The absence, measured rather than sampled, with a control that cuts against the obvious reading.
node scripts/ubiquiti-techspecs-census.js --match 'udw|dream'at 05:2xZ: eight grids, all 200 — accessories 18 cards / 816,361 B, cloud-gateways 16 / 610,412, door-access 61 / 706,784, integrations 36 / 623,688, physical-security 146 / 876,302, switching 70 / 763,907, wifi 47 / 665,417,/uisp14 / 591,708 — 408 cards, 398 unique SKUs, 10 duplicated across grids, andMatching /udw|dream/returns eight consoles of which exactly one is a Dream Wall (UDW,/unifi/cloud-gateways/udw); the other seven are UDM/UDM-Pro/UDM-Pro-Max/UDM-SE/UDM-Beast/UDR/UDR7/UDR-5G-Max.The control matters more than the count: five product pages answer 200 with no card on any shelf (
uxg-lite,uxg-max,uxg-fiber,uxg-enterprise,uxg-pro), so "not on a grid" proves nothing here — the slug probe is what settles a SKU, and/unifi/cloud-gateways/udw-prois 307 with a 1-byte body against 200 / 704,702 B for the UDW positive control and 307 for thebogus-xyznegative control. A missing card and a missing page are different findings, and only the second one is evidence.Blocker, unchanged: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Thirteen vendor surfaces have now been read across this thread and none names the SKU; the published
dl.ui.com/ds/udw_ds.pdfis the non-Pro Dream Wall, and modelling one from the other is the family-sibling error this catalogue has corrected on UDM PoE, two i-MO console ports and three MA5801 uplinks.Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC exhibit, storefront row, fingerprint record), a signed-in read ofea.store.ui.com(this worker is anonymous), or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json, 20 interfaces, re-verified against the vendor table this pass:17 (4 PoE++; 4 PoE+; 4 PoE) (1G/100M/10M),PoE Budget 420W, per-port PSE15.4W / 30W / 60W,112W (Excluding PoE output)) is the unit meant. Otherwise this needs a hand-written disposition — three merges have now been read as an answer by the forge's keyword parser, and none of them was one.This increment — PR #2265: three Ubiquiti 150 W rows served a power-supply rating as a PSE allocation.
us-16-150wwas 150 W against Ubiquiti's ownTotal available PoE 122W(datasheet p.7:Including PoE Output 150W / Excluding PoE Output 28W) — 28 Wshow power inlinehanded out that the supply cannot give;es-16-150wandes-8-150wkeep 150 W but are now traced to the vendor's150W total PoE availabilityrather than to the model string, and both gain the out-of-band UART console their pages print.audit-poe-budget"inferred from name": 11 -> 8. Same defect class as #2235, #2238, #2244 and #2251.Sources:
https://dl.ui.com/datasheets/unifi/UniFi_PoE_Switch.pdf(200, 3,962,155 B, 12 pp, text layer — the family datasheet the census file had ruled out because it only looked underdl.ui.com/ds/);https://web.archive.org/web/20231113045611id_/https://store.ui.com/us/en/products/us-16-150w(200,Total available PoE 122W, tagpoe:122w);.../20240409153711id_/.../es-16-150w;.../20240906195421id_/.../es-8-150w.2026-11-20 06:3x UTC — no Ubiquiti surface was probed this pass, so nothing on this thread changed; the increment went to the HPE OfficeConnect PoE rows instead (PR 2270, no closing keyword).
Blocker, unchanged and precise: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Thirteen vendor surfaces are closed on this thread and the last measurement (05:2x) still shows
/unifi/cloud-gateways/udw-proat 307 / 1 byte against the UDW's 200 / 704,702 B.Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO, a signed-in read ofea.store.ui.com, or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json, 20 interfaces, 420 W) is the unit meant. Otherwise this needs a hand-written disposition.2026-11-20 07:2x-08:0x UTC — the storefront's route map read rather than one more slug; the increment went to three Ubiquiti PoE rows (PR 2274,
Refs #130 only, no closing keyword).New instrument: the storefront product page is a spec source.
store.ui.com/us/en/products/udw(200, 568,234 B) is not the empty SSG shell that.../searchreturns — its__NEXT_DATA__carriestechnicalSpecification.sections[].features[]as label/value rows, plusdisplaySku: "UDW (420W)",historicalSlugs(dream-wall,dream-wall-ea,udw,unifi-dream-wall) anddocuments: [{"InstallationGuide", "https://dl.ui.com/qig/udw"}]. For any product whose slug is known that is a second, independently maintained vendor copy of the spec and a key todl.ui.com/qig/<slug>. It does not help here, because the slug is the thing that is missing.The enumeration idea, measured and rejected.
store.ui.com/us/en/category/cloud-gateways-wifi-integrated(200, 426,733 B) embedssubCategories[].products[]— 15 cloud gateways, each with a fulltechnicalSpecification: EF-Core, EFG, UDM-Beast, UDM-Pro-Max, UDM-Pro, UDM-SE (180W), UCG-Fiber (30W), UCG-Max, UCG-Ultra, UCG-Max-NS, UCG-Industrial (270W), UDR-5G-Max (15W), UDR7 (15W), UX7 twice. UDW is not among them, although its page 200s and its owncategory.currentCategory.idis that same slug, and a different slug (cloud-gateways-large-scale, 426,232 B) returns the identical 15. So this index cannot be cited as a negative — the same lesson the UXG control forced on the techspecs grids. There is no other enumeration:us/en/collections/*,api/search,api/products,api/collection,api/compareand every product miss return one byte-identical 204,478-byte not-found body;sitemap.xml/robots.txtare 307;api/opensearchis a 502-byte OpenSearch description document that ignores every parameter, and.../search?search=UDW-PROis byte-identical to?search=zzzznotathingat 261,056 B — a 200 on that route is the shell.What the same pass did measure:
us/en/products/udw-prois 404 with that not-found body, against 200 / 568,234 B forudw; cleaner than techspecs, where the Pro slug is a 1-byte 307 andcurl -Lturns a miss into the front page. The UDW page holds zero occurrences ofudw-pro/UDW Pro/Dream Wall Pro, withlinkedProducts: [],compatibleProductsandupsellProductCategoriesnull — it points at no sibling.This increment — PR 2274: three Ubiquiti rows sourced PoE and could not say how much, and two quoted an adapter rating as a PSE allocation.
usw-flex: description said 60 W, the vendor row isPoE++/60W PoE adapter input: 46W / PoE+ input: 20W / PoE input: 8W— 60 W is the adapter, sold separately, so a Flex on a PoE+ uplink hands out 20 W and cannot run four 15.4 W cameras.udb-switch: description said 60 W, the vendor row is60W AC adapter input: 35W / 210W AC adapter input: 185W— 35 W across eight PoE+ ports on that adapter.eav-xg-24-poe: 2,150 W is real but conditional (100-120V AC redundant: 850W), so the field now names the four voltage/PSU-mode figures.audit-poe-budget: silent 88 -> 85, prose 13 -> 10.Blocker, unchanged: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Fourteen vendor surfaces are now closed on this thread and none names the SKU.
Unblock, unchanged: any Ubiquiti-hosted artefact naming
UDW-PRO, a signed-in read ofea.store.ui.com, or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json, 20 interfaces, 420 W) is the unit meant. Otherwise this needs a hand-written disposition.Sources:
https://store.ui.com/us/en/products/udw(200, 568,234 B);https://store.ui.com/us/en/products/udw-pro(404, 204,478 B);https://store.ui.com/us/en/category/cloud-gateways-wifi-integrated(200, 426,733 B);https://store.ui.com/api/opensearch?keyword=UDW(200, 502 B);https://techspecs.ui.com/unifi/switching/usw-flex,/unifi/wifi/udb-switch,/unifi/switching/eav-xg-24-poe(each 200, text layer). Recorded inresearch/ubiquiti-storefront-structure-spec-payload.md.2026-11-20 08:2x-08:5x UTC — one new surface read, no Pro; the increment went to the ten door-access hubs whose PoE direction was inverted (PR 2280,
Refs #130 only, no closing keyword).New on this thread: the storefront payload's
variantsarray, not just its spec rows.https://store.ui.com/us/en/products/udw(200, 568,234 B, read 08:3x UTC) carriesprops.pageProps.collection.products[0]withoptions: []and exactly one variant:documentsis a single entry (InstallationGuide->https://dl.ui.com/qig/udw). So the Wall's page is not a family page with a Pro hiding behind an option selector: it has no options at all and one SKU variant. That closes the last "maybe the Pro is a variant of UDW" reading - every other anonymous Ubiquiti surface was already measured closed on this thread (techspecs slug census, storefront slug/storeId probes, the SWX FCC grantee list, the 701-record controller fingerprint DB).Blocker, unchanged and precise: no Ubiquiti-published artefact names
UDW-PRO— so the whole census is missing (RJ45 and SFP+ counts and rates, WAN split, PoE class mix and total budget, drive bays, cellular/WAN options). Unblock is unchanged: any vendor artefact namingUDW-PRO, a signed-in read ofea.store.ui.com, or the requester confirming the SKU meant is the catalogued UDW (devices/ubiquiti/udw.json, 20 interfaces, 420 W).What the pass did instead (PR 2280).
node scripts/audit-poe-budget.jslisted 25 Ubiquiti specs as silent PSEs; ten are door-access boxes whose input was modelled as the PoE source. Ubiquiti's own row ontechspecs.ui.com/unifi/door-access/<slug>is (1) PoE++ input, 50V DC, 1A + (N) PoE[+] outputs, 30 W per port (Max 45/55/190 W aggregated) — eth0 is now the PD input and eth1..N are the PSE ports behind that aggregate budget.ua-hub-door,ua-hub-door-mini,ua-hub-gate,ua-hub,eah-8,ua-g3-sk,ua-g3-sk-pro,ua-g3-sk-gate,ua-g2-sk,ua-g2-sk-pro. Silent PSEs 85 -> 75; Ubiquiti 25 -> 15.ua-g3-sk-elevatorwas left alone: its page prints (4) networking + (1) management = 5 jacks and a PoE row of 1 in + 4 out = 5, and which jack is the input cannot be derived from it.2026-11-20 09:5x UTC — no new UDW-PRO surface was probed, so this thread's blocker is unchanged; the increment went to the EdgeSwitch XP PoE census underneath it. PR #2290 (reference only).
Four catalogue entries in Ubiquiti's 24 V passive line disagreed with the vendor:
devices/ubiquiti/es-10x.jsonclaimedpoeOuton all eight copper ports and thepoe-psecapability. Ubiquiti's own copy for the SKU reads "PoE passthrough support" where the ES-10XP reads "each equipped with a 24V passive PoE output"; the 10X ships a 24V/1A (24 W) adapter against the XP's 2.5 A (60 W) and a published 15 W per-port cap. The eight source claims are gone.poeOutClass: "PoE"— 802.3af in this catalogue's vocabulary, a negotiated 48 V standard these boxes do not speak. All three now readpassive, likees-16xp.json.Read 2026-11-20, HTTP 200, crawler UA:
techspecs.ui.com/uisp/wired/es-10x(574,925 B),es-10xp(575,764 B),es-18x(580,575 B),es-5xp(574,944 B). The 10XP's 52 W is a derived ceiling (60 W adapter less 8 W draw), marked DERIVED; the 18X and 5XP get no budget because neither page prints a total — on the 18X the adapter arithmetic (10 W) falls below the per-port cap, so 15 W would be a claim the supply cannot honour.Blocker here, unchanged: the whole UDW-PRO census, and the product's absence from thirteen Ubiquiti surfaces. Last measurement stands (
/unifi/cloud-gateways/udw-pro307 / 1 byte vs the UDW's 200 / 704,702 B). Unblock unchanged: any Ubiquiti-hosted artefact namingUDW-PRO, a signed-in read ofea.store.ui.com, or the requester confirming the catalogued UDW (devices/ubiquiti/udw.json, 20 interfaces, 420 W) is the unit meant.jaylouisw referenced this issue2026-11-20 18:33:01 +00:00
2026-11-20 18:3x-18:4x UTC - one more surface measured, and it is a shell; this increment went to six recorder PoE budgets (PR #2297, no closing keyword).
New surface on this thread:
community.ui.com/search- the forum's own search route, not thehelp.ui.comknowledge base. Three requests, same UA:UDWtext/htmlUDW-PROxzqv-nonexistentAll three are the same ~2.6 KB SPA document -
<title>Ubiquiti Community</title>, anog:urlechoing the query, zero result markup, no__NEXT_DATA__and no result endpoint. The byte count moves with the query string, not with the term, and a string that cannot exist returns the identical shell: this route cannot distinguish "the Pro is absent" from "nothing is rendered", so it settles nothing. Recorded so no later pass spends time on it.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and their rates, which of those ports source PoE and at what class, the total budget, and the radio count - with no Ubiquiti-hosted page, datasheet, store row, FCC grant, firmware entry or machine-readable catalogue entry that carries it. What would unblock: a
techspecs.ui.com/unifi/...page, adl.ui.com/ds/udw-pro_ds.pdf, or a store listing with a SKU.2026-11-20 21:2x UTC — reopened. This close came from the forge's closing-keyword parser again, and this time the sentence was a disclaimer that PR #2301 had already merged.
What closed it. Issue 130 went to
closedat 19:08:37Z, three seconds after PR #2301 merged at 19:08:34Z, with no comment on the issue — so it was notclose-merged-issues.js, which posts its marker before changing state. #2301's body opens:No UDW-PRO spec exists:
devices/ubiquiti/holdsudw.json(the 420 W non-Pro box, 20 interfaces) and nothing matchingudw-pro.One new detail about the parser, measured on this close. The ambiguous sentence named two requests; only the first was closed. Issue 803 is still open. So the forge's run does not treat
oras a separator — the keyword binds to the number immediately after it, and the second reference is safe. That is narrower than "every number near a keyword", and it is why a body can lose exactly one of two requests and still read as if it disclaimed both.Count. This is the third close of a
[Device]:request on its own disclaimer (#2000/#803 and #2005/#130 on 2026-11-18, both reopened by hand; now #2301/#130).scripts/check-closing-keywords.jsreports this shape asnegatedbefore a push, but it is not wired into CI and was not run on #2301. The safe body isRefs #130in a sentence with no closing keyword, or "issue 130" with no hash.Blocker unchanged. Ubiquiti publishes no artifact for UDW-PRO (the nine surfaces in this thread); nothing was re-walked this pass. Reopened, not modelled.
jaylouisw referenced this issue2026-11-20 21:25:46 +00:00
2026-11-20 21:5x UTC — the Pro is unchanged; this increment went into the base UDW row, which is the model this request's use case would actually run on. PR #2320 (
Refs #130only, no closing keyword).Surface 15, measured.
https://ui.com/sitemap.xmlis 200,application/xml, 7,794 B, 82<loc>entries — a real index, unlike the techspecs one on this thread — but it carries category pages only (/cloud-gateways,/cloud-gateways/wifi-integrated,/cloud-gateways/large-scale), no per-product URL. The page it indexes,https://ui.com/cloud-gateways(200, 529,519 B), embeds a schema.orgItemList: 14 gateways, positions 1-14, position 13"name":"Dream Wall"→/unifi/cloud-gateways/udw. Zero entries name a Pro. That is Ubiquiti's own marketing taxonomy, and the sixth independent vendor surface (after the tech-spec grid, storefront, fingerprint register, SWX grantee census and firmware platform codes) to print the same range with no Pro member.What did change — the base UDW's WAN side.
devices/ubiquiti/udw.jsonshipped eighteen interchangeable copper ports,eth0-eth17, with no WAN role at all, against its own cited sources: datasheet(17) LAN: GbE RJ45 / (1) WAN: 2.5 GbE RJ45and(1) LAN + (1) WAN 10G SFP+, plus tech-spec rowsMax. WAN Port Count 8andDefault WAN Ports (1) 2.5 GbE RJ45 / (1) 10G SFP+.eth17is nowwan1withrole: "wan"; both cages declaredualRole ["wan","lan"]because the datasheet does not number them. A routed lab can now cable NAT outside to the port the vendor designates.Blocker, unchanged and precise: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO, a signed-in read ofea.store.ui.com, or the requester confirming the SKU meant is the catalogued UDW (devices/ubiquiti/udw.json, now 22 interfaces) or the UDM-Pro.2026-11-20 22:2x UTC - storefront re-measured with a control slug, and a stored 404 hash retired. PR #2324 (Refs only, no closing keyword).
Why the method changed. The not-found body is 213,322 B today, not the 204,478 B / md5
39388de6395c...this thread recorded on 2026-11-19/20 - the storefront was rebuilt and its 404 shell grew 8,844 bytes. A later pass comparing bytes against that record would have read the drift as a product appearing.Same-minute control, redirects not followed, bot UA and desktop Chrome UA identical:
store.ui.com/us/en/products/udwstore.ui.com/us/en/products/udw-prostore.ui.com/us/en/products/xzqv-nonexistent-sku(control)store.ui.com/us/en/pro/products/udwSo the Pro's 404 is a real status and a real absence, at the requested URL, and the impossible slug returns the identical body - the test is the control, not a stored hash. Two traps recorded:
/us/en/pro/products/udwstill 308s to/us/en/products/udw(the archived/pro/prefix is an alias, so probing only it tests a redirect), andproducts.json/sitemap_products_1.xml/collections/all/products.jsonall 307/308 away - the store is a Next.js app (motif-theme,assets.ecomm.ui.com), not Shopify, so there is no product API to enumerate.No spec change. The live product payload (
__NEXT_DATA__->collection.products[0].technicalSpecification) agrees withdevices/ubiquiti/udw.jsonon all six port/PoE/WiFi rows; itsMax. WAN Port Count = 8names a ceiling and the default WAN pair but no per-port rule, so the seventeen GbE ports stay non-WAN rather than being marked on a guess.research/ubiquiti-storefront-product-payload.md.Blocker unchanged: a Ubiquiti page, datasheet, FCC exhibit or quick-start guide naming UDW-PRO's ports and PoE budget, or the requester confirming they meant the UDW.
2026-11-20 22:5x UTC - the Pro is unchanged (surfaces not re-walked; last measurement 22:29, nothing has changed). This pass took the base UDW row again, and found it did not bridge. PR #2329 (Refs only).
devices/ubiquiti/udw.jsonshipped the seventeen 1G LAN sockets as seventeen routed interfaces - nol2-forward- so on the model this request's requester would actually run:switchport access vlan 10->% cannot switch frames: it has no l2-forward capability;channel-group 1 mode active->% cannot bundle ports into a LAG;eth0andeth1in 192.168.1.0/24 could not resolve each other's ARP (frames dropped asnot addressed to this device), and an address oneth0was answered oneth0only - a host oneth1could not reach its own gateway.Ubiquiti states the opposite on the page this row already cites:
https://techspecs.ui.com/unifi/cloud-gateways/udw(200, 704,702 B, read today) prints MAC Address Table Size = 8,000, VLAN = 802.1Q, and 1 GbE RJ45 = 17 (4 PoE++; 4 PoE+; 4 PoE / 1G/100M/10M), and the storefront payload (store.ui.com/us/en/products/udw, 200, 568,234 B) repeats both plus a LACP Port Aggregation row. A MAC table is a bridge table; a routed-only gateway holds neither it nor a LAG.l2-forwardis now declared; the census (17+1+2, 12 PoE ports, 2 radios) andwan1's role are untouched,no switchportstill makes a LAN port routed, andtest/udw-lan-bank-bridges.test.jsgates it.Blocker, unchanged: no Ubiquiti source publishes a Dream Wall Pro; the SKU is absent from the gateway index, the storefront (nine storefronts, control-slug tested), the compliance register, the FCC grantee census and the firmware platform codes. The four sibling gateways (
udm,udm-pro-max,ucg-max,uxg-max) carry the same missing capability; they were not edited here because each needs its own rows read first.2026-11-20 23:5x UTC — the Pro is unchanged; this pass closed the loose end the 23:02 comment left — "the four sibling gateways carry the same missing capability; each needs its own rows read first". Three of them are read and fixed. PR #2334 (
Refsonly, no closing keyword).Same UA, server-rendered pages, byte counts as returned:
MAC Address Table Size = 4,000;LACP Port Aggregation(storefront note "GbE RJ45 ports 1-8");Port Layout 1 GbE RJ45 = 8MAC Address Table Size = 2,000;Port Layout 2.5 GbE RJ45 = 5/us/en/products/ucg-max307s to the category path)MAC Address Table Size = 2,000; VLAN-segmentation and LACP rows EmptyEach row declared its eight / four LAN sockets as routed interfaces. Measured on UDM-Pro-Max before the change, two hosts on Port 1 / Port 2 in 192.168.1.0/24:
ARP: false, andswitchport access vlan 10answered "cannot switch frames: it has no l2-forward capability". A MAC table is a bridge FDB and a LAG over ports 1-8 cannot be built from routed ports, so all three now declarel2-forward— the token is MAC learning + flooding and nothing else (engine/device.js), which is why UXG-Max can carry it while its VLAN and LACP rows stay Empty in the note.test/ubiquiti-gateway-lan-bridges.test.js, 28 assertions.One model left alone, deliberately:
UDM(the non-Pro box). Its tech-spec page carries no Networking section at all — 0 occurrences ofMAC Address Tableon 608,032 B — and the onlyVLAN 802.1Qline indl.ui.com/ds/udm_ds.pdf(200, 747,030 B, 3 pp, text layer) sits in the wireless block beside "BSSID Up to 8 per radio". Nothing vendor-published says those four LAN sockets bridge, so nothing was declared.Blocker, unchanged: no Ubiquiti source publishes a Dream Wall Pro — not the gateway index, the storefront, the fingerprint register, the FCC grantee census or the firmware platform codes. Unblock is still any vendor artefact naming
UDW-PRO, or the requester confirming they meant the catalogued UDW or the UDM-Pro.2026-11-21 00:2x UTC - the Pro is unchanged; this pass swept the defect class of PR #2334 onto the four gateway rows it left behind. PR #2338 (
Refs #130only, no closing keyword).UDM-Pro,UDM-SE,UCG-UltraandUCG-Fibershipped their LAN banks as routed interfaces with nol2-forward. Measured before the change, two hosts in 192.168.1.0/24 on two adjacent LAN ports: ARP false, andswitchport access vlan 10-> "cannot switch frames: it has no l2-forward capability".Both Ubiquiti surfaces publish the opposite, read 2026-11-21:
A MAC table is a bridge FDB; a LAG over ports 1-8 cannot be built from routed ports. All four now declare
l2-forward; the two UCG rows do not claim bundle support because their LACP row is Empty on both surfaces. Census, WAN roles andno switchportare untouched.test/ubiquiti-gateway-lan-bridges.test.jscovers 7 models, 66 assertions. Gates: syntax 506 OK, audit-port-types and audit-devices 0 defects, hardware 26/0, run-tests 426 suites / 14,192 assertions 0 failed.Also fixed:
UDM-Pro.json's note carried "no 'l2-forward'" as a deliberate choice copied from the Dream Machine line - the clause #2334 refuted forUDM-Pro-Max; it is gone.Blocker, unchanged: no Ubiquiti source names
UDW-PRO(gateway index, storefront with control slug, fingerprint register, FCC census, firmware platform codes). Not re-walked this pass; last measurement 23:56Z.2026-11-21 01:2x UTC - the Pro is unchanged (no new surface this pass); this increment went into the Dream Router row. PR #2346 (
Refs #130only, no closing keyword).Two vendor surfaces that the thread had not used for the layer-2 question:
https://static.ui.com/fingerprint/ui/public.json(200, 832,585 B, sku UDR) listsdeviceCapabilities=GATEWAY,SWITCH,ACCESS_POINT,NETWORK_APPLICATION,PROTECT_APPLICATION,CONTROLLER,APPLICATION_MODE,HAS_CLIENTS, andunifi.network.diagram=01 02 03 04 __ 05. That is the vendor saying which gateways are switches, per SKU - and which are not: UXG-Lite, UXG-Enterprise, UXG-Pro and EFG carry noSWITCH.4 + 1with the singleton set apart matches the datasheet'sLAN: (4) / WAN: (1), so the UDR's fifth socket is its WAN andeth4now says so;ip nat outsidecan be cabled to it.devices/ubiquiti/udr.jsonshipped four LAN sockets as routed interfaces: hosts in 192.168.1.0/24 on eth0 and eth1 could not resolve each other's ARP, andswitchport access vlan 10answered "cannot switch frames". The tech-spec table printsMAC Address Table Size = 1,000and VLAN segmentation, the datasheet printsVLAN 802.1Q. Fixed, with a new row intest/ubiquiti-gateway-lan-bridges.test.js(75 passed).Seven rows still need it and each needs its own count read first -
research/ubiquiti-fingerprint-switch-capability.mdlists them (UDM, UDR7, UDR-5G-Max, UXG-Fiber - notucg-fiber, UCG-Industrial, UDM-Beast, EF-Core).2026-11-21 01:5x UTC - the Pro is unchanged; this pass finished the seven-row worklist that
research/ubiquiti-fingerprint-switch-capability.mdleft open. PR #2349 (Refs #130 only, no closing keyword;scripts/check-closing-keywords.js --pr 2349-> 0 at risk).Ubiquiti's controller device database classifies all seven as
SWITCH, and each one's own tech-spec page prints a bridge forwarding database. Read 2026-11-21, bytes as returned; an unknown slug 307s to the 609,911 B techspecs front page, so the byte count is the control:VLAN 802.1QAll seven now declare
l2-forward. Measured before the change on each row: hosts in 192.168.1.0/24 on two adjacent LAN ports could not resolve each other's ARP, andswitchport access vlan 10answered "cannot switch frames: it has no l2-forward capability".One honesty note: the UDM's tech-spec URL carries the model name and no specification table at all (125 text cells, no
MAC Address Table Sizerow), so its evidence is the datasheet text layer plus the fingerprint'sSWITCH- weaker than a printed FDB size, and labelled as such in the spec note.No copper socket was renamed WAN. UDR7 / UDR-5G-Max print
Default WAN Ports = (1) 10G SFP+ / (1) 2.5 GbE RJ45withMax. WAN Port Count = 4over one unbroken five-socket diagram, UCG-Industrial three defaults over six; the4 + 1separator that let the UDR get a WAN role is not present on any of them.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and their rates, which ports source PoE and at what class, the total budget, and the radio count - with no Ubiquiti-hosted page, datasheet, store row, FCC grant, firmware entry or machine-readable catalogue entry that carries it. What would unblock: a
techspecs.ui.com/unifi/...page, adl.ui.com/ds/udw-pro_ds.pdf, or a store listing with a SKU.Gates: syntax 510 OK; audit-port-types 0 gated; audit-devices 0 hard defects; hardware 26/0; run-tests 430 suites / 14,367 assertions, 0 failed.
2026-11-21 02:3x UTC - the Pro is unchanged (no new vendor surface this pass); this increment made the WAN role on the two Dream rows actually separate a surface. PR #2351 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2351-> 0 at risk).PR #2320 gave
udw.json'swan1role: "wan", and PR #2346 gaveudr.json'seth4the same - but neither LAN bank declared a role.engine/device.jsownsIpOnseparates the two L3 surfaces only when both sides carry one (owner.role && inIface.role && owner.role !== inIface.role), so the invarianttest/port-roles.test.jshas asserted for the RT-AX89X since #8 - "the WAN port does not answer the LAN address" - was silently false on both rows: with192.168.1.1/24oneth0,ownsIpOn(wan1, '192.168.1.1')returned true, and a host cabled to the WAN socket inside192.168.1.0/24got an ICMP reply from the LAN gateway.Topology: one host on
eth0, one on the far side of the bank (eth5/eth1), one on the WAN socket in the LAN prefix.ownsIpOn(wan, '192.168.1.1')192.168.1.1eth0/eth5reaches itownsIpOn(wan, own address)17 UDW + 4 UDR copper LAN ports now declare
role: "lan". Vendor rows, re-read today, bytes as returned:https://dl.ui.com/ds/udw_ds.pdf(200, 544,909 B)Networking interface (17) LAN: GbE RJ45 ports / (1) WAN: 2.5 GbE RJ45 port;https://techspecs.ui.com/unifi/cloud-gateways/udw(200, 704,702 B)Default WAN Ports (1) 2.5 GbE RJ45 (1) 10G SFP+,Max. WAN Port Count 8;https://dl.ui.com/ds/udr_ds.pdf(200, 771,202 B)LAN: (4) GbE RJ45 ports / WAN: (1) GbE RJ45 port;https://techspecs.ui.com/unifi/cloud-gateways/udr(200, 685,837 B)Default WAN Ports (1) GbE RJ45. Record:research/ubiquiti-wan-lan-role-separation.md.Still unmodelled, recorded rather than guessed: the UDW's two SFP+ cages (the datasheet prints one LAN and one WAN cage without numbering them, so they keep
dualRoleand norole- measured consequence: an address on one cage still answers on the other) andMax. WAN Port Count 8(a ceiling, not a socket list). Radios stay role-less and still serve the LAN address.Gates: syntax 511 OK; audit-port-types / audit-devices 0 gated defects; hardware 26/0; run-tests 431 suites / 14,394 assertions, 0 failed; new
test/ubiquiti-wan-lan-role-separation.test.js27 assertions.Blocker, unchanged: the Pro itself - no vendor page, no SKU in the fingerprint index, no FCC grant, no Wayback capture.
2026-11-21 02:5x UTC - the Pro is unchanged (no new vendor surface this pass; the SKU is still absent from Ubiquiti's controller database as well as its catalogue). This increment went into the six compact gateways a lab actually substitutes for it. PR #2356 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2356-> 0 at risk).The vendor's controller database (
https://static.ui.com/fingerprint/ui/public.json, 200, 832,585 B) publishes a per-socket role map -ports={"eth0": "LAN", ..., "eth4": "WAN"},switchPorts,numberOfPorts- for 407 of its 701 devices, keyed bysku. Against it, 18 Ubiquiti gateway rows indevices/ubiquiti/were shipping their LAN bank with norole, which makesownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role) a no-op. Six are fixed in #2356 (UCG-Ultra, UCG-Max, UXG-Lite, UXG-Max, UX, UX7):ownsIpOn(<uplink>, '192.168.1.1')returned TRUE on each before the change.Two traps in that surface, recorded so the next pass does not walk into them. (1)
ports.plusis not "SFP+": USW-Ultra printsplus: [8]withstandard: 7for a chassis whose techspec row isPort Layout = 8 (7 PoE+; 1 PoE++ input) (1G/100M/10M)- the 8th socket is the PoE++ input, not a cage. (2)numberOfPorts/standardare counts, not assignments; the UDW printsstandard: 19besideplus: [17, 20]on 20 sockets, so only thelinkNegotiation.*.portIdxmapping is positional.Missing fields, unchanged: the whole UDW-PRO port layout, and the product. Nothing Ubiquiti hosts names it; the datasheet
dl.ui.com/ds/udw_ds.pdfis the 420 W Dream Wall. The 12 remaining role-less gateway rows (UDM/UDM-SE/UDM-Pro-Max, UCG-Fiber, UXG-Enterprise/Fiber, UDR7, UDR-5G-Max, EFG, usg-pro-4, uxg-pro, UDM) are queued for later passes, not modelled here because each has an SFP cage the vendor prints without saying which cage is the default WAN.maxis indexed and dropped, probes are unchangeable, and an IPv6 path has no trace #23602026-11-21 03:5x UTC - the Pro is unchanged; this pass closed the last Dream-family gateway without a LAN role. PR #2362 (
Refs #130only;scripts/check-closing-keywords.js --pr 2362-> 0 at risk).devices/ubiquiti/udm.jsonshippedWANandLAN 1-LAN 4all with norole, soownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role) was a no-op. With192.168.1.1/24onLAN 1,ownsIpOn(WAN, '192.168.1.1')returned the LAN interface and a host cabled to the WAN socket inside that prefix got an ICMP reply from the LAN gateway. Both vendor surfaces name the split, read 2026-11-21:https://static.ui.com/fingerprint/ui/public.json(sku= UDM)ports={"eth0":"LAN",...,"eth3":"LAN","eth4":"WAN"}, panel01 02 03 04 __ 05https://dl.ui.com/ds/udm_ds.pdf(4) LAN: GbE RJ45 ports / (1) WAN: GbE RJ45 porthttps://techspecs.ui.com/unifi/cloud-gateways/udmWhat is still role-less, and why. The fiber gateways (UCG-Fiber, UXG-Fiber) do have a
portsmap, but it puts the second SFP+ onWAN2while the page printsDefault WAN Ports (1) 10G SFP+ / (1) 10 GbE RJ45without numbering the cages - naming a cage there would risk moving a saved uplink, so they are left as they are. UCG-Industrial, UDM-Beast and EF-Core carry an emptyportsobject in the same database, so there is nothing to copy; UDR7 / UDR-5G-Max key fiveeth*sockets against a body that also has an SFP+, and the map cannot say which key is the cage.2026-11-21 04:2x UTC - the Pro is unchanged (no new vendor surface this pass); this increment closed the last two gateways whose whole panel had no role. PR #2365 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2365-> 0 at risk).UDR7andUDR-5G-Maxshipped four 2.5G RJ45 sockets and one 10G SFP+ cage, every one of them role-less, soownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role) never fired: with192.168.1.1/24oneth0,ownsIpOn(eth3, '192.168.1.1')returned true on both rows and a host on the WAN socket inside that prefix was answered by the LAN gateway.What made this one settleable where the Dream Machine cages were not: the controller database's
linkNegotiationblock is positional.skuUDR7 (832,585 B, read today) givesports={"eth0":"LAN","eth1":"LAN","eth2":"LAN","eth3":"WAN","eth4":"WAN2"}, andlinkNegotiationputseth2atportIdx 3,eth3atportIdx 4(2500/1000/100/10 FDX) andeth4atportIdx 5(10000/1000 FDX only) - so the five-socket panel is four copper plus one cage, and the cage is the default WAN2. The tech-spec pages agree in words:Port Layout = 2.5 GbE RJ45 4 (1 PoE) / 10G SFP+ 1,Max. WAN Port Count = 4,Default WAN Ports (1) 10G SFP+ / (1) 2.5 GbE RJ45(https://techspecs.ui.com/unifi/cloud-gateways/udr7, 694,590 B;.../udr-5g-max, 876,426 B).eth0-eth2now saylan,eth3andsfp1saywan.Why the UDM/UCG/UXG cages are still role-less, and this is not an oversight. For the three Dream Machine rows the controller names the uplink
eth8/eth9and the cagesplus: [10, 11], but the spec names its cagessfp1/sfp2; tyingsfp1toportIdx 10would decide which physical cage a lab's saved WAN sits in, on the strength of a numbering the datasheet explicitly declines to give ("(1) LAN: 10G SFP+ / (1) WAN: 10G SFP+"). Same forUCG-Fiber/UXG-Fiber, whoseportsmap puts WAN2 oneth6while the page prints one SFP+ default without numbering the cages. Those stay as they are.Missing fields, unchanged: the whole UDW-PRO port layout, and the product. Re-measured today:
store.ui.com/us/en/products/udw-proand.../unifi-dream-wall-pro404;techspecs.ui.com/unifi/cloud-gateways/udw-proandudwproboth 200 with 609,911 B at the techspecs front page (the control byte count for an unknown slug); the fingerprint register (832,585 B, 701 devices) still carriesUDWonly,numberOfPorts20.Also run this pass, for the record, not part of this PR:
node scripts/huawei-doc-gate-probe.json #803 - 30 ids,gated 27 / public 2 / absent 1, "nothing changed since the baseline". The E6600 board chapters are still behind the login wall, so #803 did not move either.2026-11-21 04:5x UTC — the Pro is still not a vendor product (
techspecs.ui.com/unifi/cloud-gateways/udw-proanswers 307Location: /, re-measured this minute), and this pass found the one thing the thread kept asserting that the vendor contradicts: the Dream Machine cages are numbered. PR #2369 (Refs #130only;scripts/check-closing-keywords.js --pr 2369-> 0 at risk).The three Dream Machine rows (
UDM-Pro,UDM-Pro-Max,UDM-SE) shipped both 10G SFP+ cages with norole, justified in their notes by "the datasheet prints one LAN and one WAN cage without numbering them". That is true of the datasheet and false of the controller, and the arithmetic closes without slack:static.ui.com/fingerprint/ui/public.json(200, 832,585 B)numberOfPorts11 =standard9 +plus[10, 11];eth9-> portIdx 10 (10000/1000),eth10-> portIdx 11 (10000/1000);portsnameseth9"WAN2",eth10"LAN"techspecs.ui.com/.../udm-pro(200, 676,527 B)Port Layout 1 GbE RJ45 9 / 10G SFP+ 2,Default WAN Ports (1) 10G SFP+ (1) GbE RJ45techspecs.ui.com/.../udm-pro-max(200, 677,375 B),.../udm-se(200, 682,320 B)2.5 GbE RJ45 1Nine RJ45 plus two cages is the whole box, so position 10 is the first cage and the default WAN2:
SFP+ 1nowrole"wan",SFP+ 2"lan", both keepingdualRole. The defect was real, not cosmetic — with192.168.1.1/24onPort 1,ownsIpOn(SFP+ 1, '192.168.1.1')returned the LAN interface, because the separation needs a role on both sides.udw.jsonis deliberately still role-less, and now says why. The same database printsstandard19 besideplus[17, 20] on a 20-socket box — 21 positions for 20 sockets — so the Dream Wall's cage order cannot be placed without guessing, which is the one thing this thread will not do. That is a narrower blocker than the one recorded before (it is the UDW's own count, not a missing vendor surface), and it does not touch the Pro, which still has no page in any Ubiquiti tree.Probes unchanged: 18 vendor surfaces tested across this thread,
udw-propresent in none;ui.com/sitemap.xml(200, 82<loc>, category pages only) has no per-product entry; the Common Criteria and FCC databases carry noUDW-PROSKU.2026-11-21 06:3x UTC — the Pro is unchanged; this pass closed the last two gateway rows whose whole copper bank had no role. PR #2380 (
Refs #130only;scripts/check-closing-keywords.js --pr 2380-> 0 at risk).Re-measured this minute:
techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307Location: /, 1 byte;store.ui.com/us/en/products/udw-pro-> 404. No vendor surface has appeared.UCG-FiberandUXG-Fibershipped all five copper sockets with norole, soownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role) never fired: with192.168.1.1/24on the first LAN port,ownsIpOn(WAN, '192.168.1.1')returned true on UCG-Fiber andownsIpOn(eth4, '192.168.1.1')returned true on UXG-Fiber — a host on the 10G RJ45 uplink inside the LAN prefix got an ICMP reply from the LAN gateway.The split is the vendor's own, from the controller database read today (
https://static.ui.com/fingerprint/ui/public.json, 832,585 B,skuUCG-Fiber and UXG-Fiber):ports={eth0: LAN, eth1: LAN, eth2: LAN, eth3: LAN, eth4: WAN, eth5: LAN, eth6: WAN2},linkNegotiationpinning eth0-eth3 to the 2.5G copper bank (portIdx 1-4), eth4 to the 10G RJ45 (portIdx 5) and eth5/eth6 to the cages (portIdx 6/7, 10000/1000 FDX only). Both tech-spec pages say it in words:Default WAN Ports (1) 10G SFP+ (1) 10 GbE RJ45,Max. WAN Port Count 6(200, 667,242 B and 649,433 B).What is still role-less, and why. The two cages on each Fiber row: the controller numbers them eth5 (LAN) / eth6 (WAN2), but neither row's cage names are Ubiquiti's — both pages print one undifferentiated
10G SFP+ 2row — so naming a cage would be an ordering guess that moves a saved uplink. Same reasonMax WAN Port Count 6stays unmodelled. UCG-Industrial, UDM-Beast and EF-Core still carry an emptyportsobject in the same database, and UXG-Pro / UXG-Enterprise / EFG name their cages only by controller index.2026-11-21 06:5x UTC — the Pro is unchanged (no vendor surface this pass), and this increment closed the last two gateway rows whose whole panel carried no role. PR #2385 (
Refs #130only;scripts/check-closing-keywords.js --pr 2385-> 0 at risk).Re-measured this minute:
techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 200 but the body is the 609,911-byte techspecs home page (the known trap for slugs Ubiquiti does not have);store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared.UXG-Enterpriseanduxg-proshipped every socket with norole. The Pro even names its copperrj45-wan/rj45-lan, but nothing in the engine reads a name: the check isowner.role && inIface.role && owner.role !== inIface.role, so with192.168.1.1/24on the LAN port,ownsIpOn(eth0|SFP+-2|SFP28-1, '192.168.1.1')returned the LAN bank on the Enterprise andownsIpOn(rj45-wan|sfp+1|sfp+2, ...)returned it on the Pro — a host cabled to any of those sockets inside that prefix got an ICMP reply from the LAN gateway.What made it settleable: the controller database's arithmetic closes without slack on both chassis.
https://static.ui.com/fingerprint/ui/public.json(200, 832,585 B,sku= UXG-Enterprise) givesnumberOfPorts6 =standard2 +plus[3, 4] +sfp28[5, 6],ports={eth0: WAN, eth1: LAN, eth2: LAN, eth3: LAN, eth4: WAN2, eth5: LAN}, andlinkNegotiationputs eth0/eth1 at portIdx 1/2 on 2500 FDX, eth2/eth3 at 3/4 on 10000, eth4/eth5 at 5/6 on 25000 — so positions 1-2 are the two 2.5G RJ45, 3-4 the SFP+, 5-6 the SFP28, and the default second WAN isSFP28-1. Same file,sku= UXG-Pro: 4 =standard[0, 1] +plus[2, 3],ports={eth0: WAN, eth1: LAN, eth2: WAN2, eth3: LAN2}, eth2/eth3 at portIdx 3/4 on 10000/1000 — one cage per side, matchingdl.ui.com/ds/uxg-pro_ds.pdf(200, 433,832 B, text layer): "LAN: (1) 1 GbE RJ45 port / (1) 10G SFP+ port; WAN: (1) 1 GbE RJ45 port / (1) 10G SFP+ port". The tech-spec pages agree in words: "Default WAN Ports (1) 25G SFP28 (1) 2.5 GbE RJ45", "Max. WAN Port Count 5" (671,598 B) and "Default WAN Ports (1) 10G SFP+ (1) GbE RJ45", "Max. WAN Port Count 3" (649,578 B).dualRolewas withheld on both: the store page says "two interfaces remappable to WAN" and the pages print aMax. WAN Port Count, but no surface names which sockets, so a per-port reassignment claim would be a guess.dl.ui.com/ds/uxg-enterprise_ds.pdfstill answers 200 with the 609,911-byte front page, not a PDF.What is still role-less in the UXG/UCG family, and why. Only the Fiber pair's cages: the controller numbers them (eth5 LAN, eth6 WAN2) but neither row's cage names are Ubiquiti's — the page prints one "10G SFP+ 2" row — so naming a cage there is an ordering guess that moves a saved uplink. The EdgeRouter/EP-R/ER-X rows and the UISP-R rows have never had roles; none of them has a controller
portsmap, so there is nothing positional to copy.On this request: the SKU is absent from Ubiquiti's product index, its storefronts, the FCC grant index and the controller database, so
UDW-PROcannot be modelled from any source. The baseUDWremains the honest substitute and is catalogued —devices/ubiquiti/udw.json, 17 LAN + 2.5G WAN + 2 cages, 420 W PoE budget.2026-11-21 07:2x UTC — the Pro is unchanged (no new vendor surface); this increment went to the two Enterprise PoE switches underneath the box a lab would actually substitute. PR #2388 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2388-> 0 at risk).Re-measured this minute:
techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared since the 06:5x pass.The defect this pass found is a guessed figure, not a missing one.
USW-Enterprise-8-PoEandUSW-Enterprise-24-PoEshipped apoe.budgetW(120 / 400 W) and nopoeOuton any copper port.derivePortHardware()(engine/media.js) gives an undeclared copper port the 802.3af default of 15.4 W, so every socket on a datasheet-802.3at switch reported 15.4 W -web/faceplate.jsprintsPoE out <poeOut> W,web/app.jsprintsPSE, <poeOut> W out, both straight from the derived hardware. The vendor prints "PoE interface (8) PoE/PoE+ ... Max. PoE+ wattage per port by PSE 32W" (https://dl.ui.com/ds/usw-enterprise-8-poe_ds.pdf, 200, 526,714 B) and the same rows at 34.2 W / 400 W for the 24-port (https://dl.ui.com/ds/usw-enterprise-24-poe_ds.pdf, 200, 397,353 B); both tech-spec tables say "All PoE+". All 32 copper ports now declare the vendor's per-port ceiling and class, and both rows declarepoe-pse/802.3af/802.3at.Blocker, unchanged and precise: the whole UDW-PRO census - RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No spec written.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC grant, storefront row), a signed-in read ofea.store.ui.com, or the requester confirming they meant the catalogued UDW (420 W).2026-11-21 07:5x UTC — the Pro is unchanged (no vendor surface this pass); this increment fixed a PoE direction defect on the Flex 2.5G, the compact PoE switch a lab substituting for the Dream Wall would most likely put underneath it. PR #2391 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2391-> 0 at risk).Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared since the 07:2x pass.The defect.
USW-Flex-2.5G-8-PoEshipped apoe.budgetW(196) and no PoE direction on any of its ten sockets.derivePortHardware()(engine/media.js) fills that silence with the 802.3af default on every copper port of a switch whose label says PoE, so all nine copper sockets reported 15.4 W out — and the ninth of them is the boxs power inlet.Ubiquiti prints both facts on one page (
https://techspecs.ui.com/unifi/switching/usw-flex-2-5g-8-poe, 200, 632,312 B, server-rendered, read this minute):2.5 GbE RJ45 8 (All PoE++),10 GbE RJ45 1 (PoE+++),10G SFP+ 1PoE++ 8PoE 15.4W / PoE+ 32W / PoE++ 64WUp to PoE++(1) AC/DC adapter (Excluded), (1) PoE+++PoE+++ input: 76W / PoE++ input: 46W / PoE+ input: 16W / AC adapter: 196WSo the eight outlets now declare
poeOut: 64,poeOutClass: "PoE++", and the 10G RJ45 declarespoeIn: 90with nopoeOut— the 90 W being Ubiquiti own arithmetic (76 W available + 14 W maximum consumption with PoE input), not a standard lookup. A 25.5 W WiFi 6E AP can be cabled to any of the eight in the simulator now; before, every socket refused it. A newtest/usw-flex-2-5g-poe-census.test.js(27 checks) pins the census and both directions.Also checked and left alone:
USW-Pro-24-PoE/USW-Pro-48-PoEcarry the same missing-direction silence (16/40 PoE+ plus 8 PoE++), but neither Ubiquiti surface says which eight sockets are the PoE++ ones — not the datasheet ((8) 60W PoE++), not the tech-spec table (PoE++ 8), not the controller database (numberOfPorts/portsonly). The two surfaces also disagree on the ceiling (30W/32WPoE+ and60W/64WPoE++ on techspecs versus32W/64Wondl.ui.com/ds/usw-pro-24-poe_ds.pdf). Declaring the PoE+ floor on all 24/48 would be safe but would leave the PoE++ bank unmodelled, and picking the last eight would be an ordering guess — so that pair is not written, and it is the next candidate once someone finds a vendor source naming the sockets.Blocker, unchanged and precise: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No spec written.
Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO(page, datasheet, quick-start, FCC grant, storefront row), a signed-in read ofea.store.ui.com, or the requester confirming they meant the catalogued UDW (420 W).2026-11-21 08:2x UTC — the Pro is unchanged (no vendor surface this pass); this increment fixed the three Pro PoE racks a Dream Wall lab would put underneath the box. PR #2393 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2393-> 0 at risk).Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared.The blocker, restated precisely (unchanged since #10488). The issue asks for a
UDW-PROport/PoE census. Ubiquiti publishes no page for that SKU on any surface that has ever carried it: not in thetechspecscloud-gateway grid (sixteen cards,udwamong them,udw-prooccurring zero times in 610 KB), not in the US/EU/UK storefronts, no FCC grant underSWX, no archived capture. The only published Dream Wall is the 420 W UDW, and copying its panel onto a "Pro" is the family-sibling error this project has corrected three times. What would unblock it: Ubiquiti listing the Pro, or its quick-start guide printing a port layout — neither exists to read.The defect this pass found.
USW-Pro-24-PoE(400 W),USW-Pro-48-PoE(600 W) andUSW-Pro-Max-48-PoE(720 W) shipped apoe.budgetWand nopoeOuton any RJ45 socket.derivePortHardware()(engine/media.js) fills that silence with the 802.3af default of 15.4 W, so all 24 / 48 / 48 sockets reported 15.4 W out on chassis whose datasheets rate 32 W PoE+ and 64 W PoE++ — and on the Max 48 the declared budget (720 W) and the derived per-port figure could not both be true.Two vendor surfaces, and they disagree.
https://dl.ui.com/ds/usw-pro-24-poe_ds.pdf(200, 443,168 B) printsPoE interface (16) PoE/PoE+ / (8) 60W PoE++andMax PoE wattage per port by PSE PoE+: 32W / PoE++: 64W;https://techspecs.ui.com/unifi/switching/usw-pro-24-poe(200, 654,711 B) prints the same counts butPoE+ 30W / PoE++ 60W. The specs carry the datasheet figures and the 2 W disagreement is recorded innotesrather than averaged away.The one inference, declared. Ubiquiti prints counts, never port numbers. The PoE++ bank is the upper-numbered end of each speed bank (17-24, 41-48, 25-32 + 41-48), the ordering this catalogue already applies to
USW-Pro-Max-24-PoE— and leaving them undeclared was not neutral, it asserted 15.4 W on every socket. Thenotessay exactly that.Left for the next pass:
us-24-250wandes-24-500ware the last two Ubiquiti rows with a budget and no per-port direction.2026-11-21 08:5x UTC — the Pro is still absent from every Ubiquiti surface; this increment fixed the three 24-port PoE switches a Dream Wall lab would put beneath it. PR #2397 (Refs #130, no closing keyword;
scripts/check-closing-keywords.js --file-> 0 at risk).Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared since the last pass.Blocker, unchanged. The request asks for a
UDW-PROport/PoE census. Ubiquiti publishes no page for that SKU on any surface that has ever carried it: not in thetechspecscloud-gateway grid (sixteen cards,udwamong them,udw-prooccurring zero times in ~610 KB), not in the US/EU/UK storefronts, no FCC grant underSWX, no archived capture. The only published Dream Wall is the 420 W UDW, and copying its panel onto a "Pro" is the family-sibling error this catalogue has corrected three times. Unblock: Ubiquiti listing the Pro, or its quick-start guide printing a port layout — neither exists to read.The defect this pass found.
US-24-250W(250 W budget) andES-24-500W(budgetUnknown) shipped nopoeOuton any copper port, soderivePortHardware()(engine/media.js) filled the silence with the 802.3af default of 15.4 W on switches Ubiquiti rates at 34 W and 34.2 W PoE+.ES-24-500Walso carried noconnector, no speed ladder and no RJ45 serial console (26 jacks for 27 physical).ES-24-250Wcarried the opposite silence —poeOut: true, which the faceplate'snum()refuses andpoeDraw()adds as 1 W.Sources (all Ubiquiti, read 2026-11-21):
https://techspecs.ui.com/unifi/switching/us-24-250w(200, 638,959 B) —PoE Ports PoE+ 24,Max. PoE Wattage per Port by PSE PoE 17W / PoE+ 34W,Total PoE Availability 250W, ladder(1G/100M/10M);https://techspecs.ui.com/uisp/wired/es-24-500w(200, 582,269 B) —(24) 10/100/1000 Mbps RJ45,(1) RJ45 serial port,Max. PoE+ wattage per port by PSE 34.2W,Max. passive PoE wattage per port 17W, and noTotal PoE availablerow;https://dl.ui.com/qsg/ES-24-250W_ES-24-500W/ES-24-250W_ES-24-500W_EN.html(200, 22,805 B) — same ceilings plus "PoE settings for ports 1-24 are set to PoE+ auto by default".Not invented:
ES-24-500WkeepsbudgetW: null/budgetUnknown: true. Its 500 W is the PSU rating and the whole-box ceiling including PoE, soDevice.poeBudgetSourceremains'unknown'and the allocator is told nothing rather than 500 W.Left for the next pass:
es-48-500wandes-48-750wstill carrypoeOut: trueon their copper ports — same bare-direction shape, no numeric ceiling.2026-11-21 09:2x UTC — the Pro is unchanged; this increment fixed the two 48-port EdgeSwitch PoE chassis a Dream Wall lab would put underneath it — every socket on them was billing 1 W. PR #2400 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2400-> 0 at risk).Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /; followed, it lands on the techspecs home, 609,911 B,udw-prooccurring zero times);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared.The defect.
ES-48-500WandES-48-750WshippedpoeOut: trueon all 48 copper ports — the bare direction bitengine/media.jspoeDraw()bills as 1 W and the faceplate'snum()prints as nothing — on chassis Ubiquiti rates at 34.2 W per port by PSE. A 30 W 802.3at AP was refused power on all 48 ports of both.Three vendor surfaces, all read this pass:
https://techspecs.ui.com/uisp/wired/es-48-500w(48) GbE RJ45 / (2) 1/10G SFP+ / (2) 1G SFP;(48) PoE/PoE+ 2-pair / (48) 24V DC passive 2-pair;Max. PoE wattage per port by PSE PoE+: 34.2W / Passive PoE: 17W;Total PoE available 500Whttps://techspecs.ui.com/uisp/wired/es-48-750w(48) 10/100/1000 Mbps RJ45;34.2W/17Wper port;internal, 750W;Max. power consumption Includes PoE output: 750W / Excludes: 64W; no total-PoE rowhttps://dl.ui.com/qsg/ES-48-500W_ES-48-750W/ES-48-500W_ES-48-750W_EN.htmlModel: ES-48-500W, ES-48-750W;RJ45 (Ports 1 - 48) ... 10/100/1000 Ethernet connections;34.2W/17W;PoE settings for ports 1-48 are set to PoE+ auto by default, so 802.3af/at devices ... automatically receive PoEWhat changed. All 48 sockets on both now declare
poeOut: 34.2withpoeOutClass: "PoE+"(the shipped PoE+ auto state — not the 802.3af default the engine had been inventing), and both declare802.3afbeside802.3at.ES-48-500Walso gains the 10M rung: its tech-spec row abbreviates the ladder toGbE, while the guide naming both models prints10/100/1000for ports 1-48. The 17 W 24 V passive ceiling is on the same jacks, not additive, so it stays innotes.Not invented.
ES-48-750WkeepsbudgetW: null/budgetUnknown: true— 750 W is the PSU and whole-box ceiling, and there is no vendor allocation row, so the allocator is told nothing rather than 750 W from the model name.ES-48-500Wkeeps the published 500 W (poeBudgetSource: 'research').Gates. syntax-check 523 files OK;
audit-port-types0 contradicting ports;audit-devices2,352 models / 0 uncablable / 0 hard defects;audit-poe-budget0 name-inferred budgets, 0 budget-without-PSE;hardware-invariants26/26; newtest/ubiquiti-48-poe-per-port-watts.test.js41 checks; all 32*poe*/faceplate suites green; registry doc regenerated, no drift.Left for the next pass: the UniFi-line siblings
us-48-500wandus-48-750wstill carrypoeOut: trueon all 48 copper ports, andus-48-750wadditionally carriesbudgetW: 750— which is the PSU rating on the EdgeSwitch nameplate, so it needs the sameTotal PoE-row test before it can stay.Blocker, unchanged. No Ubiquiti artefact names
UDW-PRO: not the sixteen-card techspecs gateway grid, not the storefronts, no FCC grant underSWX, no archived capture. Unblock: Ubiquiti listing the Pro, or its quick-start printing a port layout.| includehas nineteen answers #24012026-11-21 09:5x UTC — the Pro is unchanged; this increment fixed the one published Dream Wall's whole PoE panel, which was billing 1 W a socket. PR #2404 (
Refs #130only;scripts/check-closing-keywords.js --pr 2404-> 0 at risk).Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404, 1 byte. Nothing has appeared.The defect.
devices/ubiquiti/udw.jsoncarriedpoeOut: trueon all twelve powered sockets — the bare direction bit.Device.poeDraw()(engine/device.js) adds that field into the watt total, sotrueis 1 W;pseDraw()(engine/validation.js) sums the same field against the 420 W budget, so the chassis could never show a load; the faceplate'snum()refused the boolean and printed noPoE outfigure. Two 25.5 W U7-Pros on eth0/eth4 madepoeDraw()answer 2 W.Both Ubiquiti surfaces print the per-class PSE ceiling:
Max. PoE Wattage per Port by PSE PoE: 15.4W / PoE+: 30W / PoE++: 60WbesidePoE Budget 420W(https://techspecs.ui.com/unifi/cloud-gateways/udw, 200, 704,702 B, read 2026-11-21; same rows in https://dl.ui.com/ds/udw_ds.pdf, 200, 544,909 B, 3 pp). The twelve sockets now declare 60 / 30 / 15.4 W for the classes they already carried. The class-to-socket ordering is untouched — neither surface numbers which four sockets are which, so only the figure changed. Panel sum 421.6 W against the 420 W budget is the vendor's own arithmetic, stated in the notes, not reconciled.Gates: syntax-check 524 files OK; audit-port-types 0 gated; import-devices --dry-run clean; hardware-invariants 26/26; full suite 444 suites / 14,975 assertions / 0 failed; regen-registry-doc current. New
test/ubiquiti-dream-wall-poe.test.js, 16 assertions.Blocker, unchanged and precise. What the request needs is the UDW-PRO census: RJ45 and SFP+ counts and rates, which sockets default to WAN, the PoE class split and budget, and the PSU configuration. No Ubiquiti surface publishes any of it:
techspecshas noudw-procard (sixteen cloud-gateway cards,udwamong them,udw-prozero times in ~610 KB), the US/EU/UK storefronts 404, there is no FCC grant underSWX, and no archived capture exists. Copying the 420 W UDW's panel onto a "Pro" is the family-sibling error this catalogue has corrected three times. What would unblock it: Ubiquiti listing the SKU, or a quick-start guide printing its port layout — neither exists to read.2026-11-21 10:2x UTC — the Pro is unchanged; this increment fixed five cloud-gateway PoE panels that billed every socket at 1 W. PR #2407 (
Refs #130only, no closing keyword;scripts/check-closing-keywords.js --pr 2407-> 0 at risk).Re-measured this minute:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404, 1 byte. Nothing has appeared.The defect.
UCG-Industrial,UDM-SE,UDR,UDR7andUDR-5G-MaxcarriedpoeOut: true— the bare direction bit, whichDevice.poeDraw()(engine/device.js) adds as 1 W andpseDraw()sums against the budget. So the 270 W budget on UCG-Industrial could not bind: a 90 W 802.3bt device on eth0 was taken as a 1 W load, andshow power inlinehad no figure to print. Each socket now carries the vendor's own ceiling for the class it already had, from the tables read today:2.5 GbE RJ45 = 4 (2 PoE+++, 2 PoE+),10 GbE RJ45 = 1 (PoE+++)PoE+ 30W/PoE+++ 90Wucg-industrial, 200, 699,443 B(6) PoE+(2) PoE+PoE 15.4W/PoE+ 30Wdl.ui.com/ds/udm_se_ds.pdf, 200, 358,669 B, text layer1 GbE RJ45 = 5 (2 PoE)PoE 15.4Wudr, 200, 685,837 B2.5 GbE RJ45 = 4 (1 PoE)PoE 15.4Wudr7, 200, 694,590 B2.5 GbE RJ45 = 4 (1 PoE)PoE 15.4Wudr-5g-max, 200, 876,426 BThe UCG-Industrial panel now sums to 330 W (3 x 90 + 2 x 30) against its 270 W budget, so the budget is what spends — the same shape the UDW row records. Gate:
test/ubiquiti-gateway-pse-panel.test.js(101 assertions, includingpoeDraw()after cabling a powered device to each row's first PSE socket);--filter=ubiquiti7 suites / 591 assertions and--filter=poe29 suites / 919 assertions, both 0 failed.Blocker, unchanged since #10488. The request asks for a
UDW-PROport/PoE census and Ubiquiti publishes no page for that SKU on any surface that has ever carried it. Two rows of the same bare-bit class stay untouched in this PR because their pages 307:/unifi/cloud-gateways/umr(1 byte) and/umr-industrial(39 bytes), both to/. Issue 130 stays open.2026-11-21 10:5x UTC — blocker unchanged; this increment fixed the last two bare PoE bits in the same vendor family. PR #2411 (
Refs #130only;check-closing-keywords.js --pr 2411reports 0 references, 0 at risk).Probed again this run:
/unifi/cloud-gateways/udw-pro-> 307 to/, 1 byte;store.ui.com/us/en/products/udw-pro-> 404. Nothing new to read.The defect fixed.
UMR(rj45-2) andUMR-Industrial(eth1) carriedpoeOut: truebeside a 10 W passthrough budget — the bare direction bit, whichpoeDraw()reads as 1 W andpseDraw()sums against that budget, so the passthrough could never bind. Both sockets now declare 10 W, from Ubiquiti's own row "(1) PoE output (Max. 10W, requires PoE+ switch)" ontechspecs.ui.com/unifi/integrations/umr-us(200, 708,698 B) and.../umr-industrial-us(200, 693,659 B). The class stays PoE+ (the upstream requirement); 10 W is a passthrough cap, stated in both notes.Why an earlier pass skipped them. It probed
/unifi/cloud-gateways/umrand/umr-industrial, which answer 307 to/, and read that as "no vendor page". The live pages sit under/unifi/integrations/with the-ussuffix. Recorded in both specs so it is not re-walked.Missing fields for this request, unchanged: UDW-PRO RJ45 and SFP+ counts and rates, which sockets default to WAN, the PoE class split and total budget, and the PSU configuration. What would unblock: a Ubiquiti-hosted URL for the Pro SKU (tech-spec, store, datasheet, quick-start) or a note that the UDW was meant. Issue stays open.
2026-11-21 11:2x UTC — the Pro is unchanged; this increment made the whole PoE-injector class answer its own budget. PR #2413 (
Refs #130only;scripts/check-closing-keywords.js --pr 2413-> 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B body is the store 404. Nothing has appeared since the last pass.The defect fixed. All ten catalogue entries carrying
poe-injectorsourced PoE on ports that already named the vendor's per-port wattage, and not one declared a device total.Devicefell through to the model-name parser (parsePoeBudget('POE60U-1BT-2-R')finds nothing),computePoe()skipped the box atif (!dev.poeBudget) continue;, andshow power inlineprinted budget not modelled ... the ports are reported, the power they could supply is not — the same field-level failure as the Dream Wall in this issue. Now stated:POE60U-1BT-2-R60 W,POE90U-1BT-N6-R90 W,PD-9001GR/AT/AC30 W,PD-9501GCO60 W,PD-9004G/AC120 W (4 x the sheet's "up to 30W per port for all ports"),NetWay8G240 W ("Total power: NetWay8G - 240W"),TL-PoE150S15.4 W,POE-24-24WandPOE-48-24W24 W each.mikrotik/RBGPOEis markedbudgetUnknowninstead: a bare pass-through injector's ceiling moves with the PSU, and MikroTik prints a 2 A current limit, not a wattage.test/poe-injector-budget.test.jsnow gates the class (70 assertions);audit-poe-budget.jssilent cohort 32 -> 22. Full suite: 447 suites, 15,195 assertions, 0 failed.Blocker, unchanged. The request asks for a
UDW-PROport/PoE census, and Ubiquiti publishes no such SKU on any surface that has ever carried one: not in thetechspecscloud-gateway grid (udw-prooccurring zero times in ~610 KB), not in the US/EU/UK storefronts, no FCC grant underSWX, no archived capture. The only published Dream Wall is the 420 W UDW, and copying its seventeen copper ports onto a Pro would be the family-sibling error this repo has already corrected three times. Sending the requester to the base UDW (devices/ubiquiti/udw.json, now carrying both its 420 W budget and the vendor's per-class ceilings) stays the honest substitute.2026-11-21 11:5x UTC — the Pro is unchanged; this increment fixed the three power configurations of the switch a lab substitutes for its LAN side. PR #2417 (
Refs #130only;scripts/check-closing-keywords.js --pr 2417-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 200, 609,911 B, the techspecs home page (the known not-found);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B. Nothing has appeared.The defect fixed.
USW-Ultra(42 W),USW-Ultra-60W(52 W) andUSW-Ultra-210W(202 W) carriedpoeOut: trueon their seven PoE+ sockets — the bare direction bit, whichpoeDraw()adds as 1 W andpseDraw()sums against the budget. So the 42 W budget could not bind: two 25.5 W access points on eth0/eth1 were both accepted (2 W of 42 W). Each page printsPoE Ports PoE+ 7andMax. PoE Wattage per Port by PSE PoE+ 30Wnext toMax. PoE Output Up to PoE+; each socket now declares 30 W,eth7stays the PoE++ input (poeOut: 0). The second access point on the 42 W model is now refused with2 powered ports draw 60 W of a 42 W budget.Still missing for UDW-PRO, unchanged: the entire census — LAN RJ45 count, 2.5G/10G split, which SFP+ are LAN/WAN, the PoE class mix and total budget. What would unblock: any Ubiquiti-hosted page, datasheet, QSG or FCC grant for the Pro, or a note that you meant the UDW (420W), already modelled at
devices/ubiquiti/udw.jsonwith 17x GbE RJ45 (4 PoE / 4 PoE+ / 4 PoE++), 4x 10G SFP+, 1x 2.5GbE WAN and a 420 W budget.Correction to the paragraph above: the UDW has 2x 10G SFP+ (the datasheet's
(1) LAN: 10G SFP++(1) WAN: 10G SFP+), not 4.devices/ubiquiti/udw.jsoncensus: 17x 1G RJ45 LAN, 1x 2.5G RJ45 WAN, 2x 10G SFP+, plus the 2.4/5 GHz radios. The rest of the comment stands.Noting the adjacent question this raises, for a later pass rather than this one: those two SFP+ cages carry no
roleinudw.json, while the datasheet splits them one LAN and one WAN. That is the same shape as the defect #2362 fixed on the base UDM (a role-less socket makesownsIpOn's separation a no-op), and it needs the vendor's own numbering of which cage is which before it can be written - the panel order, not an assumption.2026-11-21 12:2x UTC — the Pro is unchanged; this increment fixed the same WAN/LAN separation defect on the Enterprise Firewall. PR #2419 (
Refs #130only;scripts/check-closing-keywords.js --pr 2419-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared.The defect.
devices/ubiquiti/efg.jsonshipped all six sockets with norole, soownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role) never fired. Measured before the change: with192.168.1.1/24oneth1,ownsIpOn(eth0, '192.168.1.1')returned true — the LAN gateway answered on the 2.5G WAN socket, and a host cabled there inside the LAN prefix got an ICMP reply.The vendor map.
https://static.ui.com/fingerprint/ui/public.json(HTTP 200, 832,585 B,sku= EFG) givesports= eth0 WAN, eth1 LAN, eth2 LAN, eth3 LAN, eth4 WAN2, eth5 LAN withplus[3,4] andsfp28[5,6] andlinkNegotiationportIdx 1-6; the tech-spec page printsDefault WAN Ports (1) 25G SFP28 (1) 2.5 GbE RJ45over2.5 GbE RJ45 2 / 10G SFP+ 2 / 25G SFP28 2.The change. eth0 ->
role: "wan"; eth1 and both 10G SFP+ cages ->role: "lan"; the SFP28 pair carriesdualRoleand norole, because the row's sfp3/sfp4 are not vendor-issued names and one of the two is WAN2 — assigning which would be an ordering guess. Measured after:ownsIpOn(eth0, LAN address)false,ownsIpOn(sfp1, LAN address)true, eth0 still answers its own address. Gates: syntax-check 532 OK; audit-port-types 0 contradictions; audit-devices 0 hard defects; hardware invariants 26 passed; role test 218 passed.2026-11-21 12:5x UTC — the Pro is unchanged; this increment fixed the two Gen1 48-port UniFi PoEs a Dream Wall lab puts underneath it. PR #2425 (
Refs #130only;scripts/check-closing-keywords.js --pr 2425-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared.The defect.
US-48-500WandUS-48-750WshippedpoeOut: trueon all 48 copper ports — the bare direction bitpoeDraw()sums as 1 W and the faceplate'snum()prints as nothing — on chassis the vendor rates at 34.2 W per socket by PSE. Measured before: twenty 25.5 W AP-515s cabled to the 500 W model reported 20 W of draw of a 500 W budget, sopseDraw()could never raiseE_POE_BUDGET; the 750 W model reported 20 W of 750 W. Also 50 jacks modelled for 52 physical: the two 10G SFP+ cages were absent.The vendor's page.
https://dl.ui.com/qsg/US-48-500W_US-48-750W/US-48-500W_US-48-750W_EN.html(HTTP 200, 19,990 B, read 2026-11-21) names both models (Model: US-48-500W, US-48-750W) and printsPOE+ IEEE 802.3af/at (Pins 1, 2+; 3, 6-),Max. PoE+ Wattage per Port by PSE 34.2W,Voltage Range 802.3at Mode 50-57V,(48) 10/100/1000 Mbps RJ45 Ethernet Ports,(2) 1/10 Gbps SFP+ Ethernet Ports,(2) 1 Gbps SFP Ethernet Ports,(1) RJ45 Serial Port Out-of-Band. The tech-spec pages (.../unifi/switching/us-48-500w, 200, 626,072 B;.../us-48-750w, 200, 619,881 B) independently print10G SFP+ 2 (10G/1G),Total PoE Availability 500W/750W.What changed. All 48 sockets now declare 34.2 W (
poeOutClass: "PoE+"),802.3afjoins802.3at, thesfp+1/sfp+2cages (10G/1G) and the RJ45 serial console are added (53 jacks for 53 physical), and the description no longer omits the SFP+ pair. Measured after:US-48-500Waccepts 14 AP-515s and refuses the 15th —15 powered ports draw 513 W of a 500 W budget;US-48-750Waccepts 21 and refuses the 22nd —752.4 W of a 750 W budget.Not invented. Budgets stay the published 500 W / 750 W from the
Total PoE Availabilityrows. The QSG's PoE LED legend names24V Passive PoEon ports 1-48, but neither surface prints a passive per-port wattage, sopassive-poestays undeclared and no ceiling was guessed.Gates. syntax-check 532 OK; audit-port-types 0 contradictions; audit-devices 2,352 models / 0 uncablable / 0 hard defects; audit-poe-budget 0 name-inferred budgets; hardware-invariants 26/26; new
test/ubiquiti-us-48-poe-per-port-watts.test.js48 checks; full runner 453 suites / 15,391 assertions, 0 failed;docs/CONNECTORS.mdregenerated.Left for the next pass.
US-48(non-PoE sibling, same chassis) also models only the two 1G SFP cages though its own tech-spec page prints10G SFP+ 2— it needs the samesfp+pair and its QSG's console row; andudw.json's two SFP+ cages still carry norole.Blocker, unchanged. No Ubiquiti artefact names
UDW-PRO: not the sixteen-card techspecs gateway grid, not the US/EU/UK storefronts, no FCC grant underSWX, no archived capture. What would unblock: any Ubiquiti-hosted page, datasheet, QSG or FCC grant for the Pro, or a note that the requester meant the UDW (420W), already modelled atdevices/ubiquiti/udw.json(17x 1G RJ45 LAN, 1x 2.5GbE WAN, 2x 10G SFP+, 420 W budget).2026-11-21 13:2x UTC — the Pro is unchanged; this increment fixed a PoE port on the compact RedCap router a Dream Wall lab puts on the far side of its WAN. PR #2428 (
Refs #130only;scripts/check-closing-keywords.js --pr 2428-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404. Nothing has appeared.The defect.
devices/teltonika/rut276.jsondeclared its one LAN socket as a PSE —poeOut: true,poeOutClass: "PoE+",poe-psein the capabilities — and declared nopoeInat all. Teltonika's datasheet says the opposite. RUT276 datasheet v1.05 (2026-07-24, p.7,https://download.kamami.pl/p1207999-Datasheet_RUT276_1.05.pdf, HTTP 200, 4,182,657 B, 14 pp) reads under the heading POE IN:PoE IN ports 1 x PoE In/PoE standards Active PoE input 802.3af Class 0 (12.94 W) on LAN port, plus passive PoE 16-57 VDC on the same socket. There is no POE OUT section, no per-port PSE wattage and no budget in either revision. (v1.04,https://cdn.bueromarkt-ag.de/downloads/produktdatenblaetter/rut276000000.pdf, p.8, prints that value row asPoE OUT ports— a template leftover v1.05 corrects toPoE IN ports; that label is where the reading came from.)Measured before:
poeDraw()added the bare bit as 1 W,show power inlineansweredbudget not modelled on RUT276, and a PoE switch cabled tolan1printedport1 auto off - the far end is not a powered device— the router could not be powered by the cable that powers it. After: the switch printsport1 auto on 12.9 RUT276,Used:12.9(w), and the router answers% No PoE on RUT276: no port on this device can supply power.The same file also gained the roles its datasheet names on p.2 (
WAN 1 x WAN port/LAN 1 x LAN port): with neither declared,ownsIpOn()'s separation never fired and an address held onlan1was answered fromwan1— the defect #2385 and #2419 fixed on the UXG and EFG gateways.Gates: syntax-check 535 files OK; audit-port-types 0 gated; audit-poe-budget silent PSEs 20 -> 19; new
test/teltonika-rut276-poe.test.js15 assertions; full suite 455 suites / 15,430 assertions, 0 failed. Issue 130 stays open: no Ubiquiti source for UDW-PRO exists.2026-11-21 13:5x UTC — the Pro is unchanged; this increment fixed the NanoSwitch a Dream Wall lab puts at the far end of a long copper run. PR #2431 (
Refs #130only;scripts/check-closing-keywords.js --pr 2431-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: /);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B;https://dl.ui.com/ds/udw_pro_ds.pdf-> 302 ->https://techspecs.ui.com/. Nothing has appeared.One thread closed as a dead end, so nobody re-walks it. Comment #187 left the UDW's two SFP+ cages role-less pending "the vendor's own numbering of which cage is which". The controller database does carry one (
https://static.ui.com/fingerprint/ui/public.json,sku=UDW, 832,585 B, read 2026-11-21):networkGroupsputseth18in WAN andeth19in WAN2,linkNegotiationrateseth18at 2500 andeth19at 10000, andports.plusis[17, 20]. That resolves which role exists - one LAN cage, one WAN cage - but not which of oursfp1/sfp2is which: the vendor's names (eth16,eth19) are not our names, and itsdiagramrow still prints17in the copper row whileports.pluscounts 17 as a cage. This is the EFG shape filed in PR #2419: dual-role, role-less, because a role guessed onto the wrong cage is the bug a lab finds with a cable. Recorded, not re-opened.The defect fixed.
devices/ubiquiti/n-sw.jsonshipped three sockets on the barepoeOut: truebit and nopoe.budgetW, sopoeDraw()billed 1 W per socket andpseDraw()had no budget to sum against. Measured before: three 24 W R2AC radios cabled to eth0/eth1/eth2 were all accepted,poeDraw()answered 3 W for 72 W of load, andshow power inlinesaid the budget was not modelled. Ubiquiti's page (https://techspecs.ui.com/uisp/wired/n-sw, 200, 575,565 B) prints(4) GbE RJ45 ports [(1) PoE-in, (3) PoE passthrough],Passive PoE Max. Wattage per port ... 1A per port (24W)andTotal passive PoE Max. Wattaget ... 1A for 3 ports (30W). Each passthrough socket now carries 24 W in thepassiveclass (it had claimed 802.3af, whichPower method: Passive 24Vcontradicts), the budget is the 30 W aggregate, and eth3 is the PoE-in socket - the spec'spoe-pdcapability had no socket that accepted power at all. After:Available:30.0(w) Used:24.0(w) Remaining:6.0(w), and the second radio is refusedE_POE_BUDGET: 2 powered ports draw 48 W of a 30 W budget. Gates: syntax-check 536 OK; audit-port-types 0 gated; audit-poe-budget silent PSEs 19 -> 18; hardware-invariants 26 passed; catalogue-hygiene 25 passed.2026-11-21 14:2x UTC — the Pro is unchanged; this increment went to the catalogue's remaining silent PoE switches, where the EdgeSwitch 16XP had half its sockets missing. PR #2433 (
Refs #130only;scripts/check-closing-keywords.js --pr 2433-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 B (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B. Nothing has appeared since 13:5x.Why this device. With the only open
device-requestpermanently blocked on a SKU Ubiquiti does not sell, the pass took the next item onscripts/audit-poe-budget.js's silent list (19 devices that source PoE and cannot say how much). First of them: the EdgeSwitch XP line.The defect.
devices/ubiquiti/es-16xp.jsonmodelled eight data ports and one management port. The chassis is two EdgeSwitch 8XP systems — Ubiquiti's datasheet,https://dl.ui.com/datasheets/edgemax/EdgeSwitch_XP_DS.pdf(200,application/pdf, 3,915,117 B, 7 pp, text layer), p.2: "dual EdgeSwitch 8XP systems in a rack-mountable, 1U form factor with 300 watts of power supporting up to 16 devices"; p.4: "16 Gigabit PoE Ports"; p.7: "Hardware Configuration (2) EdgeSwitch 8XPs". The per-port rows are the ES-8XP page (p.6), which the tech-spec page heads with "* Specifications apply to each 8-Port EdgeSwitch ES-8XP unit". The old note read that asterisk as a chassis fact and recorded the shortfall as a trap — the model name was right and half the switch was absent.Measured before: 9 sockets (8 data at a bare
poeOut: true->poeDraw()1 W each), 9 PSE ports becausemedia.jsinfers 15.4 W on copper ports of apoe-psedevice with no declared figure — the management socket included — andpoeBudget 0from the name parser, i.e. unbounded. After: 18 sockets (16 data +mgmt0/mgmt1withpoeOut: false, per p.6 "PoE Configurable Per Port: Management Port N/A"), 16 PSEs at 11.5 W (the vendor's 24 V figure), 184 W at a full 24 V fill againstpoe.budgetW: 300— the datasheet's chassis figure, noted as an input envelope because Ubiquiti prints no PoE-budget row and does not say whether chassis draw sits inside the 300 W.Still silent in this family:
devices/ubiquiti/es-5xp.json(5 PSEs, 11.5 W a port, 24 V 2.5 A adapter, no total published) — the next candidate, not touched here.2026-11-21 14:5x UTC — the Pro is unchanged; this increment fixed the last silent PoE box in the EdgeSwitch XP line. PR #2438 (
Refs #130only;scripts/check-closing-keywords.js --pr 2438-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 B (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B; the gateway index (.../cloud-gateways, 200, 610,412 B, md5cf2013856f71affe0ce501b99d5f91d1) still containsudw-prozero times. Nothing has appeared since 13:5x.The defect.
devices/ubiquiti/es-5xp.jsonadvertised five PoE ports and no watts: every data port carried the barepoeOut: truebit (poeDraw()bills 1 W, the faceplate prints no figure) and there was nopoeblock, soparsePoeBudget('ES-5XP')found no number andshow power inlineanswered "budget not modelled" over six rows ofnot measured. Worse, the 10/100 management socket — on apoe-psedevice with no declared figure — was inferred bymedia.jsas a 15.4 W 802.3af PSE: six power ports on a five-port PoE switch, speaking a 48 V standard this box does not speak.The vendor's page.
https://dl.ui.com/datasheets/edgemax/EdgeSwitch_XP_DS.pdf(200,application/pdf, 3,915,117 B, 7 pp, text layer), p.5, the ES-5XP page:Data Ports (5) 10/100/1000 Ethernet Ports,Management Port (1) 10/100 Ethernet Port,PoE Out Voltage Range 22-24VDC,Max. PoE Wattage Per Data Port 11.5 W,PoE Method Passive,PoE Configurable Per Port: Management Port N/A, Data Ports Off/24V,Power Input 24VDC, 2.5A Power Adapter (Included),Max. Power Consumption 60 W. The tech-spec page (https://techspecs.ui.com/uisp/wired/es-5xp, 200, 574,944 B) prints the same rows and no total PoE row.What changed. Five data ports ->
poeOut: 11.5, classpassive;mgmt->poeOut: false(the datasheet's "Management Port N/A");poe.budgetW: 60cited to the datasheet, recorded as the adapter envelope it is — Ubiquiti prints no "PoE budget" row and, unlike its EdgeRouter pages ("excluding PoE output"), does not say whether the box's draw sits inside the 60 W, so the note states the margin (5 x 11.5 = 57.5 W leaves 2.5 W) rather than pretending to a measured budget. Same readinges-16xp.jsontakes of that chassis's 300 W. Measured after: an 8.5 W airCube on eth3 ->Available:60.0(w) Used:8.5(w) Remaining:51.5(w);show power inline mgmt-> "cannot supply power (it is not a PSE port)".Gates. syntax-check 538 OK; audit-port-types 0 gated; audit-devices 2,352 models / 0 uncablable / 0 hard defects; audit-poe-budget silent PSEs 17 -> 16; hardware-invariants 26/26; catalogue-hygiene 25/25; new
test/ubiquiti-es-5xp-poe.test.js23 checks; full runner 458 suites / 15,524 assertions, 0 failed.Left for the next pass.
ES-8XP— p.6 of the same datasheet, 8 data ports at 11.5 W (24 V) / 23 W (48 V) on a 150 W supply — has nodevices/ubiquiti/es-8xp.jsonat all;ES-16XPmodels its 16 sockets as one chassis, so the 8XP is the only member of the three-model XP sheet missing from the catalogue. That is the next increment, not this one.Blocker, unchanged. No Ubiquiti artefact names
UDW-PRO: not the sixteen-card techspecs gateway grid, not the US/EU/UK storefronts (nine storefronts enumerated), no FCC grant underSWX, no firmware platform code, no archived capture. What would unblock: any Ubiquiti-hosted page, datasheet, QSG or FCC grant for the Pro, or a note that the requester meant the UDW (420W), already modelled atdevices/ubiquiti/udw.json(17x 1G RJ45 LAN, 1x 2.5GbE WAN, 2x 10G SFP+, 420 W budget).2026-11-21 15:2x UTC — the Pro is unchanged; this increment gave the two Omada wall plates the passthrough wattage they were missing. PR #2441 (
Refs #130only;scripts/check-closing-keywords.js --pr 2441-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B; the gateway index (.../cloud-gateways) -> 200, 610,412 B,udw-prostill present zero times. Nothing has appeared.Why this device. With the only open
device-requeststill blocked on a SKU Ubiquiti does not sell, the pass took the next items onscripts/audit-poe-budget.js's silent list — 16 devices that source PoE and cannot say how much — and found a pair with the same defect shape: the Omada wall-plate APs.The defect.
devices/tp-link/eap235-wall.jsonandeap615-wall.jsoneach advertise a PoE passthrough port with the barepoeOut: truebit and no watts.poeDraw()bills 1 W for it, andshow power inlineanswered "budget not modelled" over a row ofnot measured— the same "a device that is present and a number that is not" that started this audit.The vendor's page states both figures, and both are conditional.
https://www.tp-link.com/us/business-networking/omada-wifi-wall-plate/eap235-wall/v1.20/(200, 188,991 B, read today): "PoE Out (requires 802.3at PoE input and the maximum output is 13 W)".https://www.tp-link.com/us/business-networking/omada-sdn-access-point/eap615-wall/v1/(200, 230,762 B): "The maximum power output for POE pass-through is 13 W (EU version) or 12 W (US version), based on laboratory testing." So 13 W for the EAP235-Wall and 12 W for the EAP615-Wall (the /us/ page, so the US figure).One trap recorded. The EAP235-Wall page also prints
9.8W (PoE Out Not Included) / 24.4W (PoE Out Included). 24.4 - 9.8 = 14.6 W, but only 13 W can leave the jack; the remaining 1.6 W is the converter's loss. Subtracting consumption rows would have overstated the PSE by 1.6 W — the same error class as reading a PSU rating as a PoE ceiling.The sibling that stays silent.
EAP225-Wallprints only9W or 25.5W including PoE Outand no maximum output, so the only available figure is an upper bound that includes the same loss. It is left on the silent list rather than given a subtracted number.What the schema still cannot say. Both figures exist only under an 802.3at input; on an 802.3af uplink the AP runs (9.8 W / 11.5 W) and the passthrough jack is dead.
poe.budgetWis unconditional, so the engine will allocate 13 W / 12 W on eth3 even when an af port feeds the AP. Recorded in bothpoe.notefields and in the descriptions; it needs a schema field before the engine can refuse it.2026-11-21 15:5x UTC — the Pro is unchanged; this increment gave the third Omada wall plate its passthrough wattage. PR #2445 (
Refs #130only;scripts/check-closing-keywords.js --pr 2445-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B; the gateway index (.../cloud-gateways) -> 200, 610,412 B,udw-prostill present zero times. Nothing has appeared.Why this device. With the only open
device-requeststill blocked on a SKU Ubiquiti does not sell, the pass continued downscripts/audit-poe-budget.js's silent list (13 left) into the wall-plate family that #2441 opened:EAP225-Wallcarried the same barepoeOut: trueon its passthrough jack, sopoeDraw()billed it 1 W andshow power inlineanswered "budget not modelled".The defect and the figure.
eth3is nowpoeOut: 13/PoE+withpoe: { budgetW: 13, standard: "802.3at" }. Source:https://www.omadanetworks.com/uk/business-networking/omada-wifi-wall-plate/eap225-wall/(200, 153,844 B) — "Downlink: 3x 10/100 Mbps Ethernet Ports (One port supports PoE OUT. The PoE OUT feature requires 802.3at PoE+ input and the maximum output is 13 W.)", "Max. Power Consumption 9 watts /25.5 watts (PoE Out Included)". The US v2 page insourceUrl(200, 224,096 B) confirms the port census and rates but prints no output wattage. 25.5 - 9 = 16.5 W > 13 W, so that row is the class-4 ceiling, not a sum: the stated output is modelled. The page marks the model "Product EOL : Replace with EAP235- Wall", whose spec already carries the same 13 W.Blocker here, unchanged and precise: the whole UDW-PRO census — RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. No Pro surface was re-walked; the ten routes this thread has closed still stand. Unblock: any Ubiquiti-hosted artefact naming
UDW-PRO, or a hand-written disposition. Otherwise next run takes the next silent PoE device.2026-11-21 16:5x UTC — the Pro is unchanged; this increment fixed the two Teltonika OTD outdoor routers, whose PoE-out was a boolean and whose PoE-in was the 802.3af class ceiling. PR #2453 (
Refs #130only;scripts/check-closing-keywords.js --pr 2453-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 byte (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B. Nothing has appeared.Why this device. With the only open
device-requestpermanently blocked on a SKU Ubiquiti does not sell, the pass continued downscripts/audit-poe-budget.js's silent list (12 left) and found a family pair with a worse shape than silence: the number that was there was wrong.The defect.
devices/teltonika/otd140.jsonandotd144.jsonboth declaredpoeOut: truewithpoeOutClass: "PoE+"— 802.3at — on an outlet Teltonika rates 802.3af, sopoeDraw()billed 1 W and the class over-claimed the standard. Both also declaredpoeIn: 12.95, the 802.3af class ceiling, on an inlet the vendor rates 802.3af/at, max 21 W.Now.
eth1sinks 21 W;eth2sources 15 W classed 802.3af; apoeblock carries the 15 W with the flyer/datasheet quotes. 21 W in, 6 W of router, 15 W out — the vendor's own three rows reconcile. Silent list 12 -> 10.2026-11-21 17:5x UTC - the Pro is unchanged; this increment fixed the eight-port PoE NVR a Dream Wall lab records to, where the ports overstated the vendor and the aggregate was silent. PR #2459 (
Refs #130only;scripts/check-closing-keywords.js --pr 2459-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 B (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B;https://dl.ui.com/ds/udw_pro_ds.pdf-> 302 -> https://techspecs.ui.com/. Nothing has appeared.The defect.
devices/reolink/rln8-410.jsoncarried eightpoeOut: 25.5ports - the 802.3at class-4 ceiling - on a box whose own spec sheet saysMax. Power Per Port 25W, while the description in the same file already said 25 W. Nopoeblock at all, so eight PSEs reachedscripts/audit-poe-budget.jsas silent.What Reolink does publish. The N7MB01 sheet has two PoE rows only (
Max. Power Per Port 25W,IEEE 802.3af/at) and aPower Supply DC 48V~53V; the V2 sheet givesDC 48V/1.875-2.5A(90-120 W) against 200 W of per-port ceiling. Two support articles confirm an aggregate exists and tie it to the supply: "The NVR has a fixed total power budget", and the alert fires "when the total PoE power approaches or exceeds the power adapter rated capacity". No watt figure is printed.Resolution. Ports now 25 W with class PoE+, and
poe.budgetUnknown: truerecords that the aggregate exists and is unpublished - not multiplied out, not read off the PSU (the ES-24-500W lesson). Audit: silent 11 -> 10, unknown 25 -> 26. Issue 130 stays open.2026-11-21 18:2x UTC — the Pro is unchanged; this increment fixed the three UA-SK starter-kit hubs, which sourced power on the wrong jack. PR #2461 (
Refs #130only;scripts/check-closing-keywords.js --pr 2461-> 0 references, 0 at risk).Re-measured this run:
https://techspecs.ui.com/unifi/cloud-gateways/udw-pro-> 307, 1 B (Location: https://techspecs.ui.com/);https://store.ui.com/us/en/products/udw-pro-> 404, 213,322 B. Nothing has appeared.Why this device. With the only open
device-requestpermanently blocked on a SKU Ubiquiti does not sell, the pass went back toscripts/audit-poe-budget.js(10 silent) and found a family with a worse shape than a missing number: the number was attached to the wrong port.The defect.
devices/ubiquiti/ua-sk-gate.json,ua-sk-elevator.jsonandua-g3-sk-elevator.jsoneach declaredpoeOutclass PoE++ oneth0— the jack that is fed by the switch — and left the four jacks a reader or lock is actually cabled to dry, with nopoe.budgetW. The loader fell through to the model name, found no wattage and served 0 W, so a Gate kit advertised a 60 W source on its uplink and nothing on its outputs.What Ubiquiti publishes (
https://techspecs.ui.com/unifi/door-access/ua-sk-gate200 / 726,929 B;.../ua-sk-elevator200 / 672,464 B;.../ua-g3-sk-elevator200 / 675,251 B, all read today): Gate Hub Networking Interface (5) 10/100/1000 Base-T, PoE Interface (1) PoE++ input, 50V DC, 1A; (4) PoE outputs, 50V DC, 30W per port (Max 55W aggregated), 22W without / 60W with PoE output. Elevator Hub Networking (4) + Management (1) 10/100/1000 Base-T, PoE Interface (1) PoE++ input, 50V DC, 1.2A; (4) PoE+ outputs, 50V DC, 30W per port (Max 45W aggregated), 7W without PoE output. Both censuses close to 5 RJ45 = 1 input + 4 outputs, soeth0is the PD input (50 W / 60 W) andeth1-eth4are the 30 W PSEs behindpoe.budgetW55 / 45 — the directionua-hub.json,ua-hub-gate.jsonandua-g3-sk-gate.jsonalready use.show power inlinenow answers Available:55.0(w) and 45.0(w) over four ports each. Silent list 10 -> 7.One trap recorded, not smoothed. The Gate Hub prints 55 W of output plus 22 W of draw against a 50 V x 1 A = 50 W inlet (60 W "with PoE output" in its own row), so 77 W does not fit; 55 W is kept as printed and the gap is written into
poe.noteas a vendor question. The Elevator Hub reconciles: 45 + 7 = 52 W under 60 W.Blocker, unchanged. No Ubiquiti artefact names
UDW-PRO: not the techspecs gateway grid, not the storefronts, no FCC grant underSWX, no firmware platform code. What would unblock: any Ubiquiti-hosted page, datasheet, QSG or FCC grant for the Pro, or a note that the requester meant the UDW (420W), already modelled atdevices/ubiquiti/udw.json.