Building the Ideal Network for DisplayHUB
Wired Pis, one private network, and strong WiFi where you need it—the recipe for a fast, reliable DisplayHUB system.
Your DisplayHUB network is the backbone of the entire system.
DisplayHUB is free to install and runs on standard Raspberry Pi hardware for both the controller and encoders. You can start with off-the-shelf Raspberry Pis from normal retail channels, so if it doesn’t work out in your environment, the hardware is easy to repurpose or return.
DisplayHUB is the first and only system of its kind that offers a true TV matrix over WiFi on smart TVs. You can route any source to any display, change layouts on the fly, and keep everything simple without needing dedicated HDMI matrices or special set-top boxes at every screen.
Wired Ethernet is always the best option for maximum stability, the lowest latency, and the tightest sync. Plan on wiring the controller and every encoder. Ethernet is required on first boot, and each TV pulls its own copy of the stream straight from the encoder, so an encoder’s traffic grows with every screen watching it. Your TVs can be wired or wireless—most small and medium venues run them very well on a well-designed WiFi 6 or WiFi 7 network.
First Boot Must Be Wired
Plug every Pi—the controller and each encoder—into your network with an Ethernet cable before you power it on for the first time. A freshly flashed Pi doesn’t know your WiFi yet, and it needs internet access to activate its DisplayHUB software on first boot. Already powered one on without the cable? Plug it in, then restart the Pi by unplugging its power for a few seconds. After that, stay wired (recommended) or move it to your WiFi from your browser. Full steps are in the Device Setup guide.
IMPORTANT: Keep DisplayHUB off public and guest WiFi.
The DisplayHUB ecosystem is intentionally open inside your private network, so devices can auto-discover and auto-sync with no passwords and no user accounts. That makes it fast and easy to deploy, but it also means anyone on that network can control it. So:
- Never put the controller, encoders, or displays on customer-facing or guest WiFi.
- Do not allow public devices on the same network segment as DisplayHUB.
- Never expose DisplayHUB ports directly to the internet. For remote access, use Tailscale on your router instead of port forwarding.
- When staff leave, change the WiFi password and remove old devices.
Always place DisplayHUB on a private, isolated LAN—either its own VLAN, a staff-only SSID, or a behind-the-scenes wired network that only your equipment can reach.
✓ What Makes a Good DisplayHUB Network?
- Private LAN or VLAN (no guest or customer devices).
- Wired Ethernet for the controller, encoders, and high-priority TVs.
- Internet access (required for each Pi’s first boot, recommended after).
- Strong WiFi 6 or WiFi 7 access points for wireless displays.
- Simple flat network (one LAN or subnet for every DisplayHUB device).
- DHCP reservations (static IPs) for the controller and encoders.
- Wired backhaul for mesh systems when possible.
Start With a Solid Router and Switch
This is the core of your DisplayHUB deployment. Whether you’re using a single router in a small bar or a full rack in a large venue, the foundation should be stable, have open Ethernet ports for your Pis, and be capable of handling many display devices.
Recommended Hardware
- Small system router (easy and reliable): GL.iNet GL-MT6000 (Flint 2), with Tailscale built in for remote access
Amazon - Medium to large system router: Ubiquiti UniFi Express 7, then add access points (below) as you grow
Amazon - Switch: Need more Ethernet ports than your router has? Add a gigabit switch—unmanaged is fine for most venues.
Choose Wired, WiFi, or a Mix of Both
Guidelines
- Wired Ethernet
Best for: the controller, encoders, and mission-critical TVs- Required for every Pi’s first boot
- Zero interference
- Best sync accuracy
- Handles a large number of displays very well
- WiFi 6 or WiFi 7
Best for: TVs where running cable isn’t practical- Great performance when access points are placed well
- Simple deployment with ceiling- or wall-mounted APs
- Add more APs as your system grows
- Mesh WiFi with wired backhaul
Best for: long buildings or multiple floors- Use Ethernet uplinks between mesh nodes
- Avoid wireless backhaul if possible for the best performance
No matter which layout you choose, all DisplayHUB devices—including TVs on WiFi—must be on the same LAN or subnet for auto-discovery and low-latency sync. Make sure the WiFi your TVs join connects to the same network as your wired Pis, not a separate guest or IoT network.
Moving a Pi to WiFi After Setup
We recommend keeping the controller and encoders wired. If a Pi truly can’t be wired and your WiFi is strong, switch it over in your browser after its wired first boot:
- Controller: in the dashboard, open Settings → Controller Wi-Fi, pick your staff network, enter its password, and connect.
- Encoders: click Configure on the encoder’s card, open its Wi-Fi section, enter your network name and password, and click Apply Wi-Fi Settings.
Once the Wi-Fi panel shows it’s connected, unplug the Ethernet cable and restart the Pi (unplug its power for a few seconds). Its IP address will change, so reconnect at http://displayhub.local or look up the new IP in your router (and reserve it). If it can’t join your WiFi, plug the cable back in and restart it. Step-by-step guides: Controller WiFi · Encoder WiFi
Tips and Best Practices
Tips
- Use wired Ethernet for the controller, encoders, and any high-importance TVs.
- Give the controller and encoders DHCP reservations (static IPs). In your router’s client list, their hostnames start with displayhub or raspberrypi.
- Keep DisplayHUB on a private LAN, and keep guest WiFi on a separate SSID or VLAN.
- Turn off client/AP isolation on the WiFi your TVs use.
- Place WiFi access points high and in open areas, not buried in closets.
- Prefer 5 GHz or 6 GHz bands for your DisplayHUB displays.
- Use wired backhaul between mesh or multi-AP nodes whenever you can.
Troubleshooting
- New Pi never shows up: It needs Ethernet and internet on its first boot. Plug in the cable, then restart the Pi.
- Lost the dashboard after switching to WiFi: Restart the Pi, then find its new IP in your router’s client list. Still stuck? Plug Ethernet back in and restart.
- displayhub.local won’t load: Use the controller’s IP address instead, or turn off client/AP isolation on that WiFi.
- Freezing or lag: WiFi signal may be weak or noisy. Move the AP closer or add another AP. Also make sure streaming sticks run on their wall adapter, not the TV’s USB port.
- Slow switching: Confirm encoders and displays are on the same LAN or subnet.
- Pixelation: Often caused by interference or low bandwidth. Go wired or reduce congestion. See encoder bandwidth issues.
- Many displays: Add more access points instead of overloading a single AP.
- Interference: Change the channel or band on your AP and stay off crowded 2.4 GHz.
Need Help Designing or Installing Your Network?
Professional DisplayHUB consulting, installation, and tuning are available.
Whether you’re building a 10-screen pub or a 150-screen sports bar, we can help design and deploy a rock-solid DisplayHUB system:
- Full network and WiFi design.
- Coverage and access point placement planning.
- Hardware recommendations that fit your budget.
- On-site installation in select regions.
- Remote configuration and performance tuning.
- Troubleshooting and optimization of existing networks.
We can help you go from a blank network to a fully working DisplayHUB environment that is fast, reliable, and ready for live events.