devices(ubiquiti): ten door-access hubs sourced PoE on the port that is powered, and none had a budget #2280

Merged
jaylouisw merged 1 commit from catalogue/1120-0822 into main 2026-11-20 08:39:22 +00:00
Owner

Refs #130 only (no closing keyword - the UDW-PRO question is untouched; this is queue-stream catalogue work on the same surface, Ubiquiti PoE rows).

Defect. node scripts/audit-poe-budget.js listed 25 Ubiquiti specs as "Silent (PoE out, no budget)". Almost all are door access, and on ten of them the direction was also inverted: eth0 declared poeOut class PoE++ - the uplink the switch feeds - while the jacks a camera is cabled to declared nothing. So the spec advertised a 60 W source on its input, and the real outputs could source nothing.

Vendor row (https://techspecs.ui.com/unifi/door-access/ua-hub-door, HTTP 200, 624,799 B, read 2026-11-20):

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 45W aggregated)
Max. Power Consumption 30W (Without PoE output) / 50W (With PoE output)
Power Method          PoE++

Ten files, same shape (techspecs.ui.com/unifi/door-access/<slug>):

spec ports PoE row aggregate max w/o PoE
ua-hub-door 5 1 PoE++ in + 4 PoE+ out @30 W 45 W 30 W
ua-hub-door-mini 3 1 PoE++ in + 2 PoE+ out @30 W 45 W 19 W
ua-hub-gate 5 1 PoE++ in + 4 PoE+ out @30 W 55 W 22 W
ua-hub 5 1 PoE++ in + 4 PoE+ out @30 W 45 W 30 W (direction already right, budget missing)
eah-8 10 8 PoE+ out @30 W 190 W 240 W consumption
ua-g3-sk 3 1 PoE++ in + 2 PoE out @30 W 45 W 19 W
ua-g3-sk-pro 5 1 PoE++ in + 4 PoE out @30 W 45 W 30 W
ua-g3-sk-gate 5 1 PoE++ in + 4 PoE out @30 W 55 W 22 W
ua-g2-sk 5 1 PoE++ in + 4 PoE out @30 W 45 W 30 W
ua-g2-sk-pro 5 1 PoE++ in + 4 PoE out @30 W 45 W 30 W

eah-8 is the same defect in another form: its description said "240 W max", which is Max. Power Consumption; the PSE allocation is 190 W across eight 30 W outputs. Outputs are modelled PoE+ because every page gives 30 W per port (802.3at Type 2) even where the row says "PoE outputs"; pages printing 10/100/1000 Base-T also gained the 10M rung on both banks.

Lab-visible effect. Dream Wall (PoE++ 420 W) -> UA-Hub-Door eth0, four 12.95 W PDs on eth1-eth4: before, hub budget 0 W (PSE skipped by computePoe()), nothing powered; after, budget 45 W, three PDs powered (38.85 W) and the fourth refused - PSE budget exhausted: 12.95 W requested, 6.15 W left.

Gates. node scripts/syntax-check.js (485 files OK); node scripts/audit-port-types.js (0 offending ports); node scripts/audit-poe-budget.js (silent PSEs 85 -> 75, Ubiquiti 25 -> 15); node test/hardware-invariants.test.js (26/26); node test/poe.test.js (21/21); node test/spec-vs-description.test.js (3/3); node test/port-roles.test.js (19/19); node test/request-queue.test.js (32/32); npm run regen:registry-doc (no drift).

Not touched, and why: ua-g3-sk-elevator prints (4) 10/100/1000 Base-T and Management (1) 10/100/1000 Base-T - five jacks - while its PoE row is 1 in + 4 out, also five; the jack map cannot be resolved from the page, so nothing was written rather than guessing. ua-sk-elevator / ua-sk-gate still need their own pages read.

Evidence note: research/ubiquiti-door-access-hub-poe-direction.md.

Refs #130 only (no closing keyword - the UDW-PRO question is untouched; this is queue-stream catalogue work on the same surface, Ubiquiti PoE rows). **Defect.** `node scripts/audit-poe-budget.js` listed 25 Ubiquiti specs as "Silent (PoE out, no budget)". Almost all are door access, and on ten of them the direction was also inverted: eth0 declared `poeOut` class `PoE++` - the uplink the switch feeds - while the jacks a camera is cabled to declared nothing. So the spec advertised a 60 W source on its input, and the real outputs could source nothing. **Vendor row** (`https://techspecs.ui.com/unifi/door-access/ua-hub-door`, HTTP 200, 624,799 B, read 2026-11-20): ``` 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 45W aggregated) Max. Power Consumption 30W (Without PoE output) / 50W (With PoE output) Power Method PoE++ ``` **Ten files, same shape** (`techspecs.ui.com/unifi/door-access/<slug>`): | spec | ports | PoE row | aggregate | max w/o PoE | |--|--|--|--|--| | ua-hub-door | 5 | 1 PoE++ in + 4 PoE+ out @30 W | 45 W | 30 W | | ua-hub-door-mini | 3 | 1 PoE++ in + 2 PoE+ out @30 W | 45 W | 19 W | | ua-hub-gate | 5 | 1 PoE++ in + 4 PoE+ out @30 W | 55 W | 22 W | | ua-hub | 5 | 1 PoE++ in + 4 PoE+ out @30 W | 45 W | 30 W (direction already right, budget missing) | | eah-8 | 10 | 8 PoE+ out @30 W | 190 W | 240 W consumption | | ua-g3-sk | 3 | 1 PoE++ in + 2 PoE out @30 W | 45 W | 19 W | | ua-g3-sk-pro | 5 | 1 PoE++ in + 4 PoE out @30 W | 45 W | 30 W | | ua-g3-sk-gate | 5 | 1 PoE++ in + 4 PoE out @30 W | 55 W | 22 W | | ua-g2-sk | 5 | 1 PoE++ in + 4 PoE out @30 W | 45 W | 30 W | | ua-g2-sk-pro | 5 | 1 PoE++ in + 4 PoE out @30 W | 45 W | 30 W | `eah-8` is the same defect in another form: its description said "240 W max", which is **Max. Power Consumption**; the PSE allocation is **190 W** across eight 30 W outputs. Outputs are modelled `PoE+` because every page gives 30 W per port (802.3at Type 2) even where the row says "PoE outputs"; pages printing `10/100/1000 Base-T` also gained the 10M rung on both banks. **Lab-visible effect.** Dream Wall (PoE++ 420 W) -> UA-Hub-Door eth0, four 12.95 W PDs on eth1-eth4: before, hub budget 0 W (PSE skipped by `computePoe()`), nothing powered; after, budget 45 W, three PDs powered (38.85 W) and the fourth refused - `PSE budget exhausted: 12.95 W requested, 6.15 W left`. **Gates.** `node scripts/syntax-check.js` (485 files OK); `node scripts/audit-port-types.js` (0 offending ports); `node scripts/audit-poe-budget.js` (silent PSEs **85 -> 75**, Ubiquiti **25 -> 15**); `node test/hardware-invariants.test.js` (26/26); `node test/poe.test.js` (21/21); `node test/spec-vs-description.test.js` (3/3); `node test/port-roles.test.js` (19/19); `node test/request-queue.test.js` (32/32); `npm run regen:registry-doc` (no drift). **Not touched, and why:** `ua-g3-sk-elevator` prints (4) 10/100/1000 Base-T **and** Management (1) 10/100/1000 Base-T - five jacks - while its PoE row is 1 in + 4 out, also five; the jack map cannot be resolved from the page, so nothing was written rather than guessing. `ua-sk-elevator` / `ua-sk-gate` still need their own pages read. Evidence note: `research/ubiquiti-door-access-hub-poe-direction.md`.
devices(ubiquiti): ten door-access hubs sourced PoE on the port that is powered, and none had a budget
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Server smoke and Docker build (pull_request) Successful in 23s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 4s
8b25f23007
The UA-Hub-Door family, EAH-8 and the G2/G3 starter kits declared poeOut class PoE++ on eth0 - the uplink that the switch feeds - and nothing on the jacks a camera is cabled to. None carried poe.budgetW, so the loader fell through to the model name, found no wattage and served 0 W. Ubiquiti's own row on techspecs.ui.com/unifi/door-access/<slug> is (1) PoE++ input + (N) PoE[+] outputs at 30 W per port with an aggregate max (45/55/190 W); direction and budget now follow it, and the jacks gained the 10M rung the pages print. audit-poe-budget: silent PSEs 85 -> 75.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 08:32:36 +00:00
jaylouisw deleted branch catalogue/1120-0822 2026-11-20 08:39:24 +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!2280
No description provided.