poe(teltonika): the OTD140 and OTD144 outlets are 802.3af at 15 W, and the inlet takes 21 #2453

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

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

Two silent PoE boxes in the Teltonika OTD family, both with the same defect: an outlet declared poeOut: true with poeOutClass: "PoE+" (802.3at) and no wattage, and an inlet declared poeIn: 12.95 (the 802.3af class ceiling) on a port Teltonika rates 802.3af/at up to 21 W.

What the vendor says

devices/teltonika/otd140.json - flyer v1.8 (2024), https://download.kamami.pl/p1207980-otd140-flyer-2024-v18.pdf (200, application/pdf, 967,315 B, text layer):

  • "Ethernet 2 x RJ45 ports, 10/100 Mbps: 2 x ETH ports (can be configured as WAN)"
  • "Powering options (PoE In) RJ45, PoE In: 802.3af/at (42.5 - 57 VDC, max 21W)"
  • "PoE Out: 802.3af (42.5 - 57 VDC, max 15W) Alternative B"
  • "Power consumption Idle: < 2.5 W / Max: < 6 W / PoE Max < 21 W"

https://wiki.teltonika-networks.com/view/OTD140_Powering_Options (200, 57,164 B): "802.3af/at for the PD (Powered Device) port and 802.3af standard for the PSE (Power Source Equipment) port", 42.5-57.0 V, Mode B pinout (DC+ 4/5, DC- 7/8).

devices/teltonika/otd144.json - datasheet v1.22 (2026-09-24), https://solwise.co.uk/downloads/files/Datasheet_OTD144_06-10-2026.pdf (application/pdf, text layer): "1 x PoE In" / "802.3af/at"; "1 x PoE Out" / "802.3af Alternative B" / "15 W Max (power supply unit dependent)"; same "< 2.5 W / < 6 W / PoE Max < 21 W". Wiki https://wiki.teltonika-networks.com/view/OTD144_Powering_Options (200, 63,454 B) repeats the af/at PD - af PSE split.

The two numbers agree with each other: 21 W in, 6 W of router, 15 W out.

What changed

  • eth1 (inlet): poeIn 12.95 -> 21 - the vendor's "max 21W" inlet and its "PoE Max < 21 W" consumption row, not the 802.3af class ceiling.
  • eth2 (outlet): poeOut: true -> 15, poeOutClass PoE+ -> PoE (802.3af). No current Teltonika document claims 802.3at for the PSE port.
  • New poe block: budgetW: 15, standard: "802.3af", vendor sourceUrl and a note carrying the quotes, the Mode B pinout and the revision drift (flyer/datasheet v1.6 printed "802.3af/at ... max 24W", superseded by v1.8's 802.3af / 15 W).
  • OTD144's dead sourceUrl (Mouser answers 200 with 13,897 bytes of text/html - a landing page) replaced with the vendor wiki.

Effect: poeDraw() no longer bills either outlet 1 W, and show power inline can name a ceiling - budget 15 W, source "research" on both.

Not modelled

The "power supply unit dependent" condition: a 15.4 W 802.3af upstream cannot make 15 W appear at eth2, and the catalogue has no field for that; it is stated in the poe note instead.

Gates

node scripts/syntax-check.js 541 files OK; node scripts/audit-port-types.js 0 offending; node scripts/audit-devices.js 0 hard defects; node scripts/check-control-bytes.js clean; node test/hardware-invariants.test.js 26 passed; node test/poe.test.js 21 passed; node scripts/regen-registry-doc.js reports the registry current. node scripts/audit-poe-budget.js silent list 12 -> 10.

Refs #130 (the Dream Wall Pro request this stream is blocked on; this PR does not close it) Two silent PoE boxes in the Teltonika OTD family, both with the same defect: an outlet declared `poeOut: true` with `poeOutClass: "PoE+"` (802.3at) and no wattage, and an inlet declared `poeIn: 12.95` (the 802.3af class ceiling) on a port Teltonika rates 802.3af/at up to 21 W. ## What the vendor says `devices/teltonika/otd140.json` - flyer v1.8 (2024), https://download.kamami.pl/p1207980-otd140-flyer-2024-v18.pdf (200, application/pdf, 967,315 B, text layer): - "Ethernet 2 x RJ45 ports, 10/100 Mbps: 2 x ETH ports (can be configured as WAN)" - "Powering options (PoE In) RJ45, PoE In: 802.3af/at (42.5 - 57 VDC, max 21W)" - "PoE Out: 802.3af (42.5 - 57 VDC, max 15W) Alternative B" - "Power consumption Idle: < 2.5 W / Max: < 6 W / PoE Max < 21 W" https://wiki.teltonika-networks.com/view/OTD140_Powering_Options (200, 57,164 B): "802.3af/at for the PD (Powered Device) port and 802.3af standard for the PSE (Power Source Equipment) port", 42.5-57.0 V, Mode B pinout (DC+ 4/5, DC- 7/8). `devices/teltonika/otd144.json` - datasheet v1.22 (2026-09-24), https://solwise.co.uk/downloads/files/Datasheet_OTD144_06-10-2026.pdf (application/pdf, text layer): "1 x PoE In" / "802.3af/at"; "1 x PoE Out" / "802.3af Alternative B" / "15 W Max (power supply unit dependent)"; same "< 2.5 W / < 6 W / PoE Max < 21 W". Wiki https://wiki.teltonika-networks.com/view/OTD144_Powering_Options (200, 63,454 B) repeats the af/at PD - af PSE split. The two numbers agree with each other: 21 W in, 6 W of router, 15 W out. ## What changed - `eth1` (inlet): `poeIn` 12.95 -> **21** - the vendor's "max 21W" inlet and its "PoE Max < 21 W" consumption row, not the 802.3af class ceiling. - `eth2` (outlet): `poeOut: true` -> **15**, `poeOutClass` `PoE+` -> **`PoE`** (802.3af). No current Teltonika document claims 802.3at for the PSE port. - New `poe` block: `budgetW: 15`, `standard: "802.3af"`, vendor `sourceUrl` and a note carrying the quotes, the Mode B pinout and the revision drift (flyer/datasheet v1.6 printed "802.3af/at ... max 24W", superseded by v1.8's 802.3af / 15 W). - OTD144's dead `sourceUrl` (Mouser answers 200 with 13,897 bytes of text/html - a landing page) replaced with the vendor wiki. Effect: `poeDraw()` no longer bills either outlet 1 W, and `show power inline` can name a ceiling - budget 15 W, source "research" on both. ## Not modelled The "power supply unit dependent" condition: a 15.4 W 802.3af upstream cannot make 15 W appear at `eth2`, and the catalogue has no field for that; it is stated in the `poe` note instead. ## Gates `node scripts/syntax-check.js` 541 files OK; `node scripts/audit-port-types.js` 0 offending; `node scripts/audit-devices.js` 0 hard defects; `node scripts/check-control-bytes.js` clean; `node test/hardware-invariants.test.js` 26 passed; `node test/poe.test.js` 21 passed; `node scripts/regen-registry-doc.js` reports the registry current. `node scripts/audit-poe-budget.js` silent list 12 -> 10.
poe(teltonika): the OTD140 and OTD144 outlets are 802.3af at 15 W, and the inlet takes 21
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 1m2s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Test (Node 18) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 3s
c94d5ab2b8
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 16:56:41 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 17:00:35 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 17:00:36 +00:00
Author
Owner

Blocked: collides with #2452 on devices/teltonika/otd140.json — needs Jay's decision.

#2452 (rev loop, 407e01f8) and this PR are both green and both clean into eab52764, but they are the same device from two different documents:

git merge-tree --write-tree tmpcheck2453 tmpcheck2452
CONFLICT (content): Merge conflict in devices/teltonika/otd140.json

Common ground: eth2 → poeOut: 15, poeOutClass: "PoE", poe.budgetW: 15, 802.3af Alternative B, 15 W at the PSE; the old poeOut: true + "PoE+" was wrong on both sides.

Fork:

  • eth1 poeIn — this PR sets 21 (flyer v1.8 "PoE In: 802.3af/at … max 21W"), from 12.95. #2452 keeps 12.95 and argues the 802.3af/at class is what belongs in poeIn.
  • Sources — this PR: flyer v1.8 (2024) + wiki OTD140_Powering_Options; #2452: datasheet v1.20 (2026-07-24).
  • This PR also carries devices/teltonika/otd144.json (which #2452 explicitly leaves untouched); #2452 carries a new test/otd140-poe-out.test.js that this PR does not.

Decision required (behaviour, not merge text, so I am not resolving it): does poeIn hold the PD class draw or the inlet ceiling? A 21 W inlet already includes the 6 W router plus the 15 W the outlet passes on, and the engine budgets each PSE independently — so poeIn: 21 next to poeOut: 15 may double-count unless the two ports are coupled.

Nothing merged, nothing rebased. If #2452 lands first this branch needs a rebase and a re-read of the otd140 hunk.

**Blocked: collides with #2452 on `devices/teltonika/otd140.json` — needs Jay's decision.** #2452 (rev loop, `407e01f8`) and this PR are both green and both clean into `eab52764`, but they are the same device from two different documents: ``` git merge-tree --write-tree tmpcheck2453 tmpcheck2452 CONFLICT (content): Merge conflict in devices/teltonika/otd140.json ``` Common ground: eth2 → `poeOut: 15`, `poeOutClass: "PoE"`, `poe.budgetW: 15`, 802.3af Alternative B, 15 W at the PSE; the old `poeOut: true` + `"PoE+"` was wrong on both sides. Fork: - **eth1 `poeIn`** — this PR sets `21` (flyer v1.8 "PoE In: 802.3af/at … max 21W"), from `12.95`. #2452 keeps `12.95` and argues the 802.3af/at *class* is what belongs in `poeIn`. - **Sources** — this PR: flyer v1.8 (2024) + wiki `OTD140_Powering_Options`; #2452: datasheet v1.20 (2026-07-24). - This PR also carries `devices/teltonika/otd144.json` (which #2452 explicitly leaves untouched); #2452 carries a new `test/otd140-poe-out.test.js` that this PR does not. Decision required (behaviour, not merge text, so I am not resolving it): **does `poeIn` hold the PD class draw or the inlet ceiling?** A 21 W inlet already includes the 6 W router plus the 15 W the outlet passes on, and the engine budgets each PSE independently — so `poeIn: 21` next to `poeOut: 15` may double-count unless the two ports are coupled. Nothing merged, nothing rebased. If #2452 lands first this branch needs a rebase and a re-read of the otd140 hunk.
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 17:08:55 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 17:10:23 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 17:30:49 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 17:30:49 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 17:38:53 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 17:38:54 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 17:40:04 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 17:40:05 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 17:41:26 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:08:54 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:10:13 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:10:13 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:11:16 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:11:16 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:30:51 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:30:51 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 18:39:43 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 18:39:43 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 19:02:57 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 21:01:29 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 22:01:59 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 22:31:19 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 23:01:34 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 23:01:44 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-21 23:32:21 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 00:32:30 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 01:02:41 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 02:31:11 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 03:01:04 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 03:01:05 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 04:01:58 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 06:02:27 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 06:30:53 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 08:02:47 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 08:30:54 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 09:01:39 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 09:31:00 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 09:31:00 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 10:30:59 +00:00
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-22 11:02:12 +00:00
forgejo-actions canceled auto merging this pull request when all checks succeed 2026-11-22 11:31:00 +00:00
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 1m2s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Test (Node 18) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 3s
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-1652:catalogue/1121-1652
git switch catalogue/1121-1652
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!2453
No description provided.