Appendix C - Sample Configurations
Appendix C – Sample Configurations
Version: 0.1 (Draft)
Written for: ESPixelStick Version 4.x
Last Updated: July 2026
Author: Ernest Horning
Research & Technical Editing: ChatGPT
Appendix Summary
Purpose
This appendix presents several representative ESPixelStick installations ranging from simple single-output controllers to larger multi-output systems.
The examples are intended to demonstrate typical design approaches rather than prescribe exact hardware.
Individual installations should always be adapted to local requirements.
Related Chapters
- Chapter 4 – Hardware Installation
- Chapter 5 – Firmware Installation
- Chapter 6 – Network Configuration
- Chapter 7 – Inputs, Outputs, and Interfaces
- Chapter 8 – Configuration
- Chapter 9 – Pixel Outputs and Wiring
- Appendix A – GPIO Reference Tables
- Appendix B – Controller Hardware Comparison
C.1 Introduction
No single controller configuration is ideal for every application.
The following examples illustrate common design approaches used successfully by hobbyists.
C.2 Example 1 – Single Yard Prop
A small yard prop may require only:
- One ESP8266 or ESP32 controller
- One pixel output
- One power supply
- Wi-Fi connection
Typical applications include:
- Candy canes
- Snowflakes
- Small singing faces
- Window outlines
Advantages
- Inexpensive
- Easy to troubleshoot
- Simple wiring
- Easy replacement
C.3 Example 2 – Medium Prop
A larger prop might include:
- ESP32 controller
- Several hundred pixels
- Multiple power-injection points
- One network connection
Typical applications:
- Large snowflakes
- Arches
- Roof outlines
- Medium matrices
C.4 Example 3 – Multi-Output Controller
Some installations benefit from several outputs on one controller.
Typical characteristics include:
- ESP32 processor
- Multiple pixel outputs
- Shared power distribution
- Central enclosure
- Organized wiring
Applications:
- Megatrees
- Matrixes
- Multiple nearby props
Advantages:
- Fewer controllers
- Central maintenance
- Reduced network traffic
- Simplified enclosure management
C.5 Example 4 – Distributed Wi-Fi Display
Instead of one large controller, many displays use numerous small controllers.
Typical characteristics:
- One controller per prop
- Short pixel cables
- Wi-Fi communication
- Small power supply at each prop
Applications:
- Yard displays
- Widely separated props
- Temporary installations
Advantages:
- Modular
- Easy expansion
- Easy replacement
- Minimal long pixel-data cables
C.6 Example 5 – Ethernet Installation
Where supported by the controller hardware, Ethernet may be preferred.
Typical applications:
- Large centralized controller cabinets
- Permanent installations
- Commercial displays
Advantages:
- Predictable communication
- No radio interference
- Dedicated network links
C.7 Example 6 – Differential Receivers
Large displays sometimes require long distances between the controller and the pixels.
A differential transmitter and receiver pair can extend data over longer cable runs than a direct pixel connection.
Typical applications:
- Large front yards
- Commercial displays
- Campus decorations
- Large matrices
C.8 Example 7 – Stand-Alone Playback
Some ESP32-based systems support stand-alone operation.
A typical system may include:
- ESP32 controller
- Local storage (where supported)
- Power supply
- Pixel outputs
Typical applications:
- Demonstration displays
- Portable displays
- Independent props
C.9 Configuration Comparison
| Configuration | Typical Size | Network | Complexity |
|---|---|---|---|
| Single Prop | Small | Wi-Fi | Low |
| Medium Prop | Medium | Wi-Fi | Low-Medium |
| Multi-Output | Large | Wi-Fi/Ethernet | Medium |
| Distributed | Large | Wi-Fi | Medium |
| Ethernet | Large | Ethernet | Medium |
| Differential | Very Large | Wi-Fi/Ethernet | High |
| Stand-Alone | Small-Large | Optional | Medium |
C.10 Choosing a Configuration
Consider:
- Number of props
- Pixel count
- Cable distances
- Power distribution
- Maintenance
- Future expansion
- Network coverage
- Budget
Engineering Recommendation
Design for next year's display as well as this year's.
Many hobby displays expand every season.
Leaving room for future outputs often saves significant rewiring.
C.11 Engineering Recommendations
✔ Keep controllers close to the pixels.
✔ Keep power cables as short as practical.
✔ Label everything.
✔ Test one configuration before duplicating it.
✔ Document IP addresses and GPIO assignments.
✔ Build modular systems whenever practical.
C.12 Open Research Items
| Status | Item |
|---|---|
| 🟨 | Additional Ethernet examples |
| 🟨 | Expanded stand-alone playback examples |
| 🟨 | Differential receiver hardware examples |
| 🟨 | Future multi-controller synchronization examples |
References
This appendix is based upon:
- ESPixelStick documentation
- General pixel-controller design practices
- Community experience documented on DoItYourselfChristmas.com
Revision History
| Version | Date | Description |
|---|---|---|
| 0.1 | July 2026 | Initial appendix |