EnGenius Cloud L2+: eleven switches, PoE budgets that are not ports x 30 W, and one 90 W chassis on a 410 W budget #1617

Merged
jaylouisw merged 1 commit from catalogue/1116-0625 into main 2026-11-16 06:41:30 +00:00
Owner

Adds the rest of the EnGenius Cloud managed switch family beside the ECS1552 already in the catalogue.

Added (11 specs)

  • L2Plus gigabit: ECS1528 (no PoE), ECS1528P (240 W), ECS1528FP (410 W), ECS1552P (410 W), ECS1552FP (740 W), ECS1008P (802.3af only, 55 W, desktop, no console), ECS1112FP (PoE on 1-8 only, 130 W, 2x 1G SFP)
  • MGPlus 2.5G: ECS2512 (no PoE), ECS2512FP (bt, 240 W)
  • 8XG 10G: ECS5512 (no PoE), ECS5512FP (bt up to 90 W a port, 410 W)

Corrected

  • devices/engenius/ECS1552.json: gained the sourceUrl it never had and the rj45 connector + speedCaps its port template was missing (one fewer "template port whose connector nothing declares" in the audit: 3252 -> 3204 ports, 143 -> 142 specs).

Numbers that are not what the model names suggest

  • ECS1552P: 410 W over 48 ports. 48 x 30 W would be 1440 W, so 13 ports at a full 30 W is the real limit.
  • ECS1552FP: 740 W is exactly 48 x 15.4 W (802.3af), not 48 x 30 W.
  • ECS5512FP: 8 ports at up to 90 W behind a 410 W supply - four ports at 90 W is the ceiling.
  • ECS1112FP: ports 9 and 10 are plain copper, not PoE; the two uplinks are 1G SFP, not SFP+.
  • ECS1008P: 802.3af only (15.4 W a port), no console port, no cages.

Discrepancies stated, not smoothed

  1. ECS5512FP PoE budget: 420 W in datasheet v1.00 (12/11/2020) vs 410 W on every current model page. Catalogue takes 410 W (later, and the figure the cloud comparison table prints).
  2. ECS5512FP full-load power: 745.61 W in the datasheet vs 410.35 W on the model pages - the page figure is below the switch's own PoE budget, so it cannot be total input power; the datasheet number is the credible one. No power field is modelled from either.
  3. ECS2512FP per-port wattage is not published by the vendor: modelled at the 802.3bt Type 3 60 W ceiling with that derivation written on the spec, against a 240 W budget (so at most four ports at 60 W).

Sources: the twelve EU model pages (per-model comparison table plus specification block), datasheet DS_Cloud_ECS1528P_v1.3.pdf, ECS2512FP-Datasheet.pdf (v1.10), ecs5512fp-datasheet.pdf (v1.00), and the Cloud Switch Series datasheet v1.02 (11/24/2020). Firmware lines: ECS15XX-25XX 1.2.136-197 (16 July 2026) for the 15xx/25xx classes, ECS55XX 2.2.66-174 for the 5512 pair - recorded on each spec.

Validation: syntax-check.js 339 files OK; audit-port-types.js exit 0, 0 offending devices, 0 offending ports (2,147 models / 23,658 ports); hardware-invariants 26/26, poe 18/18, validation 22/22, topology-roundtrip 35/35, canvas-ports 18/18, combo 19/19; check-control-bytes.js clean; importer accepted all 11 with 0 rejections (its only warnings are the descriptive 802.3af/at/bt tokens it keeps and reports by design).

Unverifiable: per-port PoE wattage for ECS2512FP (above); ECS5512FP's true input power; packet forwarding rates are taken from the cloud comparison table, which is the only place some of them appear.

Adds the rest of the EnGenius Cloud managed switch family beside the ECS1552 already in the catalogue. **Added (11 specs)** - L2Plus gigabit: ECS1528 (no PoE), ECS1528P (240 W), ECS1528FP (410 W), ECS1552P (410 W), ECS1552FP (740 W), ECS1008P (802.3af only, 55 W, desktop, no console), ECS1112FP (PoE on 1-8 only, 130 W, 2x 1G SFP) - MGPlus 2.5G: ECS2512 (no PoE), ECS2512FP (bt, 240 W) - 8XG 10G: ECS5512 (no PoE), ECS5512FP (bt up to 90 W a port, 410 W) **Corrected** - devices/engenius/ECS1552.json: gained the sourceUrl it never had and the rj45 connector + speedCaps its port template was missing (one fewer "template port whose connector nothing declares" in the audit: 3252 -> 3204 ports, 143 -> 142 specs). **Numbers that are not what the model names suggest** - ECS1552P: 410 W over 48 ports. 48 x 30 W would be 1440 W, so 13 ports at a full 30 W is the real limit. - ECS1552FP: 740 W is exactly 48 x 15.4 W (802.3af), not 48 x 30 W. - ECS5512FP: 8 ports at up to 90 W behind a 410 W supply - four ports at 90 W is the ceiling. - ECS1112FP: ports 9 and 10 are plain copper, not PoE; the two uplinks are 1G SFP, not SFP+. - ECS1008P: 802.3af only (15.4 W a port), no console port, no cages. **Discrepancies stated, not smoothed** 1. ECS5512FP PoE budget: 420 W in datasheet v1.00 (12/11/2020) vs 410 W on every current model page. Catalogue takes 410 W (later, and the figure the cloud comparison table prints). 2. ECS5512FP full-load power: 745.61 W in the datasheet vs 410.35 W on the model pages - the page figure is below the switch's own PoE budget, so it cannot be total input power; the datasheet number is the credible one. No power field is modelled from either. 3. ECS2512FP per-port wattage is not published by the vendor: modelled at the 802.3bt Type 3 60 W ceiling with that derivation written on the spec, against a 240 W budget (so at most four ports at 60 W). **Sources**: the twelve EU model pages (per-model comparison table plus specification block), datasheet DS_Cloud_ECS1528P_v1.3.pdf, ECS2512FP-Datasheet.pdf (v1.10), ecs5512fp-datasheet.pdf (v1.00), and the Cloud Switch Series datasheet v1.02 (11/24/2020). Firmware lines: ECS15XX-25XX 1.2.136-197 (16 July 2026) for the 15xx/25xx classes, ECS55XX 2.2.66-174 for the 5512 pair - recorded on each spec. **Validation**: syntax-check.js 339 files OK; audit-port-types.js exit 0, 0 offending devices, 0 offending ports (2,147 models / 23,658 ports); hardware-invariants 26/26, poe 18/18, validation 22/22, topology-roundtrip 35/35, canvas-ports 18/18, combo 19/19; check-control-bytes.js clean; importer accepted all 11 with 0 rejections (its only warnings are the descriptive 802.3af/at/bt tokens it keeps and reports by design). **Unverifiable**: per-port PoE wattage for ECS2512FP (above); ECS5512FP's true input power; packet forwarding rates are taken from the cloud comparison table, which is the only place some of them appear.
EnGenius Cloud L2+: eleven switches, 410 W that is not 48 x 30 W, and a 90 W chassis on the same budget
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 12s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Failing after 1m36s
CI / Test (Node 18) (pull_request) Failing after 1m46s
CI / Test (Node 22) (pull_request) Failing after 1m52s
1c510f3f49
Adds the rest of the EnGenius Cloud managed switch family beside the
ECS1552 already in the catalogue: the L2Plus gigabit line (ECS1528,
ECS1528P, ECS1528FP, ECS1552P, ECS1552FP, ECS1008P, ECS1112FP), the
MGPlus 2.5G pair (ECS2512, ECS2512FP) and the 8XG 10G pair (ECS5512,
ECS5512FP).

Port counts, PoE standards and budgets, switching capacity, cages and
console come from the vendor model pages, whose per-model comparison
table is the only place EnGenius states most of these, plus the three
model datasheets (ECS1528P v1.3 06032024, ECS2512FP v1.10 07/2021,
ECS5512FP v1.00 12/11/2020) and the Cloud Switch Series datasheet
v1.02 11/24/2020.

Facts worth the reader's attention:
- 410 W is not 48 x 30 W. ECS1552P: 410 W over 48 ports, so 13 ports at
  a full 30 W. ECS1552FP: 740 W, exactly 48 x 15.4 W, not 48 x 30 W.
- ECS5512FP declares up to 90 W a port behind a 410 W budget, so four
  ports at 90 W is the real ceiling, not eight.
- ECS1008P is 802.3af only (15.4 W), has no console port and no cages.
- ECS1112FP is PoE on ports 1-8 only; 9 and 10 are plain copper.
- ECS1112FP's two uplinks are 1G SFP, not SFP+.

Discrepancies recorded rather than smoothed:
- ECS5512FP PoE budget: 420 W in the model datasheet v1.00, 410 W on
  every current model page. Catalogue takes 410 W (the later figure).
- ECS5512FP full-load power: 745.61 W in the datasheet, 410.35 W on the
  model pages - the page figure is below its own PoE budget, so the
  datasheet number is the credible one; no power field is modelled.
- ECS2512FP per-port wattage is not published at all; modelled at the
  802.3bt Type 3 60 W ceiling with the derivation stated on the spec.

Also gives the existing ECS1552 spec a sourceUrl and the RJ45 connector
its template was missing.

2,147 models across 252 vendors (+11).
Author
Owner

This branch conflicts with main, so it was not rebased:

README.md devices/engenius/ecs1008p.json devices/engenius/ecs1112fp.json devices/engenius/ecs1528.json devices/engenius/ecs1528fp.json devices/engenius/ecs1528p.json devices/engenius/ecs1552.json devices/engenius/ecs1552fp.json devices/engenius/ecs1552p.json devices/engenius/ecs2512.json devices/engenius/ecs2512fp.json devices/engenius/ecs5512.json devices/engenius/ecs5512fp.json docs/DEVICE_REGISTRY.md research/incoming/devices-engenius-ecs.json 

A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.

This branch conflicts with `main`, so it was not rebased: ``` README.md devices/engenius/ecs1008p.json devices/engenius/ecs1112fp.json devices/engenius/ecs1528.json devices/engenius/ecs1528fp.json devices/engenius/ecs1528p.json devices/engenius/ecs1552.json devices/engenius/ecs1552fp.json devices/engenius/ecs1552p.json devices/engenius/ecs2512.json devices/engenius/ecs2512fp.json devices/engenius/ecs5512.json devices/engenius/ecs5512fp.json docs/DEVICE_REGISTRY.md research/incoming/devices-engenius-ecs.json ``` A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
jaylouisw force-pushed catalogue/1116-0625 from 1c510f3f49
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 12s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Failing after 1m36s
CI / Test (Node 18) (pull_request) Failing after 1m46s
CI / Test (Node 22) (pull_request) Failing after 1m52s
to bc86dcc888
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 1m14s
CI / Test (Node 18) (pull_request) Successful in 1m28s
CI / Test (Node 22) (pull_request) Successful in 1m35s
2026-11-16 06:41:02 +00:00
Compare
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 06:41:23 +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!1617
No description provided.