Best PoE touch panels for wall controls

PoE (Power over Ethernet) touch panels are appealing for clean wall-mounted controls: one cable in the wall delivers both power and data, no separate outlet or transformer needed. The catch is that genuine PoE touch panels are a smaller category than the marketing suggests. A lot of popular “smart panels” are mains-powered Wi-Fi devices, not PoE, and some are explicitly damaged by PoE. This guide sorts out what really runs over PoE and works locally with Home Assistant.

What Actually Counts as a PoE Local Panel

For a local-first wall panel you want three things: it draws power and data over a single Ethernet run (true PoE, or PoE + a small splitter), it can display and control Home Assistant without depending on a vendor cloud, and it stays responsive on the LAN even when the internet is down.

In practice, the panels that meet all three fall into two camps:

1. Android “86-type” PoE wall panels that you run as a kiosk pointed at a Home Assistant dashboard.
2. DIY ESP32 panels flashed with ESPHome, powered via a PoE splitter or a PoE-capable ESP32 board.

Crucially, a panel being “smart” does not make it PoE, and many touchscreen smart switches are mains-wired, not Ethernet-powered. Check the spec sheet for an RJ45 jack and an explicit PoE rating before you buy.

Best Practical Option: Android PoE Wall Panel as a Kiosk

The most reliable off-the-shelf PoE panels today are generic Android in-wall touch panels designed for the 86-type electrical box, sold with a PoE variant. The good ones use a modern Rockchip SoC (RK3566 or the newer RK3576S; avoid the older RK3288, which struggles with rich dashboards), run stock-ish Android, and accept power and data over a single Ethernet cable.

Because they run plain Android, you install Fully Kiosk Browser (or a similar kiosk app) and point it at your Home Assistant dashboard URL. That gives you a fully local wall controller: the panel renders your real HA dashboard, the controls hit Home Assistant directly on the LAN, and nothing depends on a manufacturer cloud. Fully Kiosk also exposes screen, motion, and sensor data back to Home Assistant via its REST/MQTT integration, so the panel can wake on approach and dim on a schedule.

Tradeoffs: these are commodity devices, so build quality and screen brightness vary, and you’re responsible for locking down the Android side. But for a true PoE, cloud-free wall dashboard, this is the most dependable route.

DIY: ESP32 Panel + ESPHome + PoE

If you want a small, purpose-built panel rather than a tablet, an ESP32-based display flashed with ESPHome is the most local option there is. ESPHome panels appear in Home Assistant as native devices over the local API (no MQTT broker required, though MQTT is optional), and recent ESPHome releases have solid LVGL UI support for building touch controls.

The honest caveat on PoE here: most hobby ESP32 display boards are USB/5V powered, so to make one PoE you add an inexpensive PoE splitter (it takes PoE in, outputs 5V to the board) or use an ESP32 board with an onboard PoE module. It’s a DIY project, not a plug-and-play appliance, but the result is a fully local, ESPHome-native panel.

A relevant clarification: the original Sonoff NSPanel is the ESP32 model you can flash with ESPHome, but it is not PoE (it’s a mains-wired smart switch panel). And despite the similar name, the SONOFF NSPanel Pro is a completely different device — it runs Android on a Rockchip chip with built-in Zigbee, is not ESP32, cannot be flashed with ESPHome, and is not PoE (it’s Wi-Fi, mains-powered). If you see the NSPanel Pro recommended as a PoE/ESPHome panel, that’s wrong on every count. You can, however, use the NSPanel Pro’s Android side as a Wi-Fi kiosk if PoE isn’t a requirement.

Non-PoE Wall Controls Worth Knowing

If you don’t strictly need PoE, a couple of solid local wall controllers are worth a mention so you don’t force a panel into the wrong job:

• The Aqara Scene Panel S1 is a Zigbee 3.0 touch scene panel. It’s a hardwired, neutral-required smart switch (not PoE), and it pairs directly to any Zigbee coordinator (ZHA or Zigbee2MQTT) with no Aqara hub required for local control; once paired it integrates with Home Assistant through Zigbee. Good if you’re already in Aqara/Zigbee, but it’s a wall switch, not a dashboard tablet.
• The Zooz ZEN32 Scene Controller isn’t a touchscreen at all — it’s a hardwired 120 VAC Z-Wave 800 scene controller with five physical buttons. It is not PoE and not USB-powered; it replaces an in-wall switch and is line-powered. It pairs locally to Home Assistant via Z-Wave JS and is excellent if you prefer tactile buttons over a screen.

What to Avoid

Avoid panels that need a vendor cloud to render their UI or run automations; they fail exactly when your internet does. Common offenders are Tuya-ecosystem panels: the Tuya T6E (and its many rebrands), for example, is an Android Zigbee-gateway panel that is Wi-Fi and mains-powered, not PoE — its own manual warns that connecting PoE will damage it. It can be coaxed toward local control with the Local Tuya integration, but it isn’t a clean PoE local panel.

Also skip any panel that only exposes proprietary cloud endpoints with no local API or kiosk capability. If you can’t point it at a Home Assistant dashboard or pair it over Zigbee/Z-Wave/ESPHome locally, you’re locked into the vendor.

Quick Verdict

For a true PoE wall dashboard that runs locally, the most reliable choice is a modern Android 86-type PoE panel (RK3566/RK3576S) running Fully Kiosk pointed at Home Assistant. For a hand-built, fully-local panel, an ESP32 + ESPHome display with a PoE splitter is the purist option. If PoE isn’t actually a hard requirement, a hardwired Zooz ZEN32 (buttons) or Aqara Scene Panel S1 (Zigbee touch) gives you reliable local wall control. Whatever you choose, confirm the RJ45/PoE rating on the spec sheet first — and don’t mistake the Wi-Fi, mains-powered NSPanel Pro or Tuya T6E for PoE devices.