devices(ubiquiti): source the UDM-Pro-Max census and stop its copper ports drawing PoE (refs issue 130) #2111

Merged
jaylouisw merged 1 commit from catalogue/1119-0652 into main 2026-11-19 07:12:15 +00:00
Owner

Refs #130

The Dream Wall Pro itself remains unsourced (see the comment on the issue), so this pass repaired the nearest real sibling a requester would be offered instead: devices/ubiquiti/udm-pro-max.json had no source at all - no sourceUrl, no notes - and its nine copper ports were being turned into a 12.95 W PoE load by the engine's unifi name match.

Census, from the vendor's own structured table - https://techspecs.ui.com/unifi/cloud-gateways/udm-pro-max (HTTP 200, 677,375 B):
1 GbE RJ45 = 8 (1G/100M/10M), 2.5 GbE RJ45 = 1 (2.5G/1G/100M/10M), 10G SFP+ = 2 (10G/1G), Max. WAN Port Count = 8, Default WAN Ports = (1) 10G SFP+ / (1) 2.5 GbE RJ45, Max. Power Consumption = 60W, Power Method = (1) Universal AC input, 100-240V AC / (1) USP-RPS DC input, 11.5V DC, NVR Storage = (2) 3.5" bays, IDS/IPS Throughput = 5 Gbps. The eleven interfaces already on the row are exactly those rows - no port added or removed.

PoE is the field this row had to get right, because it is the one field where its sibling differs: https://store.ui.com/us/en/products/udm-pro-max (200, 598,527 B, displaySku UDM-Pro-Max) carries the same table as embedded spec JSON with PoE Support = Empty, PoE Budget = Empty, PoE / PoE+ / PoE++ / PoE+++ = Empty, Voltage Range PoE Mode = Empty - the vendor saying the field does not apply, against udm-se.json's 8 ports and 180 W. Copying the SE numbers here is the family-sibling error this catalogue has corrected on UDM PoE, two i-MO console ports and three MA5801 uplinks.

What changed

  • sourceUrl and a notes block quoting both tables (byte counts, read date 2026-11-19).
  • poeIn: false on the nine copper ports. isPoePd() in engine/media.js treats any model or label matching unifi as a powered device, which is right for an access point and wrong for a box fed by a 100 W internal AC supply or the RPS DC input; neither vendor table publishes a PoE input. Declared, the port no longer picks up a phantom 12.95 W draw that a lab could spend against a switch's budget. No engine change - the declaration is the spec's, the same way poeOut: true is.
  • Description now states the 8-WAN-port maximum and "no PoE on any port" instead of calling the 1G ports LAN-only.

dl.ui.com/ds/udm-pro-max_ds.pdf was tried and falls back to the 609,911-byte techspecs home page, so no datasheet is cited.

Gates: node scripts/syntax-check.js (443 files OK), node scripts/audit-port-types.js ("No port contradicts its declared type"), node test/poe-inference.test.js (17 passed), node test/hardware-invariants.test.js (26 passed), node scripts/audit-poe-budget.js (108 of 403 PSEs unaskable, unchanged), node scripts/run-tests.js (364 suites, 12,420 assertions, 0 failed), node scripts/check-control-bytes.js clean, registry doc regenerates with no diff (972 shapes).

Refs #130 The Dream Wall Pro itself remains unsourced (see the comment on the issue), so this pass repaired the nearest real sibling a requester would be offered instead: `devices/ubiquiti/udm-pro-max.json` had **no source at all** - no `sourceUrl`, no notes - and its nine copper ports were being turned into a 12.95 W PoE **load** by the engine's `unifi` name match. **Census, from the vendor's own structured table** - `https://techspecs.ui.com/unifi/cloud-gateways/udm-pro-max` (HTTP 200, 677,375 B): `1 GbE RJ45 = 8 (1G/100M/10M)`, `2.5 GbE RJ45 = 1 (2.5G/1G/100M/10M)`, `10G SFP+ = 2 (10G/1G)`, `Max. WAN Port Count = 8`, `Default WAN Ports = (1) 10G SFP+ / (1) 2.5 GbE RJ45`, `Max. Power Consumption = 60W`, `Power Method = (1) Universal AC input, 100-240V AC / (1) USP-RPS DC input, 11.5V DC`, `NVR Storage = (2) 3.5" bays`, `IDS/IPS Throughput = 5 Gbps`. The eleven interfaces already on the row are exactly those rows - no port added or removed. **PoE is the field this row had to get right**, because it is the one field where its sibling differs: `https://store.ui.com/us/en/products/udm-pro-max` (200, 598,527 B, `displaySku` `UDM-Pro-Max`) carries the same table as embedded spec JSON with `PoE Support = Empty`, `PoE Budget = Empty`, `PoE / PoE+ / PoE++ / PoE+++ = Empty`, `Voltage Range PoE Mode = Empty` - the vendor saying the field does not apply, against `udm-se.json`'s 8 ports and 180 W. Copying the SE numbers here is the family-sibling error this catalogue has corrected on UDM PoE, two i-MO console ports and three MA5801 uplinks. **What changed** - `sourceUrl` and a `notes` block quoting both tables (byte counts, read date 2026-11-19). - `poeIn: false` on the nine copper ports. `isPoePd()` in `engine/media.js` treats any model or label matching `unifi` as a powered device, which is right for an access point and wrong for a box fed by a 100 W internal AC supply or the RPS DC input; neither vendor table publishes a PoE input. Declared, the port no longer picks up a phantom 12.95 W draw that a lab could spend against a switch's budget. No engine change - the declaration is the spec's, the same way `poeOut: true` is. - Description now states the 8-WAN-port maximum and "no PoE on any port" instead of calling the 1G ports LAN-only. `dl.ui.com/ds/udm-pro-max_ds.pdf` was tried and falls back to the 609,911-byte techspecs home page, so no datasheet is cited. **Gates**: `node scripts/syntax-check.js` (443 files OK), `node scripts/audit-port-types.js` ("No port contradicts its declared type"), `node test/poe-inference.test.js` (17 passed), `node test/hardware-invariants.test.js` (26 passed), `node scripts/audit-poe-budget.js` (108 of 403 PSEs unaskable, unchanged), `node scripts/run-tests.js` (364 suites, 12,420 assertions, 0 failed), `node scripts/check-control-bytes.js` clean, registry doc regenerates with no diff (972 shapes).
devices(ubiquiti): source the UDM-Pro-Max census and stop its copper ports drawing PoE (refs issue 130)
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 13s
CI / Arm auto-merge (pull_request) Successful in 3s
4b0174ad1f
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 07:04:14 +00:00
jaylouisw deleted branch catalogue/1119-0652 2026-11-19 07:12:17 +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!2111
No description provided.