# Christmas Pixel Lights — Troubleshooting, FAQ & Glossary

> Australian context. Prices in AUD. Last updated: September 2026.

---

## Part 1: Troubleshooting by Symptom

### 1. Pixels Flickering / Strobing
**Possible causes:** Insufficient power supply, long data runs without signal conditioning, bad ground connection, 3.3V data signal on 5V pixels, noisy power supply, code sending intermittent commands.
**Diagnostic steps:** Check voltage at the pixel end with a multimeter (should be within 10% of rated). Try a shorter run. Test with a different power supply. Check ground continuity between controller and pixels.
**Fix:** Add power injection. Use a logic level shifter (74HCT245) if controller outputs 3.3V (ESP32). Add a 300–500Ω resistor on the data line. Ensure data and ground wires run together (figure-8 or paired cable, not separate loose wires). Add a 1000µF capacitor across power at the first pixel.

### 2. Wrong Colors (RGB vs GRB Ordering)
**Possible causes:** Colour order mismatch between controller/software config and actual pixel IC. WS2812B defaults to GRB; some controllers default to RGB.
**Diagnostic steps:** Set a single pixel to pure red in xLights/WLED. If it shows green, your colour order is wrong.
**Fix:** In WLED: Config → LED Preferences → Color Order (try GRB, RGB, BRG until correct). In xLights: change the colour order in the controller/model settings. No rewiring needed — it's purely a software setting.

### 3. Only First Pixel Lights Up
**Possible causes:** Data signal not passing through first pixel (dead IC), wrong pixel count in config, voltage too low for subsequent pixels, incorrect data pin assignment.
**Diagnostic steps:** Swap the first pixel with a known good one. Check data-out (DOUT) connection on first pixel. Verify pixel count in WLED/xLights matches physical count.
**Fix:** Replace the first pixel if its data-out is dead. Check solder joints on strip or connectors on bullet pixels. If using a "sacrificial" or "null" pixel, ensure it's wired correctly (data-in to data-out, power connected).

### 4. Random Pixels Lighting Up / Garbage Data
**Possible causes:** Data line picking up electrical noise (EMI), data wire too long without signal conditioning, missing ground between controller and pixels, incompatible voltage levels.
**Diagnostic steps:** Shorten data cable to <30cm and test. Add ground wire alongside data wire. Check for nearby interference sources (motors, dimmers, RF transmitters).
**Fix:** Add a 74HCT245 level shifter between controller and first pixel. Keep data wire under 5m or use a null pixel at the start. Run data and ground as a twisted pair. Add 100nF capacitors across power on every 50th pixel (usually built-in on strips).

### 5. Dead Sections in a String
**Possible causes:** One pixel IC has failed and broken the data chain, physical wire break, corrosion on connectors, water ingress.
**Diagnostic steps:** Count pixels from the controller — the dead section starts at the failed pixel. Inspect connectors and solder joints visually. Flex the cable gently to find intermittent breaks.
**Fix:** For bullet/node pixels: unplug the dead pixel and replace it. For strip: cut out the dead section and solder in a replacement. Data passes through each IC sequentially, so one dead IC kills everything after it. WS2815 has a backup data line that can skip one dead pixel.

### 6. Controller Can't Find / Detect Pixels
**Possible causes:** Wrong GPIO pin configured, data wire not connected to the correct output port, pixel type mismatch, power supply not turned on, blown fuse on controller port.
**Diagnostic steps:** Run the controller's built-in test mode (most Falcon/Kulp controllers have this). Check which GPIO pin your data wire is connected to. Verify pixel type setting matches actual hardware.
**Fix:** Match the physical wiring to the controller port configuration. Check and replace blown fuses on the controller board. Ensure the power supply is on and providing correct voltage to both controller and pixels.

### 7. xLights Can't Connect to Controller
**Possible causes:** Controller and PC on different subnets, firewall blocking traffic, wrong IP address, controller not powered on, Ethernet cable faulty.
**Diagnostic steps:** Ping the controller IP from a terminal/command prompt. Check both devices are on the same subnet (e.g., 192.168.1.x). Try a direct Ethernet cable between PC and controller.
**Fix:** Assign static IPs on the same subnet. Disable Windows Firewall temporarily to test. Use the controller's built-in web UI to verify it's responding. Ensure you're using the correct protocol (E1.31/DDP/ArtNet) in xLights controller settings.

### 8. E1.31 (sACN) Packets Not Arriving
**Possible causes:** Multicast traffic blocked by router/switch, universe numbering mismatch, network congestion, WiFi instead of Ethernet, IGMP snooping enabled on switch without querier.
**Diagnostic steps:** Use Wireshark to capture traffic on the network — filter for sACN (port 5568). Check universe numbers match between xLights and controller. Verify multicast is enabled on your switch.
**Fix:** Use unicast instead of multicast (specify controller IP in xLights). Switch to a dedicated show network (separate VLAN or switch). Disable IGMP snooping on unmanaged switches. Use Ethernet, not WiFi, for E1.31 transport — WiFi introduces packet loss and latency above ~10 universes.

### 9. Power Supply Tripping / Overloading
**Possible causes:** Total pixel draw exceeds PSU rating, inrush current at startup, short circuit in wiring, undersized wiring causing excessive load.
**Diagnostic steps:** Calculate total draw: up to 60mA per pixel at full white (WS2812B 5V), though typical use is ~20mA. Measure actual draw with a clamp meter. Check for shorts with a multimeter.
**Fix:** Size PSU to 60mA × pixel count, then add 20% headroom. Use WLED's current limiter feature. Stagger startup (don't power everything simultaneously). Use multiple PSUs and split the load. Fuse each output run individually (5A fuses are common for 12V runs).

### 10. Voltage Drop — Dim / Wrong Colours at End of Run
**Possible causes:** Wire gauge too thin for the current, run too long without power injection, too many pixels on one power feed, 5V pixels on long runs.
**Diagnostic steps:** Measure voltage at the last pixel with a multimeter. Compare to voltage at the first pixel. A drop of >0.5V on 5V pixels will cause visible colour shift (reds go dim, whites turn yellowish).
**Fix:** Inject power at both ends of the run, and every 2–3m for 5V pixels or every 5–10m for 12V pixels. Use heavier gauge wire (16AWG or 14AWG for power runs). Switch to 12V pixels (WS2811) for long runs — they tolerate voltage drop far better. Never run data through power injection points; only inject V+ and GND.

### 11. WLED WiFi Keeps Disconnecting
**Possible causes:** WiFi signal too weak, IP address conflict, ESP8266/ESP32 WiFi sleep mode, interference from pixel data signals, router on 5GHz only (ESP only supports 2.4GHz), power supply instability causing controller resets.
**Diagnostic steps:** Check RSSI in WLED info page (should be >-70dBm). Try connecting with the WLED app to verify discovery. Check router logs for DHCP conflicts.
**Fix:** Assign a static IP in WLED settings. Disable WiFi sleep in WLED (Config → WiFi → Disable WiFi sleep). Move the ESP closer to the access point or add a 2.4GHz AP near the display. For large installs (>500 pixels), use an Ethernet-enabled ESP32 board (QuinLED-Dig-Octa with Ethernet, Olimex ESP32-POE). Ensure NTP, mDNS, and "Emulate Alexa" are disabled if not needed — they can cause instability.

### 12. Pixels Work Inside but Not After Rain
**Possible causes:** Water ingress into connectors, corroded solder joints, moisture in pixel housings, non-waterproof connections exposed to weather.
**Diagnostic steps:** Dry connections with compressed air. Inspect connectors for green corrosion. Test individual sections after drying.
**Fix:** Use IP67-rated pixels and connectors for outdoor use. Apply dielectric grease to all connections before assembly. Seal connections with self-amalgamating tape or heat-shrink with adhesive lining. Elevate all ground-level connections at least 50mm off the ground. Use drip loops on vertical cable runs so water flows away from connectors.

### 13. GFI / RCD Keeps Tripping
**Possible causes:** Moisture in connections (most common), cumulative leakage current from multiple switch-mode power supplies, damaged cable insulation, faulty RCD, overloaded circuit.
**Diagnostic steps:** Unplug everything, reset the RCD. Add items back one at a time to isolate the fault. Test the RCD with a plug-in tester (available at Jaycar ~$25). Check for moisture in all outdoor connections.
**Fix:** Tape all male/female connections with quality electrical tape (3M Scotch 33+ stays flexible in cold). Use IP-rated connection boxes. Run Christmas lights on a dedicated RCD circuit separate from the house. Limit the number of switch-mode PSUs per RCD circuit (each PSU has small inherent leakage; 5+ PSUs can cumulatively exceed the 30mA trip threshold). Consider medical-grade low-leakage PSUs for large installs. In Australia, get an electrician to add a dedicated outdoor circuit with its own RCD/MCB.

### 14. Controller Overheating
**Possible causes:** Insufficient ventilation, direct sun exposure, overloaded output ports, undersized enclosure, ambient temperature (Australian summer can exceed 40°C).
**Diagnostic steps:** Touch-test the controller board and voltage regulators. Check current draw per port against the controller's rated maximum. Measure enclosure internal temperature.
**Fix:** Mount controller in a ventilated weatherproof enclosure with mesh vents (not sealed). Add a small 12V fan. Shade the enclosure from direct sun. Reduce pixel brightness to lower current. Don't exceed the per-port current rating (typically 4–8A per port on Falcon/Kulp controllers).

### 15. FPP Not Playing Sequences
**Possible causes:** FSEQ file format incompatibility, E1.31/DDP output not configured, wrong file path, network misconfiguration, sequence not uploaded correctly.
**Diagnostic steps:** Check FPP status page for errors. Verify the FSEQ file is in the correct directory. Check Channel Outputs page — ensure E1.31/DDP is enabled with correct IPs and universe numbers. Test with FPP's built-in test mode.
**Fix:** Re-export FSEQ from xLights using V2 ZSTD (for FPP) or V2 Uncompressed (for Falcon standalone). Ensure the controller is set to "Active" not "xLights Only" in xLights if FPP needs to send E1.31 to it. Upload sequences via FPP's web UI or use xLights FPP Connect. Verify FPP and controller are on the same network.

### 16. xLights Crashing When Rendering
**Possible causes:** Insufficient RAM, corrupt sequence file, too many effects on one model, GPU driver issues, very large layouts.
**Diagnostic steps:** Check xLights log files (Help → Open Log). Try rendering a single model to isolate the problem. Monitor RAM usage during render.
**Fix:** Close other applications to free RAM. Break large sequences into smaller segments. Update GPU drivers. Use xLights' backup files (.xbkp) to recover from corruption. Increase virtual memory / swap space. On macOS, ensure xLights has full disk access.

### 17. Timing Drift in Music Sync
**Possible causes:** Audio file sample rate mismatch, network latency between FPP master and remotes, audio output device latency, FSEQ frame rate doesn't match sequence.
**Diagnostic steps:** Compare audio playback on the master FPP against a phone recording of the actual show. Check FPP multisync status page for timing offsets. Verify FSEQ was exported at the same frame rate as the sequence (typically 20–50ms).
**Fix:** Use consistent audio formats (44.1kHz 16-bit WAV or MP3). Set all FPP instances to the same time source (NTP or GPS). Use FPP's built-in audio offset adjustment. For multi-player setups, use FPP multisync with one master and all others as remotes. Ethernet only — WiFi adds too much jitter for music sync.

### 18. Pixels Show White Instead of Colours
**Possible causes:** All three colour channels at max (software issue), wrong pixel type configured, data signal corruption causing all-high.
**Diagnostic steps:** Set a single colour in WLED and observe. Check pixel type setting matches hardware.
**Fix:** Correct the pixel type in your controller software. Check for data signal integrity issues (see #4). If using RGBW pixels (SK6812), ensure the software supports the W channel.

### 19. First Few Pixels Are Wrong, Rest Are Fine
**Possible causes:** Null pixel not accounted for in addressing, level shifter consuming first pixel's data, start channel offset incorrect.
**Diagnostic steps:** Count physical pixels and compare to configured count. Check if a null pixel or level shifter is consuming addressing.
**Fix:** Add the null pixel count to your total in xLights/WLED. Adjust the start channel to skip null pixels. Physically verify the null pixel is connected data-in to data-out only (not as part of the display).

### 20. Pixels Work on Test but Not During Show Playback
**Possible causes:** Universe/channel mapping mismatch between xLights and controller, E1.31 output not active during playback, "xLights Only" mode on controller, FSEQ file doesn't include all channels.
**Diagnostic steps:** Use xLights' "Output to Lights" button and verify pixels respond. Compare universe/channel settings in xLights vs the controller's web UI. Check FPP channel outputs are enabled.
**Fix:** Ensure controller is set to "Active" in xLights controller tab. Re-upload outputs to FPP. Verify the FSEQ file was rendered after the latest layout changes. Check that the universe range in the controller covers all your models.

### 21. ESP32/ESP8266 Boot Loops
**Possible causes:** Power supply can't handle inrush current when pixels turn on, GPIO conflict, corrupt firmware, insufficient current for both ESP and pixels simultaneously.
**Diagnostic steps:** Disconnect pixels and see if the ESP boots normally. Monitor serial output via USB for error messages. Check power supply amperage.
**Fix:** Power the ESP from a separate regulated 5V source (not directly from the pixel PSU). Add a large capacitor (1000µF) across the ESP's power input. Re-flash WLED firmware via USB. Use a PSU with soft-start capability.

### 22. Pixels Stuck on One Colour / Not Responding to Commands
**Possible causes:** Data line disconnected but power still connected, controller crashed, WiFi disconnected (WLED defaults to last state), sequence stopped but "force output" still on.
**Diagnostic steps:** Access the controller's web UI. Check if WLED/FPP is still running. Verify data line continuity.
**Fix:** Power cycle the controller. Reconnect data lines. In WLED, set "Turn LEDs off after" timeout. Check FPP isn't still transmitting idle data (disable "Always transmit channel data").

### 23. Smoke / Burnt Smell from Pixels or Controller
**Possible causes:** Reverse polarity connection, voltage mismatch (12V to 5V pixels), short circuit, overloaded controller port.
**Diagnostic steps:** Immediately disconnect power. Inspect for burnt components. Check wiring polarity. Verify voltage matches pixel rating.
**Fix:** Replace damaged components. Double-check all polarity before reconnecting. Use inline fuses (5A for 12V, 10A for 5V runs). Never connect 12V to WS2812B (rated 3.5–5.3V) — it will destroy them instantly. Test with a multimeter before powering up new installations.

### 24. Intermittent Blackouts on Entire Display
**Possible causes:** Loose mains connection, RCD tripping and auto-resetting, timer malfunction, power supply thermal shutdown, controller crash.
**Diagnostic steps:** Set up a camera to record the display overnight. Check RCD position after each blackout. Monitor PSU temperature. Check FPP/WLED logs for crash reports.
**Fix:** Tighten all connections. Add an RCD with indicator light so you can see trips. Use a UPS or power conditioner for the controller. Set up FPP watchdog to auto-restart on crash. Use a smart plug with monitoring to log power events.

### 25. Can't Upload to Controller from xLights
**Possible causes:** Firewall blocking FTP/HTTP, wrong controller type selected in xLights, firmware version mismatch, controller password set.
**Diagnostic steps:** Try accessing the controller's web UI directly in a browser. Check xLights controller tab for error messages. Verify controller vendor/model selection.
**Fix:** Temporarily disable firewall. Update controller firmware and xLights to latest compatible versions. Use the correct controller type in xLights (Falcon, ESPixelStick, WLED, FPP, etc.). Clear any saved passwords that may be incorrect.

### 26. Sequences Look Different on Actual Pixels vs xLights Preview
**Possible causes:** Model layout doesn't match physical layout, pixel mapping orientation is reversed, brightness limiting changes the look, colour temperature differs between screen and LEDs.
**Diagnostic steps:** Run a simple chase effect and compare direction between preview and reality. Check model start/end pixel assignments. Verify orientation settings (bottom-left vs top-left start).
**Fix:** Adjust model properties in xLights to match physical layout. Use the "Wiring View" in xLights to verify pixel order. Run test patterns (red/green/blue chase) to verify correct mapping. Take a video of the physical display and compare side-by-side with the preview.

### 27. WLED Effects Work but E1.31/DDP Input Doesn't
**Possible causes:** Sync interfaces not enabled in WLED, wrong port number, universe count exceeds WLED's default limit of 9, multicast not reaching the device.
**Diagnostic steps:** Check WLED Config → Sync Interfaces → enable E1.31 or DDP. Verify port and universe settings. Check if the "Receive" toggle is on.
**Fix:** Enable E1.31 (sACN) or DDP in WLED sync settings. For DDP, the default port is 4048. For E1.31, set start universe and check "Multicast" or enter the xLights unicast IP. If using >9 universes over E1.31 in WLED, compile a custom build with a higher limit, or switch to DDP (which has no universe limit). Disable WLED's own effects while receiving E1.31/DDP (set to "Solid Black" or turn off).

---

## Part 2: Frequently Asked Questions

### Networking & Setup

**Q1: Can I use my normal house WiFi or do I need a separate network?**
For a small setup (<500 pixels, 1–2 controllers), your home WiFi will work. For larger displays, a dedicated network is strongly recommended. E1.31 multicast traffic can saturate a home network and cause buffering on streaming services. Use a separate cheap Ethernet switch ($20–$40 from Officeworks) connected to your controllers via Cat6 cable. WiFi is unreliable for more than ~10 E1.31 universes.

**Q2: How many pixels can one controller handle?**
Depends on the controller. Common limits: WLED on ESP32 — up to ~2000 pixels per board (WiFi) or ~4000 (Ethernet). Falcon F16V5 — up to 48 ports × 1024 pixels per port. FPP on a Raspberry Pi with a hat — 16+ ports. The real limit is usually data refresh rate and power, not the controller chip. At 800kbps (WS2812B protocol), each port can refresh ~680 pixels at 30fps.

**Q3: WS2811 vs WS2812B vs WS2815 — which do I buy?**
- **WS2811** (12V): Best for rooflines, outlines, mega trees. Separate IC drives 3 LEDs as one pixel. Tolerates longer runs (5–10m between power injection). Easy to repair — unplug bad node, plug in replacement. ~$15–$30/string of 50–100 nodes.
- **WS2812B** (5V): Best for matrices, dense props, short runs. One IC per LED. Needs power injection every 2–3m. Repair requires soldering. ~$7–$20/strip of 5m.
- **WS2815** (12V): Like WS2812B density but at 12V with a backup data line (can skip one dead pixel). Best of both worlds for medium-density outdoor use. More expensive. ~$15–$30 per 5m strip.
- **For beginners in Australia: start with 12V WS2811 bullet pixels for house outlines.**

**Q4: Can I mix 5V and 12V pixels on the same controller?**
Yes, if your controller supports per-port voltage configuration (most Falcon/Kulp boards do). The key rule: **never share power between 5V and 12V strings**. Each voltage group needs its own power supply. Data signals are the same protocol regardless of voltage.

**Q5: What power supply should I buy?**
Meanwell LRS or SE series are the community standard. Budget ~60mA per WS2812B pixel at full white, but real-world draw is typically 20–30mA. For 500 × 12V pixels: ~500 × 20mA = 10A, so a Meanwell LRS-150-12 (12.5A) with headroom. For 5V, draw is higher per pixel. Always add 20% headroom. In Australia, ensure PSU is rated for 240VAC input. Available from Mouser, Element14, or eBay for $25–$80 AUD depending on wattage.

**Q6: How do I waterproof connections?**
- **Best:** IP67 waterproof connectors (pre-fitted on Ray Wu pixels) — ~$0.50–$1.00 each
- **Good:** Self-amalgamating silicone tape over connections — ~$8–$15/roll at Bunnings
- **Acceptable:** 3M Scotch 33+ electrical tape — stays flexible in cold/heat — ~$8/roll
- **For power supply enclosures:** IP65 junction boxes from Bunnings ($10–$25)
- **Never:** Plastic bags over connections (trap moisture, cause more problems)
- Apply dielectric grease to all connections before sealing

**Q7: Can I leave pixels up year-round in Australia?**
Yes, many Australian displayers do. UV is the main enemy — silicone-coated strip (IP67) and quality bullet pixels handle Australian sun reasonably well. Clear pixels yellow after 2–3 years of UV exposure. Black or coloured housings last longer. Coastal salt spray accelerates corrosion — rinse with fresh water monthly. Budget for replacing ~10–20% of outdoor pixels annually due to UV degradation or failures.

**Q8: How much will my electricity bill go up?**
A typical 2,000-pixel display running 6 hours/night for 6 weeks at average brightness uses roughly 1–2 kWh per night. At ~$0.30/kWh (Australian average), that's $0.30–$0.60/night or **$12–$25 for the entire season**. A mega display with 10,000+ pixels might cost $50–$100/season. The controller and power supply idle draw is negligible. Use WLED's brightness limiter or xLights' brightness cap to reduce consumption.

### Software & Protocols

**Q9: Can I use xLights with WLED controllers?**
Absolutely — this is one of the most popular combinations. xLights sends E1.31 (sACN) or DDP packets to WLED over your network. In WLED, enable E1.31 or DDP under Config → Sync Interfaces. In xLights, add the WLED controller by IP address. DDP is simpler (no universe management) while E1.31 is more widely supported.

**Q10: What's the difference between E1.31, DDP, and ArtNet?**
- **E1.31 (sACN):** Industry standard. 512 channels (170 RGB pixels) per universe. Supports multicast and unicast. Most widely compatible. Needs universe planning for large installs.
- **DDP (Distributed Display Protocol):** Simpler — no universe limits, just point it at an IP and set pixel count. Fewer configuration headaches. Preferred for WLED and FPP-to-FPP.
- **ArtNet:** Older DMX-over-IP standard. 512 channels per universe. Less common in Christmas lighting but used in professional stage lighting.
- **Recommendation:** Use DDP for WLED controllers, E1.31 for Falcon/SanDevices hardware.

**Q11: Do I need FPP (Falcon Player)?**
FPP runs on a Raspberry Pi and acts as your show player — it plays back sequences on a schedule without needing your PC running. If you want a "set and forget" show, yes. FPP can also be a controller (with a pixel hat) or just a player that sends data to other controllers. For a WLED-only setup, you can use WLED's built-in playlists for simple shows or FPP for complex music-synced sequences.

**Q12: Can I design sequences on Mac/Linux or only Windows?**
xLights is fully cross-platform — Windows, macOS, and Linux. FPP runs on Linux (Raspberry Pi). WLED is configured via a web browser on any platform. The entire Christmas lighting software stack is free and open-source.

**Q13: What frame rate should I use for sequences?**
20ms (50fps) is the xLights default and works well for most displays. 25ms (40fps) is fine and uses less network bandwidth. Faster isn't always better — the human eye can't perceive differences above ~30fps at typical viewing distances. Faster frame rates generate more network traffic and can overwhelm WiFi-connected controllers.

**Q14: How do I back up my xLights show?**
Your entire show is in one folder (the "show directory"). Back up this whole folder regularly — it contains sequences (.xml), rendered data (.fseq), layouts, and models. Use cloud sync (Google Drive, Dropbox) or an external drive. xLights also creates .xbkp backup files automatically.

### Hardware & Physical Install

**Q15: How do I add pixels to an existing display?**
1. Buy matching pixel type and voltage
2. Wire them to a free port on your controller (or add a new controller)
3. In xLights, add a new model matching the new prop
4. Assign it to the correct controller port
5. Create or extend sequences to include the new model
6. Upload new configuration to FPP/WLED

**Q16: How far can I run data cable?**
Without signal conditioning: 5–10m maximum. With a null pixel (sacrificial pixel at the start): extends reliable range. With a 74HCT245 level shifter: up to 15–20m. For very long runs, use differential signalling (RS485) — some controllers support this natively. Always run data and ground as a pair.

**Q17: What wire gauge do I need?**
- **Data lines:** 22–20 AWG is fine (low current)
- **Power runs <3m:** 18 AWG
- **Power runs 3–10m:** 16 AWG
- **Power runs >10m:** 14 AWG or heavier
- Rule of thumb: voltage drop = current × resistance. Use an online voltage drop calculator. For 5V systems, even small drops matter.

**Q18: What's a null pixel and do I need one?**
A null pixel is the first pixel in a string that's hidden from view. It acts as a signal repeater/buffer between your controller and the visible display. It cleans up the data signal, especially useful with ESP32 controllers that output 3.3V data. Cost: ~$0.50. Highly recommended for any run over 1m from controller to first visible pixel.

**Q19: Can my neighbours hear the music?**
If using an FM transmitter (most common approach), neighbours tune in on their car radio — no outdoor speakers needed. This is legal in Australia at low power. If using outdoor speakers, keep volume reasonable and check your local council noise restrictions. Many displayers run their shows 6pm–10pm on weeknights and until 11pm on weekends. The ACL (AusChristmasLighting) community recommends always being a good neighbour first.

**Q20: Do I need council permission in Australia?**
Generally no, for a residential display on your own property. However:
- If you expect significant traffic, notify your local council and police
- Some councils offer free "Christmas lights map" registration
- If using structures that could be considered temporary buildings (large frames >2.5m), check local regulations
- Electrical work on 240V mains must be done by a licensed electrician — low-voltage (5V/12V/24V) pixel work doesn't require a licence in most states
- Check strata/body corporate rules if in a unit or apartment

**Q21: How do I mount pixels on a brick house?**
- **Chromatrim channels:** Aluminium channels that screw to the wall; pixels snap in. Reusable yearly. ~$5–$10/m from Australian suppliers.
- **Boscoyo strips:** Plastic strips with pre-drilled holes for bullet pixels. Mount with screws. ~$3–$5/m.
- **Conduit:** PVC electrical conduit drilled at pixel spacing. Very sturdy. ~$2–$3/m from Bunnings.
- **Clip strips:** Adhesive or screw-mount clips. Removable each season.
- For rendered brick: use Tapcon masonry screws or adhesive hooks (Command strips struggle in Australian heat).

**Q22: 30 pixels/m or 60 pixels/m — which spacing?**
- **30/m (~33mm spacing):** Good for rooflines and outlines viewed from the street (10m+ distance). Lower cost, lower power draw. Most common for house outlines.
- **60/m (~17mm spacing):** Better for matrices, arches, and props viewed up close. Smoother colour transitions. Double the cost, power, and channels.
- **For beginners: 30/m for outlines, 60/m for feature props.**

**Q23: Can I daisy-chain multiple controllers?**
Yes. FPP multisync allows one master Pi to synchronise multiple remote FPP players. E1.31 from xLights/FPP can target multiple controllers on the same network. WLED controllers can sync with each other via UDP. The key is a reliable network (Ethernet preferred) and static IP addresses for every controller.

### Buying & Cost

**Q24: Where do I buy pixels in Australia?**
- **LightItUpLEDs** (pixelprops.com.au) — Australian reseller, local warranty
- **Ray Wu's store** on AliExpress — direct from manufacturer, cheapest, 2–6 week shipping
- **BTF-Lighting** on AliExpress/Amazon — popular budget option
- **Adafruit / Core Electronics** (core-electronics.com.au) — for controllers and dev boards
- **AusChristmasLighting.com forums** — second-hand gear, group buys, local advice
- If ordering from China now (mid-Sept), pay for express shipping — standard won't arrive in time
- Prefer Australian suppliers (Hanson, PixelController) for 1–2 week delivery this late in the season

**Q25: What's a realistic budget for a beginner display?**
- **Starter (house outline only, ~500 pixels):** $200–$400 AUD
  - 500 WS2811 12V bullet pixels: $60–$100
  - Falcon or ESP32 controller: $30–$80
  - Meanwell PSU: $30–$50
  - Mounting, wiring, connectors: $50–$100
  - Enclosure and misc: $30–$70
- **Intermediate (outline + 2–3 props, ~2000 pixels):** $600–$1,200 AUD
- **Advanced (full display with music sync, 5000+ pixels):** $1,500–$3,000+ AUD

**Q26: Should I buy 5V or 12V?**
12V for almost everything outdoor. It runs longer between power injection points (5–10m vs 2–3m for 5V), which means simpler wiring. 5V only where you need very dense strip (matrices, small props). The ACL community overwhelmingly recommends 12V for beginners.

### Safety & Electrical

**Q27: Is it safe to run pixel lights in the rain?**
Yes, if you use IP67 rated pixels and properly sealed connections. The pixel voltage (5V/12V/24V) is classified as Extra Low Voltage (ELV) in Australia and poses minimal shock risk. The 240V mains side (power supplies, extension cords, RCDs) is where the real danger is — this must be waterproof and ideally installed by a licensed electrician. Always use RCD protection on outdoor 240V circuits.

**Q28: Do I need an electrician?**
For the 240V mains side (adding outdoor power points, running permanent circuits, installing RCDs): **yes, licensed electrician required by Australian law**. For the low-voltage side (5V/12V/24V pixel wiring, controllers, data cables): no licence required — a "competent person" can do this work in most Australian states per AS/NZS 3000.

**Q29: What's the fire risk?**
Low if installed correctly. LED pixels run cool compared to incandescent lights. Main risks: overloaded power supplies, undersized wiring, short circuits. Mitigations: fuse every power run, use quality PSUs (Meanwell, not unbranded), don't exceed wire current ratings, keep PSUs ventilated, and never run cables under carpet or insulation.

**Q30: Can I plug pixels into a normal power point?**
Pixels need a DC power supply (5V/12V/24V), not 240VAC. Your power supply plugs into the 240V power point, and the pixels plug into the power supply's DC output. Never connect pixels directly to 240V mains.

### Advanced

**Q31: What's the best controller for beginners?**
- **Simplest:** WLED on an ESP32 board ($10–$20 AUD). Flash via USB, configure via phone browser. Good for up to ~1000 pixels without sequencing.
- **Best value for sequenced shows:** Kulp K32A-B ($50–$80 AUD) or Falcon F4V3 ($60–$100 AUD). Multiple ports, web UI, runs xLights sequences via FPP.
- **Most capable:** Falcon F48 ($150–$250 AUD). 48 ports, handles massive displays.

**Q32: How do I sync lights to music?**
1. Design your sequence in xLights — map beats, drops, and accents to effects
2. Export the FSEQ file and audio to FPP on a Raspberry Pi
3. FPP plays the audio (via USB sound card or HDMI) while simultaneously sending pixel data to controllers via E1.31/DDP
4. Use an FM transmitter ($15–$30 AUD) so visitors can tune in on their car radio
5. Set up a playlist and schedule in FPP for automated nightly shows

**Q33: What's a universe and why do I care?**
A universe is a group of 512 DMX channels (enough for 170 RGB pixels). E1.31 sends data in universe-sized chunks. If you have 500 pixels, you need 3 universes (500 × 3 channels ÷ 512 = 2.93, rounded up). You assign universe numbers in xLights and the controller. DDP eliminates this concept — just set the total pixel count.

**Q34: How do I troubleshoot with a multimeter?**
Essential measurements:
- **DC voltage** at the pixel end of a run (should be within 10% of rated)
- **Continuity** on data and ground wires (beep = connected)
- **Current draw** with a clamp meter on the power feed (compare to calculated)
- **AC voltage** at the power point (should be 230–250V in Australia)
- A basic multimeter from Jaycar ($25–$40 AUD) is sufficient

**Q35: What's the difference between a controller and a player?**
- **Controller:** Receives data (E1.31/DDP/DMX) and drives pixel output pins. Examples: Falcon F16V5, ESPixelStick, WLED on ESP32.
- **Player:** Reads sequence files (FSEQ) and sends data to controllers over the network. Also handles scheduling, playlists, and audio. Example: FPP on Raspberry Pi.
- Some devices do both (FPP with a pixel hat, Falcon in standalone mode).

---

## Part 3: Glossary

| Term | Definition |
|------|-----------|
| **ArtNet** | An older protocol for sending DMX data over IP networks. Less common in Christmas lighting than E1.31. |
| **Bullet pixel** | A single LED node in a sealed waterproof housing, typically WS2811 12V. Connects via pigtail wires or plugs. Easy to replace individually. |
| **Channel** | A single control value (0–255). One RGB pixel uses 3 channels (red, green, blue). One RGBW pixel uses 4 channels. |
| **Chromatrim** | An aluminium mounting channel for LED strip, popular in Australia. Pixels snap into the channel; the channel screws to the building. |
| **Colour order** | The sequence of colour data expected by the pixel IC (e.g., RGB, GRB, BRG). Must match between software and hardware. |
| **Controller** | Hardware that receives pixel data and drives output to LEDs. Examples: Falcon F16V5, ESP32 running WLED, Kulp boards. |
| **CQC (Christmas Quarters of Craziness)** | Informal term in the ACL community for the peak October–December period when everyone is building and troubleshooting their displays. |
| **DDP (Distributed Display Protocol)** | A simple protocol for sending pixel data over IP. No universe limits — just set total pixel count. Default port 4048. Preferred for WLED. |
| **Differential pixel (WS2815/WS2813)** | Pixel ICs with a backup data line that allows data to bypass one failed pixel, improving reliability. |
| **DMX-512** | The original stage lighting control protocol. 512 channels per universe. Used over XLR cable. E1.31 wraps DMX data in IP packets. |
| **E1.31 (sACN)** | Streaming ACN — the standard protocol for sending DMX universes over Ethernet/IP. Port 5568. Supports multicast and unicast. 512 channels per universe. |
| **ELV (Extra Low Voltage)** | Voltage under 50V AC or 120V DC. In Australia, a competent person can work with ELV without an electrical licence. Christmas pixel voltages (5V/12V/24V) are ELV. |
| **FSEQ** | The file format used by xLights and FPP for rendered sequence data. Contains raw channel values for each frame. V1 (uncompressed) and V2 (compressed) variants exist. |
| **FPP (Falcon Player)** | Open-source show player software that runs on Raspberry Pi and BeagleBone. Plays FSEQ sequences, handles scheduling, audio, and multisync. |
| **Fuse** | Inline overcurrent protection placed on each power run. Prevents wiring fires if a short circuit occurs. Typically 5A for 12V runs, 10A for 5V runs. |
| **GPIO** | General Purpose Input/Output — the pins on an ESP32/Raspberry Pi that connect to pixel data lines. |
| **GRB** | Green-Red-Blue — the colour order used by most WS2812B pixels. Software must send data in this order. |
| **IGMP snooping** | A switch feature that filters multicast traffic. Can block E1.31 multicast if not configured correctly. Disable on simple show networks. |
| **IP67** | Ingress Protection rating — protected against dust (6) and temporary immersion in water (7). Standard for outdoor Christmas pixels. |
| **Level shifter** | A chip (typically 74HCT245) that converts 3.3V data signals to 5V, ensuring reliable communication with pixels. Essential for ESP32 controllers. |
| **Mega tree** | A large conical tree shape made from strings of pixels radiating from a central pole. A signature prop in Christmas displays. |
| **Model** | In xLights, a virtual representation of a physical prop (roofline, tree, arch, matrix). Used to map effects onto pixel layouts. |
| **Multicast** | Network transmission to all devices simultaneously. E1.31 can use multicast (239.255.x.x) so multiple controllers receive the same data. |
| **Multisync** | FPP's feature for synchronising playback across multiple Raspberry Pi players. One master controls timing; remotes follow. |
| **Node** | A single addressable point in a pixel string. For WS2811 12V, one node = 3 LEDs. For WS2812B, one node = 1 LED. |
| **Null pixel** | A sacrificial pixel placed between the controller and the first visible pixel. Acts as a signal buffer/repeater. Hidden from view. |
| **Pixel** | A single individually-addressable LED (or group of LEDs) that can display any colour. Uses 3 channels (RGB) or 4 (RGBW). |
| **Pixel mapping** | The process of assigning physical pixel positions to virtual model positions in xLights, so effects display correctly on the actual prop. |
| **Power injection** | Adding additional power feed points along a pixel run to compensate for voltage drop. Essential for runs longer than 2–3m (5V) or 5–10m (12V). Only inject V+ and GND, never data. |
| **Prop** | Any physical display element — an arch, star, wreath, tree, snowflake, singing face, etc. Each prop is represented as a model in xLights. |
| **RCD (Residual Current Device)** | Australian term for a safety switch that trips when it detects current leaking to ground (>30mA). Called GFCI in the USA. Required on outdoor 240V circuits. |
| **sACN** | Streaming Architecture for Control Networks — the formal name for E1.31. |
| **Sequence** | A timeline of lighting effects synchronised to music or a timer. Created in xLights and exported as FSEQ files for playback. |
| **Show directory** | The folder containing all xLights files for a show — sequences, layouts, models, networks, and rendered FSEQ files. |
| **Smart pixel** | Another term for an individually-addressable pixel (as opposed to "dumb" LEDs that all show the same colour). |
| **Start channel** | The first DMX channel number assigned to a model or controller port. Determines where in the data stream a device's pixel data begins. |
| **Strip** | Flexible PCB tape with surface-mount LEDs. Available in densities from 30 to 144 LEDs/m. Usually WS2812B (5V) or WS2815 (12V). |
| **Unicast** | Network transmission to a single specific IP address. More reliable than multicast on complex networks. |
| **Universe** | A group of 512 DMX/E1.31 channels. One universe addresses up to 170 RGB pixels (170 × 3 = 510 channels). Large displays use many universes. |
| **WLED** | Free, open-source firmware for ESP8266/ESP32 that controls addressable LEDs. Features a web UI, app, E1.31/DDP support, and hundreds of built-in effects. |
| **WS2811** | A pixel driver IC commonly used in 12V bullet/node pixels. One IC controls 3 LEDs as a single addressable pixel. |
| **WS2812B** | A pixel IC integrated into a 5050 LED package. 5V, one IC per pixel. Standard for LED strip. |
| **WS2815** | A 12V pixel IC integrated into a 5050 LED package with a backup data line. Combines 12V tolerance with per-pixel addressability. |
| **xLights** | Free, open-source sequencing software for designing and rendering Christmas light shows. Cross-platform (Win/Mac/Linux). The de facto standard for hobbyist displays. |
| **xSchedule** | xLights' built-in show scheduler. Alternative to FPP for automated playback on a Windows PC. |

---

---

## Part 4: Seasonal Checklist

### Pre-Season (August–October)
- [ ] Test all pixels from last year — plug in each string and run a test pattern
- [ ] Replace any failed pixels or strips found during testing
- [ ] Update xLights, FPP, and WLED firmware to latest stable versions
- [ ] Check all connectors for corrosion — clean with contact cleaner
- [ ] Inspect all power supplies — check for bulging capacitors or burn marks
- [ ] Order replacement pixels and new props — allow 4–6 weeks for AliExpress
- [ ] Plan power layout and calculate total amperage per circuit
- [ ] Test RCDs with a plug-in tester before the season starts

### Install Week
- [ ] Mount pixels and props during dry weather
- [ ] Apply dielectric grease to all outdoor connections before sealing
- [ ] Test each section as you install — don't wait until everything is up
- [ ] Verify all power injection points are connected and fused
- [ ] Run a full show test including audio sync before opening night
- [ ] Set up FPP schedule with appropriate on/off times
- [ ] Check display from the street — adjust brightness and effects for viewer distance

### Mid-Season
- [ ] Walk the display weekly checking for failures or water damage
- [ ] Monitor PSU temperatures during hot days
- [ ] Keep spare pixels, fuses, and connectors on hand for quick repairs
- [ ] Check FPP logs for any errors or crashes
- [ ] Respond to RCD trips promptly — identify and fix the cause

### Pack-Down (January–February)
- [ ] Label every cable, prop, and controller before disconnecting
- [ ] Photograph your wiring layout for reference next year
- [ ] Coil cables loosely — don't kink or crush insulation
- [ ] Store pixels in labelled bins, indoors, away from heat and rodents
- [ ] Back up your xLights show directory and FPP configuration
- [ ] Note any failures or improvements needed for next season

---

*Sources: AusChristmasLighting.com community forums, WLED Project documentation (kno.wled.ge), xLights manual, Falcon Player documentation, WorldSemi datasheets (WS2811/WS2812B/WS2815), Adafruit NeoPixel Überguide, YourPixelStore.com, PlanetChristmas.com. Prices approximate as of mid-2026.*