Writing · Checklist

Wi-Fi requirements for e-paper signs: an IT checklist

To put battery e-paper signs on a business network, give them a 2.4 GHz SSID with no captive portal, use WPA2 with a pre-shared key unless the vendor confirms 802.1X support, isolate them on their own VLAN with outbound-only HTTPS to the vendor's hosts, size DHCP for devices that reconnect on every wake, and check the signal where each sign will actually hang. The checklist below has eleven items and the reason behind each.

Published 2026-11-14. Written for IT and facilities teams reviewing an e-paper signage pilot. We build battery e-paper signs on ESP32-S3 and E Ink Spectra 6, so where this post describes “our firmware” it is describing our own code; check each item against your vendor’s documentation.

Why battery signs are different from LCD players

An LCD signage player is plugged in and stays on the network all day. A battery e-paper sign is asleep almost all the time. On a schedule, it wakes, joins Wi-Fi, asks the server whether there is new content, downloads it if so, turns the radio off, redraws the panel and goes back to deep sleep. Our firmware gives the Wi-Fi join about 20 seconds before giving up on that wake. Network guidance written for always-on players, like this signage network requirements page, gets the firewall and VLAN parts right, but it does not have to care how long a connection takes. For a battery sign, that is the whole game.

The rule behind most of this checklist: A battery e-paper sign pays for its network on every wake. Make joining fast and boring, and the battery lasts; make it slow or interactive, and it doesn’t. Our battery life table shows how strongly runtime follows the number of wakes per day.

The checklist

ItemWhat to set upWhy
Band2.4 GHz SSID available at every mounting spotESP32-class chips are 2.4 GHz only; band steering can hide the SSID
Captive portalNone on the signage SSID, or the signs' MACs exemptedA headless device cannot click through a sign-in page
Security modeWPA2 with a pre-shared key, unless the vendor confirms 802.1XEnterprise auth is firmware-dependent; ask before the pilot
SegmentationDedicated SSID and/or VLAN for signs, no access to corporate subnetsContains a compromised or misbehaving device
FirewallOutbound TCP 443 to the vendor's hosts, DNS; no inboundGet the exact hostnames from the vendor in writing
DNSExternal names resolve from the signage VLANSplit-horizon DNS can break cloud hostnames
DHCPPool sized for every sign plus spares; reservations if you track by IPSigns reconnect on every wake, not once a day
Signal at the wallSurvey at the actual mounting height, behind glass or metal if relevantWeak signal means retries, and retries cost battery
InventoryA list of MAC address, location and owner per signNeeded for allowlists, portal exemptions and support
Password changesA plan for re-provisioning signs when the PSK rotatesEvery sign holds the old key until someone updates it
Offline behaviorConfirmed: last good content stays on screenAn outage should not blank a hundred signs

2.4 GHz, and only 2.4 GHz

Espressif’s ESP32-S3 datasheet lists “2.4 GHz Wi-Fi (IEEE 802.11b/g/n)”, with 20 and 40 MHz channels in the 2.4 GHz band. Many low-power sign and label products use ESP32-class chips or similar parts, so assume 2.4 GHz only unless the spec sheet says otherwise. Two consequences for IT: the signage SSID must be broadcast on 2.4 GHz at every mounting spot, and band steering must not push or hide it from clients that cannot move to 5 GHz.

Captive portals and guest networks

The most common reason a pilot sign “works in the office and not in the store” is a captive portal. Guest and venue networks often require a click-through or a sign-in page before traffic flows. A sign has no browser and no person in front of it at 6 a.m. when it wakes. Either give signs their own SSID without a portal, or exempt each sign’s MAC address from the portal if your wireless controller supports that. The MAC list you build for this is the same inventory you need for support, so build it once.

Security mode: pre-shared key or 802.1X

Corporate Wi-Fi often uses WPA2- or WPA3-Enterprise (802.1X), where each client authenticates with its own credentials or certificate. Whether a sign can do that is a firmware question, not a chip question, so ask the vendor directly. Our shipping firmware joins a network with an SSID and a pre-shared key and does not implement 802.1X today; adding it would be custom work we scope per project. The common pattern is a dedicated pre-shared-key SSID for signs, on its own VLAN, with the key rotated on a schedule that someone has actually planned for.

Plan the key rotation before you deploy

A sign stores the Wi-Fi credentials it was set up with. If the key rotates and nobody updates the signs, every one of them drops off the network at its next wake and keeps showing its last image. On our signs, the fix is a six-second button hold, which sends the sign back to setup mode so the new key can be entered. On the 13.3-inch build that clears only the Wi-Fi settings and keeps the account pairing; on the 7.3-inch build it is a full reset and the sign is paired again. Either way, a rotation is a visit per sign unless you keep the old SSID up in parallel during the changeover.

VLAN and firewall rules

Put signs on their own SSID and/or VLAN with no route to corporate subnets, and allow only what they need outbound. For most cloud-managed signage that is TCP 443 to the vendor’s hosts plus DNS, and no inbound ports at all. Ask the vendor for the exact hostnames. Ours make outbound HTTPS calls to our API and to our storage provider for image downloads, and in normal operation they do not listen for inbound connections: they sync, render and go back to sleep. They also take the clock from the sync response, so they do not need NTP.

DHCP, DNS and signal at the wall

Provisioning a fleet without a laptop at every sign

Every sign needs Wi-Fi credentials once. How that happens decides how long a rollout takes. On our firmware, a sign with no saved network starts its own setup hotspot, named “8frames-setup-” plus four characters from its MAC address. Joining it from a phone opens a small page with a list of nearby networks and a password field. After it saves, the sign reboots, connects, and shows a QR code and a six-digit code on its own screen that pairs it to an account. Other vendors use Bluetooth apps, QR codes or pre-loaded credentials from the factory; ask which, and time it on one sign before you plan a hundred.

Our firmware falls back to cached images when it cannot reach the network, so an outage leaves the last good content on screen rather than a blank panel. For the rest of the pre-deployment list, see the dev-kit-to-product checklist; for room signs specifically, the ESP32 meeting-room sign guide covers wake schedules. If you are still weighing signs against screens, start with e-paper vs LCD signage, and see the workplace signage use case for what we build.

FAQ

Do e-paper signs work on 5 GHz Wi-Fi?

Most battery e-paper signs built on ESP32-class chips do not. Espressif's ESP32-S3 datasheet lists 2.4 GHz Wi-Fi (IEEE 802.11b/g/n) only. Broadcast the signage SSID on 2.4 GHz, and check that band steering does not hide it from 2.4 GHz-only clients.

Can e-paper signs connect to guest Wi-Fi with a captive portal?

Not reliably. A captive portal expects a person to click through a page in a browser, and a headless sign that wakes, connects and sleeps cannot do that every time. Give signs their own SSID without a portal, or exempt their MAC addresses from the portal if your controller supports it.

Do e-paper signs support WPA2-Enterprise (802.1X)?

It depends on the firmware, so ask each vendor. Our shipping firmware joins networks with an SSID and a pre-shared key (WPA2-Personal style) and does not implement 802.1X today; enterprise authentication would be custom work. Many sites put signs on a dedicated PSK network on an isolated VLAN instead.

What firewall ports do e-paper signs need?

Usually outbound HTTPS (TCP 443) to the vendor's servers plus DNS, and nothing inbound. Our signs make outbound HTTPS calls to our API and to our storage provider for image downloads, and in normal operation they do not listen for inbound connections; they sync, then sleep.

Why does Wi-Fi setup affect e-paper battery life?

Because a battery sign spends most of its energy joining the network. Every scheduled wake means associate, get an address, fetch, then sleep again. Anything that makes joining slow or flaky, such as weak signal at the mounting spot, a portal or a slow DHCP server, is paid for on every wake.