poe(ubiquiti): the three UA-SK starter-kit hubs source on four jacks, not on the uplink #2461

Open
jaylouisw wants to merge 1 commit from catalogue/1121-1822 into main
Owner

Refs #130

Issue #130 (UDW-PRO) stays blocked - no Ubiquiti artefact names a Pro SKU - so this pass takes the next defect behind it. Three starter-kit hubs declared the PoE++ uplink as the PSE and left the four jacks a reader or lock is cabled to dry, with no poe.budgetW: Device fell through to the model-name parser, found no wattage and served 0 W, and scripts/audit-poe-budget.js listed all three as silent with 1 PSE each.

The vendor rows (all HTTP 200, read 2026-11-21)

  • https://techspecs.ui.com/unifi/door-access/ua-sk-gate (726,929 B) - Gate Hub: 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 55W aggregated), Max. Power Consumption 22W (Without PoE output) / 60W (With PoE output).
  • https://techspecs.ui.com/unifi/door-access/ua-sk-elevator (672,464 B) and https://techspecs.ui.com/unifi/door-access/ua-g3-sk-elevator (675,251 B) - Elevator Hub: Networking Interface (4) 10/100/1000 Base-T, Management (1) 10/100/1000 Base-T, PoE Interface (1) PoE++ input, 50V DC, 1.2A; (4) PoE+ outputs, 50V DC, 30W per port (Max 45W aggregated), Max. Power Consumption 7W (Without PoE output).

The census closes: Gate Hub 5 RJ45 = 1 input + 4 outputs; Elevator Hub 4 networking + 1 management = 5 RJ45 = 1 input + 4 outputs. So eth0 is the PD input (50 W, 60 W) and eth1-eth4 are 30 W PSE outputs behind poe.budgetW 55 / 45 - the same direction already used by ua-hub.json, ua-hub-gate.json and ua-g3-sk-gate.json.

One arithmetic trap recorded, not papered over

The Gate Hub prints 55 W of aggregate output and 22 W of device draw against a 50 V x 1 A = 50 W inlet (the kit ships a PoE++ adapter), and its own row says 60 W with PoE output. 55 + 22 = 77 W does not fit under either. The printed 55 W is kept as-is and the gap is written into poe.note as a vendor question - the Elevator Hub, by contrast, reconciles (45 + 7 = 52 W under 60 W).

Gates

  • node scripts/syntax-check.js - 543 files, all OK
  • node scripts/audit-port-types.js - 0 port(s) contradict their declared type
  • node scripts/premerge-check.js catalogue/1121-1822 - ok, 1/1 clean (builds the merged tree: hardware invariants + spec-vs-description)
  • node scripts/audit-poe-budget.js - silent 10 -> 7; unknown unchanged at 26; orphan 0; inferred 0
  • show power inline after computePoe(): Gate Hub Available:55.0(w) over eth1-eth4; both Elevator Hubs Available:45.0(w) over eth1-eth4
  • docs/CONNECTORS.md regenerated (29,786 sockets, 977 shapes)
Refs #130 Issue #130 (UDW-PRO) stays blocked - no Ubiquiti artefact names a Pro SKU - so this pass takes the next defect behind it. Three starter-kit hubs declared the PoE++ **uplink** as the PSE and left the four jacks a reader or lock is cabled to dry, with no `poe.budgetW`: `Device` fell through to the model-name parser, found no wattage and served 0 W, and `scripts/audit-poe-budget.js` listed all three as silent with 1 PSE each. ### The vendor rows (all HTTP 200, read 2026-11-21) - `https://techspecs.ui.com/unifi/door-access/ua-sk-gate` (726,929 B) - Gate Hub: **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 55W aggregated)**, **Max. Power Consumption 22W (Without PoE output) / 60W (With PoE output)**. - `https://techspecs.ui.com/unifi/door-access/ua-sk-elevator` (672,464 B) and `https://techspecs.ui.com/unifi/door-access/ua-g3-sk-elevator` (675,251 B) - Elevator Hub: **Networking Interface (4) 10/100/1000 Base-T**, **Management (1) 10/100/1000 Base-T**, **PoE Interface (1) PoE++ input, 50V DC, 1.2A; (4) PoE+ outputs, 50V DC, 30W per port (Max 45W aggregated)**, **Max. Power Consumption 7W (Without PoE output)**. The census closes: Gate Hub 5 RJ45 = 1 input + 4 outputs; Elevator Hub 4 networking + 1 management = 5 RJ45 = 1 input + 4 outputs. So `eth0` is the PD input (50 W, 60 W) and `eth1`-`eth4` are 30 W PSE outputs behind `poe.budgetW` 55 / 45 - the same direction already used by `ua-hub.json`, `ua-hub-gate.json` and `ua-g3-sk-gate.json`. ### One arithmetic trap recorded, not papered over The Gate Hub prints 55 W of aggregate output and 22 W of device draw against a 50 V x 1 A = 50 W inlet (the kit ships a PoE++ adapter), and its own row says 60 W *with* PoE output. 55 + 22 = 77 W does not fit under either. The printed 55 W is kept as-is and the gap is written into `poe.note` as a vendor question - the Elevator Hub, by contrast, reconciles (45 + 7 = 52 W under 60 W). ### Gates - `node scripts/syntax-check.js` - 543 files, all OK - `node scripts/audit-port-types.js` - 0 port(s) contradict their declared type - `node scripts/premerge-check.js catalogue/1121-1822` - **ok**, 1/1 clean (builds the merged tree: hardware invariants + spec-vs-description) - `node scripts/audit-poe-budget.js` - silent **10 -> 7**; unknown unchanged at 26; orphan 0; inferred 0 - `show power inline` after `computePoe()`: Gate Hub `Available:55.0(w)` over eth1-eth4; both Elevator Hubs `Available:45.0(w)` over eth1-eth4 - `docs/CONNECTORS.md` regenerated (29,786 sockets, 977 shapes)
poe(ubiquiti): the three UA-SK starter-kit hubs source on four jacks, not on the uplink (Refs #130)
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Successful in 1m25s
CI / Test (Node 22) (pull_request) Successful in 1m27s
CI / Test (Node 18) (pull_request) Successful in 1m36s
CI / Arm auto-merge (pull_request) Successful in 7s
1380d1c5b9
The Gate Hub and both Elevator Hubs modelled the PoE++ uplink as the PSE and
left the four jacks a reader or lock is actually cabled to dry, with no
poe.budgetW, so the loader fell through to the model name and served 0 W.
Ubiquiti's own rows close the census: Gate Hub (5) 10/100/1000 Base-T with
(1) PoE++ input 50V 1A and (4) PoE outputs 50V 30W/port, max 55W aggregated;
Elevator Hub (4) networking + (1) management with (1) PoE++ input 50V 1.2A and
(4) PoE+ outputs 50V 30W/port, max 45W aggregated.

Same direction as ua-hub.json, ua-hub-gate.json and ua-g3-sk-gate.json, which
were corrected the same way. audit-poe-budget: silent 10 -> 7.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:27:43 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:31:03 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:31:03 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:39:57 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 20:01:49 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 21:31:51 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 22:02:30 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 22:31:33 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 23:01:59 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 23:33:03 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 23:33:04 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 00:32:43 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 00:32:44 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 01:31:37 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 02:01:56 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 02:31:24 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 07:31:07 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 08:03:03 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 09:02:22 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 09:31:14 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 14:30:59 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 15:01:06 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 16:01:08 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 16:31:07 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 16:31:07 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 17:01:05 +00:00
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Successful in 1m25s
CI / Test (Node 22) (pull_request) Successful in 1m27s
CI / Test (Node 18) (pull_request) Successful in 1m36s
CI / Arm auto-merge (pull_request) Successful in 7s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin catalogue/1121-1822:catalogue/1121-1822
git switch catalogue/1121-1822
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!2461
No description provided.