poe(reolink): the RLN8-410 source ports are 25 W each, and the aggregate exists but is never printed (Refs #130) #2459

Merged
jaylouisw merged 1 commit from catalogue/1121-1752 into main 2026-11-21 18:08:53 +00:00
Owner

Refs #130 (the Dream Wall Pro request this stream is blocked on; this PR does not close it)

devices/reolink/rln8-410.json had eight PSE ports at 25.5 W each and no poe block. 25.5 is the 802.3at class-4 ceiling, not anything Reolink prints: its own sheet says 25 W, and the description in the same file already said 25 W, so the ports contradicted the prose beside them. With no poe block the eight PSEs also reached scripts/audit-poe-budget.js as silent - the exact shape of the Dream Wall defect that audit was written for.

What the vendor says

Read 2026-11-21, Reolink only:

  • https://home-cdn.reolink.us/files/docs/specs/RLN8-410-PoE-NVR-Specifications.pdf (200, application/pdf, 36,246 B, text layer, hardware N7MB01): the PoE table is exactly two rows - Max. Power Per Port 25W, Supported Standard IEEE 802.3af/at. General table: Power Supply DC 48V~53V, Power Consumption <10W (Without HDD&PoE).
  • https://reolink.com/product/rln8-410/ (200, 470,157 B): the same two PoE rows, 8, RJ-45 10/100 Mbps self-adaptive PoE Ethernet interface for IP camera.
  • https://cdn.reolink.com/files/docs/specs/RLK8-800B4-NVR-Kit-NVR-Specifications.pdf (200, 83,472 B, hardware V2): Power Supply DC 48V/1.875-2.5A - 90 to 120 W - against eight ports at 25 W, which is 200 W.
  • https://support.reolink.com/articles/29093193132825-How-Many-Cameras-Can-be-Added-to-Reolink-NVRs/: "The NVR has a fixed total power budget", and "Maximum total power supported by the NVR" is listed as a factor in camera count - but no watt figure is printed anywhere on the page.
  • https://support.reolink.com/articles/39154522558617-Overview-of-Monitoring-PoE-Camera-Power-Usage-via-Reolink-NVRs/: the alert fires "when the total PoE power approaches or exceeds the power adapter rated capacity".

So an aggregate exists, the vendor ties it to the supply, and never prints it. The supply is DC 48V~53V (V2: 1.875-2.5 A), which is below 8 x 25 W, so the cap that binds is the unpublished one.

The change

  • Eight ports: poeOut 25.5 -> 25, plus poeOutClass: "PoE+" (the sheet says IEEE 802.3af/at).
  • poe.budgetUnknown: true with sourceUrl and a note quoting the rows above and the two support articles. Not multiplied out and not read off the PSU: a PSU rating is not a PSE ceiling (the ES-24-500W lesson), and Reolink prints no number between them.
  • capabilities gains poe-pse, 802.3af, 802.3at (it sources power, and the sheet says so).
  • notes records the correction and the read date.

Gates

  • node scripts/syntax-check.js -> Syntax-checked 543 files: all OK
  • node scripts/audit-port-types.js -> Gated: 0 port(s) contradict their declared type
  • node scripts/audit-devices.js -> Gated: 0 hard defect(s)
  • node test/hardware-invariants.test.js -> 26 passed, 0 failed
  • node test/poe.test.js 21 passed, node test/poe-agreement.test.js 17 passed, node test/show-power-inline.test.js 41 passed
  • node scripts/audit-poe-budget.js: silent 11 -> 10, unknown on purpose 25 -> 26, orphan 0. reolink/RLN8-410 leaves the silent list; its eight PSEs are now counted as deliberately unknown.
Refs #130 (the Dream Wall Pro request this stream is blocked on; this PR does not close it) `devices/reolink/rln8-410.json` had eight PSE ports at **25.5 W each** and no `poe` block. 25.5 is the 802.3at class-4 ceiling, not anything Reolink prints: its own sheet says **25 W**, and the description in the same file already said 25 W, so the ports contradicted the prose beside them. With no `poe` block the eight PSEs also reached `scripts/audit-poe-budget.js` as silent - the exact shape of the Dream Wall defect that audit was written for. ## What the vendor says Read 2026-11-21, Reolink only: - `https://home-cdn.reolink.us/files/docs/specs/RLN8-410-PoE-NVR-Specifications.pdf` (200, `application/pdf`, 36,246 B, text layer, hardware N7MB01): the PoE table is exactly two rows - `Max. Power Per Port 25W`, `Supported Standard IEEE 802.3af/at`. General table: `Power Supply DC 48V~53V`, `Power Consumption <10W (Without HDD&PoE)`. - `https://reolink.com/product/rln8-410/` (200, 470,157 B): the same two PoE rows, `8, RJ-45 10/100 Mbps self-adaptive PoE Ethernet interface for IP camera`. - `https://cdn.reolink.com/files/docs/specs/RLK8-800B4-NVR-Kit-NVR-Specifications.pdf` (200, 83,472 B, hardware V2): `Power Supply DC 48V/1.875-2.5A` - 90 to 120 W - against eight ports at 25 W, which is 200 W. - `https://support.reolink.com/articles/29093193132825-How-Many-Cameras-Can-be-Added-to-Reolink-NVRs/`: "The NVR has a **fixed total power budget**", and "Maximum total power supported by the NVR" is listed as a factor in camera count - but no watt figure is printed anywhere on the page. - `https://support.reolink.com/articles/39154522558617-Overview-of-Monitoring-PoE-Camera-Power-Usage-via-Reolink-NVRs/`: the alert fires "when the total PoE power approaches or exceeds the power adapter rated capacity". So an aggregate exists, the vendor ties it to the supply, and never prints it. The supply is `DC 48V~53V` (V2: 1.875-2.5 A), which is below 8 x 25 W, so the cap that binds is the unpublished one. ## The change - Eight ports: `poeOut` 25.5 -> **25**, plus `poeOutClass: "PoE+"` (the sheet says `IEEE 802.3af/at`). - `poe.budgetUnknown: true` with `sourceUrl` and a note quoting the rows above and the two support articles. Not multiplied out and not read off the PSU: a PSU rating is not a PSE ceiling (the ES-24-500W lesson), and Reolink prints no number between them. - `capabilities` gains `poe-pse`, `802.3af`, `802.3at` (it sources power, and the sheet says so). - `notes` records the correction and the read date. ## Gates - `node scripts/syntax-check.js` -> `Syntax-checked 543 files: all OK` - `node scripts/audit-port-types.js` -> `Gated: 0 port(s) contradict their declared type` - `node scripts/audit-devices.js` -> `Gated: 0 hard defect(s)` - `node test/hardware-invariants.test.js` -> `26 passed, 0 failed` - `node test/poe.test.js` 21 passed, `node test/poe-agreement.test.js` 17 passed, `node test/show-power-inline.test.js` 41 passed - `node scripts/audit-poe-budget.js`: silent **11 -> 10**, unknown on purpose **25 -> 26**, orphan 0. `reolink/RLN8-410` leaves the silent list; its eight PSEs are now counted as deliberately unknown.
poe(reolink): the RLN8-410's eight ports are 25 W each and the aggregate exists but is never printed (Refs #130)
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 1m3s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
7ce29f9847
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 17:58:19 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:01:03 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:01:03 +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!2459
No description provided.