devices(hikvision): seven DS-3E PoE budgets, and three of them were the /M build's #2271

Merged
jaylouisw merged 1 commit from catalogue/1120-0652 into main 2026-11-20 07:08:21 +00:00
Owner

Hikvision DS-3E PoE budgets — seven rows, three of them wrong

scripts/audit-poe-budget.js listed seven devices/hikvision/ds-3e*.json rows as silent: PoE out on
the panel, no poe.budgetW, and the figure only in prose. Reading the model-specific vendor PDFs shows
that three of those prose figures belong to the /M build of the same chassis, and one is the wrong
row of the datasheet entirely:

spec was now vendor's PoE Power Budget
ds-3e0510p-e 58 W 110 W 58 W is DS-3E0510P-E/M; the base sheet prints PoE Power Budget 110 W
ds-3e1318p-ei 130 W 230 W 130 W is DS-3E1318P-EI/M, and its panel is 1x RJ45 + 1x combo, not 2x combo
ds-3e0505hp-e "65 W total" 60 W 65 W is Max. Power Consumption; PoE Power Budget is 60 W
ds-3e0505p-e 60 W 60 W (cited) traced; max consumption 65 W, 5 W idle
ds-3e0518p-e 230 W 230 W (cited) traced; max consumption 250 W, 20 W idle
ds-3e1105p-ei 60 W 60 W (cited) traced to the Hikvision USA sheet
ds-3e1326p-ei 370 W 370 W (cited) traced; max consumption 400 W

ds-3e1318p-ei also carried the /M uplink layout — 1x 1G RJ45 + 1x 1G combo. Both the 2020-03-31
and the 2024-04-28 sheets print 16 x 10/100 Mbps PoE port, 2 x Gigabit combo for the base model,
so the spec now has combo1 + combo2 like its 24-port sibling, and 18 interfaces total.

Every budget now sits in poe.budgetW with the URL that prints it in poe.sourceUrl, and the same URL
in the top-level sourceUrl (none of the seven had one).

research/hikvision-poe-census.md records the full table, the five /M budgets that must not be copied
up (58/130/125/35/45 W), and one instrument trap: www.hikvision.com/content/dam/... answers 200 with
a 985-byte HTML shell
for a path that does not exist (control: DS-3E9999ZZ-DoesNotExist.pdf), so a
200 there is not evidence and curl cannot read those PDFs at all — web_extract can.

Gates

  • node scripts/syntax-check.js — 483 files, all OK
  • node scripts/audit-port-types.js — no port contradicts its declared type
  • node scripts/audit-devices.js — no hard defects
  • test/hardware-invariants.test.js — 26/26
  • node scripts/run-tests.js — 403 suites, 13,407 assertions, 0 failed
  • node scripts/audit-poe-budget.js — silent rows 95 → 88 (the three Hikvision NVRs remain, uncited)

Device-request queue

Nothing here is from a request: both entries in the open queue stay blocked and were re-read, not
re-probed. Refs #803 and #130 — the E6616X still needs a stated build plus an E1/T1 media family
(engine/media.js has no such cage, and this stream carries no engine changes), and the UDW-PRO still
has no Ubiquiti-hosted artefact naming the SKU after thirteen surfaces. The three DS-7616NXI-K2/16P
class NVRs with PSE ports and no cited budget are the next item on this vendor.

## Hikvision DS-3E PoE budgets — seven rows, three of them wrong `scripts/audit-poe-budget.js` listed seven `devices/hikvision/ds-3e*.json` rows as *silent*: PoE out on the panel, no `poe.budgetW`, and the figure only in prose. Reading the model-specific vendor PDFs shows that **three of those prose figures belong to the `/M` build of the same chassis**, and one is the wrong row of the datasheet entirely: | spec | was | now | vendor's `PoE Power Budget` | |---|---|---|---| | `ds-3e0510p-e` | 58 W | **110 W** | 58 W is `DS-3E0510P-E/M`; the base sheet prints `PoE Power Budget 110 W` | | `ds-3e1318p-ei` | 130 W | **230 W** | 130 W is `DS-3E1318P-EI/M`, and its panel is 1x RJ45 + 1x combo, not 2x combo | | `ds-3e0505hp-e` | "65 W total" | **60 W** | 65 W is `Max. Power Consumption`; `PoE Power Budget` is 60 W | | `ds-3e0505p-e` | 60 W | 60 W (cited) | traced; max consumption 65 W, 5 W idle | | `ds-3e0518p-e` | 230 W | 230 W (cited) | traced; max consumption 250 W, 20 W idle | | `ds-3e1105p-ei` | 60 W | 60 W (cited) | traced to the Hikvision USA sheet | | `ds-3e1326p-ei` | 370 W | 370 W (cited) | traced; max consumption 400 W | `ds-3e1318p-ei` also carried the `/M` uplink layout — `1x 1G RJ45 + 1x 1G combo`. Both the 2020-03-31 and the 2024-04-28 sheets print **`16 x 10/100 Mbps PoE port, 2 x Gigabit combo`** for the base model, so the spec now has `combo1` + `combo2` like its 24-port sibling, and 18 interfaces total. Every budget now sits in `poe.budgetW` with the URL that prints it in `poe.sourceUrl`, and the same URL in the top-level `sourceUrl` (none of the seven had one). `research/hikvision-poe-census.md` records the full table, the five `/M` budgets that must not be copied up (58/130/125/35/45 W), and one instrument trap: `www.hikvision.com/content/dam/...` answers **200 with a 985-byte HTML shell** for a path that does not exist (control: `DS-3E9999ZZ-DoesNotExist.pdf`), so a 200 there is not evidence and `curl` cannot read those PDFs at all — `web_extract` can. ### Gates - `node scripts/syntax-check.js` — 483 files, all OK - `node scripts/audit-port-types.js` — no port contradicts its declared type - `node scripts/audit-devices.js` — no hard defects - `test/hardware-invariants.test.js` — 26/26 - `node scripts/run-tests.js` — 403 suites, 13,407 assertions, 0 failed - `node scripts/audit-poe-budget.js` — silent rows 95 → 88 (the three Hikvision NVRs remain, uncited) ### Device-request queue Nothing here is from a request: both entries in the open queue stay blocked and were re-read, not re-probed. Refs #803 and #130 — the E6616X still needs a stated build plus an E1/T1 media family (`engine/media.js` has no such cage, and this stream carries no engine changes), and the UDW-PRO still has no Ubiquiti-hosted artefact naming the SKU after thirteen surfaces. The three `DS-7616NXI-K2/16P` class NVRs with PSE ports and no cited budget are the next item on this vendor.
devices(hikvision): seven DS-3E PoE budgets, and three of them were the /M build's
All checks were successful
CI / Classify the change (pull_request) Successful in 22s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Test (Node 20) (pull_request) Successful in 1m7s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Server smoke and Docker build (pull_request) Successful in 27s
CI / Arm auto-merge (pull_request) Successful in 4s
62a2cead4a
The six DS-3E switches and one Hi-PoE switch carried their PoE budget in prose only - seven rows
'audit-poe-budget' reported as silent - and three of those prose figures were the /M variant's:

  ds-3e0510p-e   58 W  -> 110 W   (58 W is DS-3E0510P-E/M)
  ds-3e1318p-ei  130 W -> 230 W   (130 W is DS-3E1318P-EI/M, a different panel too)
  ds-3e0505hp-e  '65 W' -> 60 W   (65 W is max power consumption, not the budget)

ds-3e1318p-ei also had the /M uplink layout: 1x 1G RJ45 + 1x 1G combo where the base model's
datasheet prints 2x 1G combo. Both vendor sheets (2020-03-31 and 2024-04-28) agree.

The other four budgets were right and are now traced to a URL: 0505P-E 60 W, 0518P-E 230 W,
1105P-EI 60 W, 1326P-EI 370 W. Idle-vs-max consumption rows corrected on 0505P-E (65 W max /
5 W idle) and 0518P-E (250 W max / 20 W idle).

research/hikvision-poe-census.md records the table, the five /M budgets, and the instrument trap:
hikvision.com/content/dam answers 200 with a 985-byte HTML shell for paths that do not exist.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 07:05:26 +00:00
jaylouisw deleted branch catalogue/1120-0652 2026-11-20 07:08: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!2271
No description provided.