devices(ubiquiti): the UXG family is USB-C/AC powered, not PoE-powered (refs #130) #2121
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!2121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-0822"
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 (does not close it - the Pro's census is still unpublished; this is the catalogue defect found underneath the request).
What was wrong
isPoePd()inengine/media.jsmatchesunifiin a device's model/label and infers a 12.95 W 802.3af draw on any copper port the spec leaves silent. Four UXG rows said nothing about power, so each of their RJ45 sockets was a powered device:uxg-lite.jsonuxg-max.jsonuxg-enterprise.jsonuxg-fiber.jsonNone of the four accepts PoE on any port. A lab that cables one of these to a PoE switch would see the switch's budget spent on a gateway running off a wall wart. Same correction as
uxg-pro.json(#2118) andudm-pro-max.json(#2111).Evidence
Sources read 2026-11-19, all Ubiquiti-hosted:
https://techspecs.ui.com/unifi/cloud-gateways/uxg-lite- 200, 643,116 B. Port Layout: 1 GbE RJ45 x2 (1G/100M/10M); Max. WAN 1; Default WAN (1) GbE RJ45; Max. Power Consumption 3.83 W; Power Method USB type C (5V DC/3A).https://techspecs.ui.com/unifi/cloud-gateways/uxg-max- 200, 647,803 B. Port Layout: 2.5 GbE RJ45 x5 (2.5G/1G/100M/10M); Max. WAN 4; Max. Power Consumption 9.6 W; Power Method USB type C (5V DC/3A).https://techspecs.ui.com/unifi/cloud-gateways/uxg-enterprise- 200, 671,598 B. Port Layout: 2.5 GbE RJ45 x2, 10G SFP+ x2 (10G/1G), 25G SFP28 x2 (25G/10G/1G); Max. WAN 5; Max. Power Consumption 82 W; Power Method Universal AC input, 100-240V AC, 7A Max.; Power Supply (2) hot-swappable 150 W CRPS.https://techspecs.ui.com/unifi/cloud-gateways/uxg-fiber- 200, 649,433 B. Port Layout: 2.5 GbE RJ45 x4, 10 GbE RJ45 x1 (10G/2.5G/1G), 10G SFP+ x2 (10G/1G); Max. WAN 6; Max. Power Consumption 25 W excluding PoE; Power Method DC jack (54V DC/1.1A).store.ui.com/us/en/products/uxg-lite(200, 534,758 B),.../uxg-max(200, 525,162 B),.../uxg-enterprise(200, 539,028 B) each carry PoE Budget: flag Empty and repeat the power method quoted above.Port counts were re-checked against the same pages and are unchanged - only the power claim moves.
Deliberately not modelled: the Fiber's 30 W PoE+ port
uxg-fiberdoes source power: techspecs prints PoE Budget 30 W and Max. PoE Wattage per Port by PSE - PoE+ 30 W at 50-57 V, andstore.ui.com/us/en/products/uxg-fiber(200, 476,760 B) says "Integrated 4-port switch with (1) PoE+ port". So one of the four 2.5G RJ45 ports is a 30 W PSE - but Ubiquiti does not say which one, and publishes no datasheet for the SKU (the store payload carriesdatasheet: null;dl.ui.com/ds/uxg-fiber_ds.pdflands on the 609,911-byte techspecs front page). Naming a port would be a guess; declaring the 30 W budget with no PSE port failstest/poe-inference.test.js("a device that claims a budget with no port to source it"). Both stay unwritten, and the open field is recorded in the row's notes.Traps recorded
dl.ui.com/ds/{uxg-lite,uxg-max,uxg-enterprise,uxg-fiber}_ds.pdfall resolve tohttps://techspecs.ui.com/, 609,911 B,text/html- that is the datasheet miss, not a datasheet. The hyphenated key worked foruxg-proonly because that SKU has a published PDF.Gates
node scripts/syntax-check.js- 445 files, all OKnode scripts/audit-port-types.js- 2356 models, 0 offending portsnode test/hardware-invariants.test.js- 26 passed, 0 failednode test/import-devices-capabilities.test.js- 34 passed, 0 failednode test/poe-inference.test.js- 17 passed, 0 failednode scripts/regen-registry-doc.js- no diff (no device added or removed)