devices(ubiquiti): three EdgeSwitch PoE rows sourced 0 W and had no console #2251

Merged
jaylouisw merged 1 commit from catalogue/1120-0322 into main 2026-11-20 03:39:18 +00:00
Owner

Refs #130 only. This PR does not answer the UDW-PRO request and is deliberately worded so a merge cannot be read as one: no Ubiquiti-hosted artefact names that SKU (see the issue's own comment thread), so the request stays open on its blocker.

The defect

devices/ubiquiti/es-24-250w.json, es-48-500w.json and es-48-750w.json modelled every copper port as a bare 1G ethernet jack: no connector, no speedCaps, no poeOut, no poe block, and no sourceUrl at all. So:

  • a 24- or 48-port 802.3at switch answered show power inline with 0 PSE ports - an AP on Port 5 got no power from a box whose own page prints "Total PoE available: 250W" / "500W";
  • the engine fell through to the model-name parser, which is the exact defect class of #2235, #2244 and #2249;
  • the serial console each page prints was missing from the faceplate (26 jacks modelled for 27 physical on the 24-port, 52 for 53 on both 48-port units), and the four SFP cages named no connector.

What the vendor pages say (read 2026-11-20)

model Networking PoE Total PoE Console
ES-24-250W (24) GbE RJ45; (2) 1G SFP (24) PoE/PoE+; (24) 24V passive 250W (1) RJ45 serial
ES-48-500W (48) GbE RJ45; (2) 1/10G SFP+; (2) 1G SFP (48) PoE/PoE+; (48) 24V passive 500W (1) RJ45 serial
ES-48-750W (48) 10/100/1000 RJ45; (2) 1/10G SFP+; (2) 1G SFP PoE/PoE+; 24V passive, 34.2W/17W per port no row (1) RJ45 serial

Per-port ceiling on all three is PoE+: 34.2W (802.3at Type 2, 50-57V); max draw excluding PoE is 30W / 64W / 64W.

The 750 W model is modelled budgetUnknown, not 750 W. Its page prints Power supply: AC/DC, internal, 750W and Max. power consumption: Includes PoE output: 750W; Excludes PoE output: 64W, and no Total PoE available row - unlike its 500 W sibling. The arithmetic ceiling for PDs would be 750 - 64 = 686 W, and that subtraction is ours, not Ubiquiti's, so the ports and their 802.3at class are modelled and the budget is left explicitly unknown: the same call already recorded for ES-24-500W. If a maintainer prefers the derived 686 W, the two printed rows are in the file's poe.note.

Also here

  • es-16-150w.json: its page states (16) 10/100/1000 Mbps RJ45 ports, but the ports declared 1G/100M - the 10M rung is added, the same fix #2249 made across the ECS family. Its 150 W budget is not re-sourced by this pass: that page prints a 150 W PSU and a 150 W max consumption and no total-PoE row, so the figure is still the SKU name's, as the file's notes now state.
  • Speed ladders are declared only where printed: 10/100/1000 on the 48-750W and the 16-150W, GbE (1G/100M) on the 24-250W and 48-500W, 10G/1G on the SFP+ cages.

Gates

node scripts/syntax-check.js      -> Syntax-checked 476 files: all OK
node scripts/audit-port-types.js  -> models 2355, ports 29728, offending 0
node scripts/audit-devices.js     -> No hard defects.
node scripts/audit-poe-budget.js  -> ubiquiti/ES-24-250W and ES-48-500W leave the
                                     "budget from name" cohort; unknown 16 -> 17
node scripts/run-tests.js         -> 396 suites, 13235 assertions, 0 failed
node scripts/regen-registry-doc.js-> docs/CONNECTORS.md counts regenerated
                                     (29725 -> 29728 sockets, 972 -> 971 shapes)

Sources: https://techspecs.ui.com/uisp/wired/es-24-250w (583,341 B), .../es-48-500w (583,292 B), .../es-48-750w (582,768 B), .../es-16-150w (574,980 B) - all HTTP 200, server-rendered #product-attribute-specs-table, and none the 609,911 B techspecs front page that this host serves for a slug it does not have.

Refs #130 only. This PR does not answer the UDW-PRO request and is deliberately worded so a merge cannot be read as one: no Ubiquiti-hosted artefact names that SKU (see the issue's own comment thread), so the request stays open on its blocker. ## The defect `devices/ubiquiti/es-24-250w.json`, `es-48-500w.json` and `es-48-750w.json` modelled every copper port as a bare 1G ethernet jack: no `connector`, no `speedCaps`, no `poeOut`, no `poe` block, and no `sourceUrl` at all. So: - a 24- or 48-port 802.3at switch answered `show power inline` with 0 PSE ports - an AP on `Port 5` got no power from a box whose own page prints "Total PoE available: 250W" / "500W"; - the engine fell through to the model-name parser, which is the exact defect class of #2235, #2244 and #2249; - the serial console each page prints was missing from the faceplate (26 jacks modelled for 27 physical on the 24-port, 52 for 53 on both 48-port units), and the four SFP cages named no connector. ## What the vendor pages say (read 2026-11-20) | model | Networking | PoE | Total PoE | Console | |---|---|---|---|---| | ES-24-250W | (24) GbE RJ45; (2) 1G SFP | (24) PoE/PoE+; (24) 24V passive | **250W** | (1) RJ45 serial | | ES-48-500W | (48) GbE RJ45; (2) 1/10G SFP+; (2) 1G SFP | (48) PoE/PoE+; (48) 24V passive | **500W** | (1) RJ45 serial | | ES-48-750W | (48) 10/100/1000 RJ45; (2) 1/10G SFP+; (2) 1G SFP | PoE/PoE+; 24V passive, 34.2W/17W per port | *no row* | (1) RJ45 serial | Per-port ceiling on all three is `PoE+: 34.2W` (802.3at Type 2, 50-57V); max draw excluding PoE is 30W / 64W / 64W. **The 750 W model is modelled `budgetUnknown`, not 750 W.** Its page prints `Power supply: AC/DC, internal, 750W` and `Max. power consumption: Includes PoE output: 750W; Excludes PoE output: 64W`, and no `Total PoE available` row - unlike its 500 W sibling. The arithmetic ceiling for PDs would be 750 - 64 = 686 W, and that subtraction is ours, not Ubiquiti's, so the ports and their 802.3at class are modelled and the budget is left explicitly unknown: the same call already recorded for `ES-24-500W`. If a maintainer prefers the derived 686 W, the two printed rows are in the file's `poe.note`. ## Also here - `es-16-150w.json`: its page states `(16) 10/100/1000 Mbps RJ45 ports`, but the ports declared 1G/100M - the 10M rung is added, the same fix #2249 made across the ECS family. Its 150 W budget is **not** re-sourced by this pass: that page prints a 150 W PSU and a 150 W max consumption and no total-PoE row, so the figure is still the SKU name's, as the file's notes now state. - Speed ladders are declared only where printed: `10/100/1000` on the 48-750W and the 16-150W, `GbE` (1G/100M) on the 24-250W and 48-500W, `10G/1G` on the SFP+ cages. ## Gates ``` node scripts/syntax-check.js -> Syntax-checked 476 files: all OK node scripts/audit-port-types.js -> models 2355, ports 29728, offending 0 node scripts/audit-devices.js -> No hard defects. node scripts/audit-poe-budget.js -> ubiquiti/ES-24-250W and ES-48-500W leave the "budget from name" cohort; unknown 16 -> 17 node scripts/run-tests.js -> 396 suites, 13235 assertions, 0 failed node scripts/regen-registry-doc.js-> docs/CONNECTORS.md counts regenerated (29725 -> 29728 sockets, 972 -> 971 shapes) ``` Sources: `https://techspecs.ui.com/uisp/wired/es-24-250w` (583,341 B), `.../es-48-500w` (583,292 B), `.../es-48-750w` (582,768 B), `.../es-16-150w` (574,980 B) - all HTTP 200, server-rendered `#product-attribute-specs-table`, and none the 609,911 B techspecs front page that this host serves for a slug it does not have.
devices(ubiquiti): the 24/48-port EdgeSwitch PoE rows sourced no power
All checks were successful
CI / Classify the change (pull_request) Successful in 19s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke and Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m10s
CI / Test (Node 20) (pull_request) Successful in 1m15s
CI / Test (Node 18) (pull_request) Successful in 1m19s
CI / Arm auto-merge (pull_request) Successful in 4s
6b7d343891
ES-24-250W, ES-48-500W and ES-48-750W modelled every copper port as a
plain 1G ethernet jack: no connector, no poeOut, no budget. A 48-port
PoE+ switch therefore refused power to anything cabled to it, and the
serial console each page prints was missing from the faceplate.

Read from each model's own tech-spec table (uisp/wired/<model>):
  - (24)/(48) PoE/PoE+ ports, 34.2 W per port by PSE, 24V passive on
    the same jacks;
  - "Total PoE available" 250W (24-250W) and 500W (48-500W);
  - 48-750W prints no total-PoE row at all - only a 750 W PSU and
    64 W max draw excluding PoE - so it is modelled budgetUnknown,
    the same call already made for ES-24-500W;
  - (1) RJ45 serial console;
  - ES-16-150W gains the 10M rung its page states as 10/100/1000.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 03:30:31 +00:00
jaylouisw deleted branch catalogue/1120-0322 2026-11-20 03:39:20 +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!2251
No description provided.