Power over Ethernet for Maker Electronics: Passive vs 802.3af/at/bt, Splitting and Injecting PoE

Running power to a remote ESP32 sensor node, a security camera, or a shop monitoring station usually means either a battery you'll have to recharge or an ugly extension cord run. Power over Ethernet solves both problems by carrying DC power over the same cable that carries your data, which means one cable run instead of two and no battery maintenance schedule. This guide covers how PoE actually works electrically, the standards you'll run into, and how to add PoE to a custom ESP32 or Raspberry Pi build that wasn't designed for it out of the box.

Passive PoE vs. the 802.3 Standards

"PoE" covers two genuinely different things, and mixing them up can destroy equipment.

TypeHow it worksRisk Passive PoEA fixed DC voltage (commonly 12V, 24V, or 48V) is simply placed on unused wire pairs — no negotiation, no detectionPlugging a passive PoE injector into a device that doesn't expect it (or a standards-compliant PoE device) can deliver the wrong voltage and damage the port 802.3af (PoE)Detects a valid powered device via resistance signature before energizing the line; delivers up to 15.4W at the source (~12.95W at the device)Safe — will not power a non-PoE device 802.3at (PoE+)Same detection scheme, higher power budget — up to 30W at the source (~25.5W at the device)Safe, same detection handshake 802.3bt (PoE++/4PPoE)Uses all four pairs instead of two; up to 60W (Type 3) or 90-100W (Type 4) at the sourceSafe, backward compatible with af/at devices

The standards-based versions negotiate before applying voltage specifically so that a non-PoE Ethernet device — a plain switch port, a laptop NIC — never sees power on the line. Passive PoE skips that negotiation, which is why passive injectors and passive-PoE cameras/access points must be matched carefully: never plug a passive 24V injector into a device that expects 802.3af, and never plug an 802.3af switch port output into wiring you've assumed is passive.

Getting Power Onto (and Off) the Cable

Standard Ethernet uses four twisted pairs. 10/100 Mbps only uses two of them for data, leaving the other two pairs completely free to carry DC power — this is how older PoE injectors work on Fast Ethernet runs. Gigabit and faster use all four pairs for data, so 802.3at/bt PoE instead superimposes DC on top of the data pairs using center-tapped transformers, which is transparent to the data signal as long as your switch or injector is genuinely spec-compliant.

Injector: sits between a non-PoE switch and the device, adding power to an otherwise plain Ethernet run. The simplest way to add PoE to an existing non-PoE network.
PoE switch: a switch with PoE built into some or all ports, negotiating and delivering power per-port. Cleanest option for a shop or home network being built from scratch.
Splitter: sits at the far end of a PoE-powered cable run and separates the power back out to a barrel jack or screw terminals, alongside a plain Ethernet cable for the data. This is the piece most relevant to powering a custom microcontroller build — it lets you feed a device that has no PoE circuitry of its own.

Powering an ESP32 or Raspberry Pi from PoE

Three approaches, in order of increasing integration:

External splitter, dumb device. Cheapest and easiest: a $10-15 PoE splitter converts the incoming 48V PoE to 5V or 12V via a small buck converter, and you feed that output straight into your ESP32 dev board's 5V pin or a Raspberry Pi's USB-C/micro-USB input. No PoE-aware circuitry needed on your board at all.
PoE HAT (Raspberry Pi specific). The official Raspberry Pi PoE+ HAT and third-party equivalents (like the W5500-based Ethernet+PoE boards) handle detection and buck conversion on a board that stacks directly onto the Pi's GPIO header, giving you PoE without any external splitter box.
Onboard PoE PD circuitry. For a custom PCB — an ESP32 project with a W5500 or similar Ethernet controller — you can design in a PoE powered-device (PD) controller IC (parts like the TI TPS2378 or Silicon Labs Si3402 are common choices) that handles the detection handshake and feeds a buck regulator directly on your board. This is the right approach for a permanently wall- or ceiling-mounted sensor node where you want one cable and no external boxes.

For a wired ESP32 sensor node — the kind covered in this site's guide to W5500 Ethernet ESP32 nodes — PoE is the natural pairing: you already need a network cable for reliable uptime, and adding power to that same cable means the node needs nothing else but a mounting bracket and an antenna, if it has one.

Safety Notes

802.3bt Type 4 can deliver up to 90W at the source — enough to matter if you're working on live cabling. Treat PoE runs like low-voltage DC power, not "just Ethernet": disconnect the switch port or injector before working on wiring, don't assume a cable is unpowered just because it's thin, and never mix passive PoE injectors from different vendors without confirming voltage and polarity match, since reversed polarity on non-standard passive gear is a real way to release the magic smoke from an otherwise perfectly good board.

Choosing an Approach

For a single sensor node or camera, a $12 PoE splitter feeding a stock ESP32 dev board is the fastest path and doesn't require any board design work. For a fleet of nodes across a shop or property, a PoE switch plus PoE HATs (or splitters) at each endpoint scales better than running individual injectors everywhere. Only reach for onboard PD circuitry if you're already laying out a custom PCB for other reasons — it's overkill to design an IC-level PoE input just to avoid a $12 external splitter.

Related Guides

Loading_