Running power and data over a single Ethernet cable sounds simple enough. But when you're designing an IoT device that needs to sip power from PoE while staying reliable across temperature swings, firmware updates, and weird cable runs — the details get tricky fast.
I've designed a handful of PoE-powered sensors and controllers, and the same problems keep showing up. Under-budgeting power. Forgetting about cable loss. Picking the wrong PoE class. Let's walk through the real design considerations so you can get it right the first time.
Why PoE for IoT?
If you're building smart home gear, industrial sensors, or building automation nodes, PoE solves two problems at once: power delivery and network connectivity. No need to run separate power lines or deal with battery replacement cycles.
Where PoE makes the most sense for IoT:
- Building automation — temperature sensors, occupancy detectors, air quality monitors mounted in ceilings where power outlets don't exist
- Industrial sensors — vibration monitors, pressure transducers, flow meters spread across a factory floor
- Security cameras — the classic PoE use case, but increasingly with on-device AI inference
- Access control — badge readers, electronic locks, intercoms
- Smart lighting controllers — DALI gateways, PoE-powered LED drivers
The key advantage: your device gets both power and a wired network backhaul. No Wi-Fi reliability headaches, no battery charging circuits, no Bluetooth range anxiety.
Understanding PoE Standards for IoT
Not all PoE is created equal. The IEEE has evolved the standard over the years, and picking the right one depends on your device's power needs.
| Standard | IEEE | Max PSE Output | Max PD Power | Typical Use |
|---|---|---|---|---|
| PoE | 802.3af | 15.4W | 12.95W | Sensors, basic cameras |
| PoE+ | 802.3at | 30W | 25.5W | PTZ cameras, displays |
| PoE++ Type 3 | 802.3bt (Type 3) | 60W | 51W | Multiple radios, small servers |
| PoE++ Type 4 | 802.3bt (Type 4) | 90W | 71.3W | Smart lighting, laptops |
Most IoT devices land squarely in 802.3af territory. A temperature sensor with an MCU, an Ethernet PHY, and maybe a small radio draws 1–3W. Even a sensor with a small display typically stays under 10W.
The question isn't "which standard gives me the most power?" It's "which standard lets me use the cheapest PSE equipment while still having headroom?"
PoE Classes and Your Power Budget
PoE uses a classification system so the Power Sourcing Equipment (PSE) knows how much power to allocate. This matters because switches have a total power budget — a 24-port PoE switch with a 370W budget can't deliver 15.4W on every port simultaneously.
| Class | Power Range (PD) | Max PSE Allocation | Your Device Draw |
|---|---|---|---|
| 0 | 0.44–12.95W | 15.4W | Default — use when unsure |
| 1 | 0.44–3.84W | 4.0W | Low-power sensors |
| 2 | 3.84–6.49W | 7.0W | Sensors + radio |
| 3 | 6.49–12.95W | 15.4W | Sensors + display |
| 4 | 12.95–25.5W | 30.0W | PoE+ devices |
Here's the practical tip: if your IoT device draws 2W, declare Class 1. The switch will only reserve 4W for your port instead of 15.4W. On a 24-port switch, that's the difference between supporting 24 devices versus maybe 12.
Let's work through a real example.
Example: Smart Temperature + Humidity Sensor
Components and typical power draw:
| Component | Quiescent | Active | Notes |
|---|---|---|---|
| MCU (STM32L4) | 1.5µA | 15mW | Low-power ARM Cortex-M4 |
| Ethernet PHY (DP83848) | — | 150mW | Always on when linked |
| PoE PD controller (TPS2378) | — | 10mW | Conversion losses included |
| Temp/humidity sensor (SHT40) | 0.4µA | 5mW | Polled every 30 seconds |
| Status LED | — | 60mW | Blinking, 50% duty cycle |
| DC-DC conversion losses (85% eff) | — | ~40mW | 3.3V buck from 48V |
Total active power: 15 + 150 + 10 + 5 + 60 + 40 = 280mW (0.28W)
That's comfortably within Class 1 (0.44–3.84W). With headroom, we'd budget about 0.5W worst-case.
Now account for cable loss. At 0.5W load on 48V, the current is only ~10mA. Over 100 meters of Cat5e (about 10Ω round-trip per pair), that's a voltage drop of 0.1V. Negligible. But if you were drawing 10W, the story changes — you'd lose about 2V in the cable, which is still within spec but worth accounting for.
The PD Controller Is Your Best Friend
The Powered Device (PD) controller handles negotiation with the PSE. It does the classification signature, inrush current limiting, and under-voltage lockout. Don't try to roll your own — use a dedicated IC.
Popular PD controllers for IoT:
- TI TPS2378 — IEEE 802.3af, low external component count, good app notes
- TI TPS2379 — Adds auxiliary power ORing for designs with backup power
- Silicon Labs Si3402 — Integrated DC-DC, tiny footprint, great for space-constrained designs
- Microchip PD70201 — 802.3bt capable, good for higher-power IoT edge devices
The PD controller typically feeds a flyback or buck converter that steps 48V down to your system voltage (3.3V or 5V). Efficiency matters here because losses at 48V mean heat in a small enclosure.
DC-DC Design Tips for PoE IoT
- Target >85% efficiency at your typical load, not just at full load. Many converters look great at 80% load but tank at 5% load where your IoT device spends most of its time.
- Use a buck converter for single-voltage systems. A simple buck from 48V to 3.3V is more efficient and smaller than a flyback.
- Check no-load quiescent current. If your MCU sleeps 99% of the time, the DC-DC quiescent current dominates your power budget. Look for converters with IQ < 100µA.
- Input capacitor selection matters. You need enough input capacitance to handle the PD controller's inrush current limit without drooping below the UVLO threshold.
Cable Considerations for IoT Deployments
Cable quality matters more than most people think, especially in industrial environments.
Cat5e vs Cat6 vs Cat6a for PoE IoT:
| Spec | Cat5e | Cat6 | Cat6a |
|---|---|---|---|
| Max distance (PoE) | 100m | 100m | 100m |
| Conductor gauge | 24 AWG | 23 AWG | 22-23 AWG |
| DC resistance (per pair) | ~9Ω/100m | ~7.5Ω/100m | ~6Ω/100m |
| Cost premium | Baseline | +20% | +50% |
For low-power IoT devices under 3W, Cat5e is fine. The voltage drop is negligible. But if you're running higher-power devices or bundling many cables in a conduit (which adds thermal resistance), step up to Cat6.
Heat rise in cable bundles is covered by TIA TSB-184-A. When you bundle more than 24 PoE cables together, the cables in the center can't dissipate heat effectively. This increases resistance, which increases voltage drop, which means your device gets less power. Derate your maximum cable length by 10-20% for large bundles.
Industrial IoT: Rugged Design Considerations
Industrial environments add another layer of complexity.
Temperature: Industrial PoE sensors might see -40°C to +85°C. Your DC-DC converter and PD controller need to be rated for extended temperature. The capacitor derating curve is your enemy — a ceramic capacitor that's 10µF at 25°C might be 5µF at -40°C.
EMC: IEEE 802.3 specifies isolation requirements. Your Ethernet magnetics (either discrete transformers or integrated in the RJ45 jack) provide galvanic isolation. Don't skip the common-mode choke — it's what keeps your sensor from becoming an antenna for factory floor EMI.
Surge protection: Add TVS diodes on the PoE input. IEC 61000-4-5 is the relevant surge immunity standard for industrial environments. A lightning strike on a cable tray a few meters away can induce thousands of volts on your Ethernet pairs.
Practical surge protection for PoE input:
- TVS diode array on the center-tap of each pair (before the PD controller)
- Series resistors or PTC fuses for current limiting
- Keep the TVS as close to the RJ45 jack as physically possible
Power Budget Spreadsheet: A Worked Example
Let's say you're designing an industrial air quality monitor with PoE. Here's how to think about the power budget:
| Stage | Power | Notes |
|---|---|---|
| Ethernet PHY | 180mW | Always active |
| MCU (ESP32-S3) | 240mW | Wi-Fi + processing |
| Gas sensors (x3) | 150mW | Warm-up + measurement |
| Fan (air sampling) | 500mW | Runs continuously |
| Status LEDs | 100mW | Indicators |
| DC-DC (85% eff) losses | 175mW | 5V/1.2W load at 85% |
| Total at PD input | ~1.3W | Well within 802.3af |
Even with margin for startup transients and cold-temperature operation, this is a ~2W device. Class 1 allocation (4W) gives 100% headroom. A Class 1 device on a 370W switch can run on all 24 ports simultaneously with power to spare.
Common Design Mistakes
I've seen (and made) these errors more times than I'd like to admit:
-
Not accounting for startup inrush. Your bulk capacitors charge through the PD controller's inrush limiter, but if the limit is set too high, the PSE might cut power. Check your PD controller's inrush setting against your total input capacitance.
-
Forgetting about thermal derating. At 70°C ambient, your DC-DC converter's efficiency drops, and the cable resistance increases. Run your power budget at the worst-case temperature, not at room temp.
-
Using the wrong classification. If your device draws 3.5W and you leave it at Class 0, the switch reserves 15.4W for you. On a dense deployment, you'll run out of switch budget way before you should.
-
Skipping the common-mode choke. Your design passes EMC in the lab. Then you deploy it next to a VFD on a factory floor and get constant link drops. The CMC costs $0.30. Use it.
-
Not testing with long cables. Everything works on a 1-meter patch cord. Deploy with a 90-meter run through a ceiling plenum at 50°C, and suddenly your undervoltage lockout trips randomly. Test with 100m cable at temperature.
Tools and Resources
- IEEE 802.3af/at/bt — The actual standards. Dense reading but the source of truth.
- TI Application Note AN-2132 — "PoE PD Design Considerations" — practical guide with real component values
- TIA TSB-184-A — Guidelines for PoE cable bundle thermal management
- IEC 61000-4-5 — Surge immunity testing for industrial environments
- Silicon Labs AN1363 — "PoE Powered Device Design Guide" — good for space-constrained IoT
Quick Reference: PoE IoT Design Checklist
- Calculate worst-case power draw (all peripherals active, cold temperature)
- Add 20% margin for component variation and aging
- Select appropriate PoE class (minimize switch power reservation)
- Verify cable voltage drop at maximum length and temperature
- Choose PD controller rated for your temperature range
- Design DC-DC for efficiency at typical load (not just full load)
- Include TVS surge protection on PoE input
- Add common-mode choke on Ethernet lines
- Test with 100m cable at temperature extremes
- Verify inrush current doesn't trip PSE limits
Want to skip the manual voltage drop math? Try the PoE Power Budget Planner — it handles cable gauge, distance, power class, and thermal derating automatically, then gives you a downloadable PDF report for your design documentation.