devices(ubiquiti): source the UDM-Pro-Max census and stop its copper ports drawing PoE (refs issue 130) #2111
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-0652"
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?
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.jsonhad no source at all - nosourceUrl, no notes - and its nine copper ports were being turned into a 12.95 W PoE load by the engine'sunifiname 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,displaySkuUDM-Pro-Max) carries the same table as embedded spec JSON withPoE Support = Empty,PoE Budget = Empty,PoE / PoE+ / PoE++ / PoE+++ = Empty,Voltage Range PoE Mode = Empty- the vendor saying the field does not apply, againstudm-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
sourceUrland anotesblock quoting both tables (byte counts, read date 2026-11-19).poeIn: falseon the nine copper ports.isPoePd()inengine/media.jstreats any model or label matchingunifias 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 waypoeOut: trueis.dl.ui.com/ds/udm-pro-max_ds.pdfwas 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.jsclean, registry doc regenerates with no diff (972 shapes).