Ubiquiti cloud gateways: UDM-SE's 8 PoE ports and UCG-Industrial's PoE+++ 10G port #1657

Merged
jaylouisw merged 1 commit from catalogue/1116-1155 into main 2026-11-16 12:02:05 +00:00
Owner

Catalogue correction, Ubiquiti cloud-gateway family. The open [Device]: queue is fully blocked (#760/#757/#495/#494/#130 chassis or unlocalised fields, #789-#810 Huawei chassis and LineCard-only tables, #741-#743 OceanProtect controller configurations), so this run audits the one vendor family we can settle against the vendor's own spec tables.

Two specs contradicted a vendor source, both in the same direction: the box ships with PoE hardware the spec did not model.

UDM-SE — eight power-sourcing LAN ports were modelled as plain copper

devices/ubiquiti/udm-se.json declared no poe-pse capability and no poeOut on any port, while its own description already said "8x 1GbE RJ45 LAN (2 PoE+, 6 PoE, 180W)".

Ubiquiti's datasheet, PoE interface row:

Networking interface: (8) LAN: GbE RJ45 ports
PoE interface: (6) PoE (Pair A 1, 2+; 3, 6-) · (2) PoE+ (Pair A 1, 2+; 3, 6-)
PoE budget: 180W · Max. PoE wattage per port by PSE: PoE: 15.4W, PoE+: 30W

Fix: all eight LAN ports carry poeOut, six as PoE and two as PoE+; capabilities gain poe-pse, 802.3af, 802.3at.

Modelling note, stated rather than hidden: Ubiquiti publishes the class counts, not which physical ports are which. The two PoE+ ports are modelled as Port 1–2, i.e. the higher class on the lowest-numbered ports, which is the convention the sibling udw.json already follows (eth0–3 PoE++, eth4–7 PoE+, eth8–11 PoE). No port, speed or wattage was changed.

UCG-Industrial — five PoE ports, not four

Ubiquiti's Port Layout table for techspecs.ui.com/unifi/cloud-gateways/ucg-industrial:

2.5 GbE RJ45 — 4 (2 PoE+++, 2 PoE+) (2.5G/1G/100M)
10 GbE RJ45 — 1 (PoE+++) (10G/5G/2.5G/1G/100M)
10G SFP+ — 1 (10G/1G)
PoE budget: DC input 270W / ATX power 75W · PoE+ 30W · PoE+++ 90W

The 10G RJ45 port is marked PoE+++ but eth4 carried no poeOut, so the catalogue would have hung a 90 W camera off a port it believed unpowered. Fix: eth4 gains poeOut/poeOutClass: PoE+++, and the description now names it. 802.3bt (which PoE+++ is) and 802.3at were already declared, so no capability was added or dropped.

Sources

Checked and left alone

  • UCG-Fiber publishes a 30 W PoE budget and its description claims "1 PoE+", but the Port Layout rows annotate no port as PoE and no per-class wattage is given, so there is no source for which port sources power. Left unchanged rather than guessed; worth a follow-up if Ubiquiti ever localises it.
  • Dream Wall Pro (#130) — Ubiquiti's tech-specs catalogue now enumerates 17 cloud gateways and contains no Pro entry at all, and dl.ui.com/ds/udw_pro_ds.pdf returns the site's HTML, not a PDF. Blocker stands.

Gates

  • node scripts/syntax-check.js — 348 files, all OK
  • node scripts/audit-port-types.js — no port contradicts its declared type (exit 0)
  • node scripts/audit-devices.js — no hard defects
  • node test/spec-vs-description.test.js — 3 passed
  • node test/hardware-invariants.test.js — 26 passed
  • node test/poe.test.js 18, poe-agreement.test.js 16, poe-inference.test.js 17 — all passed
  • Loaded both specs through the engine: UDM-SE 11 ports / 8 poeOut, UCG-Industrial 6 ports / 5 poeOut
Catalogue correction, Ubiquiti cloud-gateway family. The open `[Device]:` queue is fully blocked (#760/#757/#495/#494/#130 chassis or unlocalised fields, #789-#810 Huawei chassis and LineCard-only tables, #741-#743 OceanProtect controller configurations), so this run audits the one vendor family we can settle against the vendor's own spec tables. Two specs contradicted a vendor source, both in the same direction: the box ships with PoE hardware the spec did not model. ## UDM-SE — eight power-sourcing LAN ports were modelled as plain copper `devices/ubiquiti/udm-se.json` declared no `poe-pse` capability and no `poeOut` on any port, while its own description already said "8x 1GbE RJ45 LAN (2 PoE+, 6 PoE, 180W)". Ubiquiti's datasheet, PoE interface row: > Networking interface: (8) LAN: GbE RJ45 ports > PoE interface: (6) PoE (Pair A 1, 2+; 3, 6-) · (2) PoE+ (Pair A 1, 2+; 3, 6-) > PoE budget: 180W · Max. PoE wattage per port by PSE: PoE: 15.4W, PoE+: 30W Fix: all eight LAN ports carry `poeOut`, six as `PoE` and two as `PoE+`; capabilities gain `poe-pse`, `802.3af`, `802.3at`. **Modelling note, stated rather than hidden:** Ubiquiti publishes the class *counts*, not which physical ports are which. The two PoE+ ports are modelled as Port 1–2, i.e. the higher class on the lowest-numbered ports, which is the convention the sibling `udw.json` already follows (eth0–3 PoE++, eth4–7 PoE+, eth8–11 PoE). No port, speed or wattage was changed. ## UCG-Industrial — five PoE ports, not four Ubiquiti's Port Layout table for `techspecs.ui.com/unifi/cloud-gateways/ucg-industrial`: > 2.5 GbE RJ45 — 4 (2 PoE+++, 2 PoE+) (2.5G/1G/100M) > 10 GbE RJ45 — 1 (PoE+++) (10G/5G/2.5G/1G/100M) > 10G SFP+ — 1 (10G/1G) > PoE budget: DC input 270W / ATX power 75W · PoE+ 30W · PoE+++ 90W The 10G RJ45 port is marked PoE+++ but `eth4` carried no `poeOut`, so the catalogue would have hung a 90 W camera off a port it believed unpowered. Fix: `eth4` gains `poeOut`/`poeOutClass: PoE+++`, and the description now names it. `802.3bt` (which PoE+++ is) and `802.3at` were already declared, so no capability was added or dropped. ## Sources - https://techspecs.ui.com/unifi/cloud-gateways/udm-se - https://dl.ui.com/ds/udm_se_ds.pdf (PoE interface + budget rows) - https://techspecs.ui.com/unifi/cloud-gateways/ucg-industrial ## Checked and left alone - **UCG-Fiber** publishes a 30 W PoE budget and its description claims "1 PoE+", but the Port Layout rows annotate no port as PoE and no per-class wattage is given, so there is no source for *which* port sources power. Left unchanged rather than guessed; worth a follow-up if Ubiquiti ever localises it. - **Dream Wall Pro (#130)** — Ubiquiti's tech-specs catalogue now enumerates 17 cloud gateways and contains no Pro entry at all, and `dl.ui.com/ds/udw_pro_ds.pdf` returns the site's HTML, not a PDF. Blocker stands. ## Gates - `node scripts/syntax-check.js` — 348 files, all OK - `node scripts/audit-port-types.js` — no port contradicts its declared type (exit 0) - `node scripts/audit-devices.js` — no hard defects - `node test/spec-vs-description.test.js` — 3 passed - `node test/hardware-invariants.test.js` — 26 passed - `node test/poe.test.js` 18, `poe-agreement.test.js` 16, `poe-inference.test.js` 17 — all passed - Loaded both specs through the engine: UDM-SE 11 ports / 8 poeOut, UCG-Industrial 6 ports / 5 poeOut
Ubiquiti cloud gateways: the PoE the datasheets publish and the specs did not
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 18) (pull_request) Successful in 1m28s
CI / Test (Node 20) (pull_request) Successful in 1m29s
CI / Test (Node 22) (pull_request) Successful in 1m40s
46231f0d33
UDM-SE: the datasheet lists (6) PoE and (2) PoE+ on the eight GbE LAN ports
with a 180 W budget, but all eight ports were modelled as plain copper and
the capability list had no poe-pse at all - a lab could not power anything
from the box that ships with a PoE budget.

UCG-Industrial: Ubiquiti's Port Layout row marks the 10G RJ45 port
'(PoE+++)', 90 W by PSE, so the box has five power-sourcing ports, not four.

Sources: https://dl.ui.com/ds/udm_se_ds.pdf,
https://techspecs.ui.com/unifi/cloud-gateways/udm-se,
https://techspecs.ui.com/unifi/cloud-gateways/ucg-industrial
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 12:01:56 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1657
No description provided.