🎛️ FPP Players — Zone & NDB Mapping
Each FPP (Falcon Player) runs pixel sequences and sends DDP Raw Channel data to NDB controllers. Universe size is typically 8,192 or 8,193 channels per output. Data collected from live FPP APIs — March 2026.
Contents
FPP Player Overview
All players share the same show schedule: 16:30–21:30 daily. NUC-based players run the rolling 9.x-master branch; RPi players run the 9.4 stable release.
| Hostname | IP | Platform | FPP Version | Zone | Active Playlist / Sequence | Schedule | Model Count | Status |
|---|---|---|---|---|---|---|---|---|
| forest-pix1 | 10.50.0.11 |
Debian NUC | 9.x-master | Flowers | SummerFinal.fseq |
16:30–21:30 | 69 | Online |
| forest-pix2 | 10.50.0.12 |
Debian NUC | 9.x-master | Fire | FireFinal.fseq |
16:30–21:30 | 44 | Online |
| forest-pix3 | 10.50.0.13 |
RPi 4 | 9.4 | Mushrooms | MushroomFinal.fseq |
16:30–21:30 | 44 | Online |
| forest-pix4 | 10.50.0.14 |
Debian NUC | 9.x-master | Huts | Huts.fseq |
16:30–21:30 | 44 | Online |
| forest-pix5 | 10.50.0.15 |
Debian NUC | 9.x-master | Spring | SpringFInal.fseq |
16:30–21:30 | 44 | Online |
| forest-minipix1 | 10.50.0.20 |
RPi 3B+ | 9.4 | Clocks | ClocksFinal.fseq |
16:30–21:30 | 44 | Online |
| forest-minipix2 | 10.50.0.21 |
RPi | — | Rain | — | 16:30–21:30 | — | Offline (data collection) |
| forest-minipix3 | 10.50.0.22 |
RPi | — | Garden Centre | — | 16:30–21:30 | — | Offline (data collection) |
| forest-minipix5 | 10.50.0.24 |
RPi 3B+ | 9.4 | Monsters | MonstersFinal.fseq |
16:30–21:30 | 69 | Online |
| forest-Music3 | 10.50.0.227 |
RPi 3B | 9.4 | Audio | — | 16:30–21:30 | — | Online |
| forest-Music4 | 10.50.0.228 |
RPi 3B | 9.4 | Audio | — | 16:30–21:30 | — | Online |
Schedule & Deployment Notes
FPP schedule runs 16:30–21:30 — this is a deliberate 30-minute buffer before Home Assistant’s automated trigger at 17:00. The early start ensures all NDBs are fully initialized and outputting before visitors arrive.
Valentines playlist deployed Feb 9, 2026. Every player has a secondary “Valentines” playlist containing V-prefixed sequences (
VFire.fseq, VSummer.fseq, VHuts.fseq, etc.). These override the default startup playlist during seasonal events.
NUC vs RPi firmware split:
forest-pix1, pix2, pix4, and pix5 run Intel NUC hardware with Debian and track the rolling 9.x-master branch. forest-pix3 (RPi 4) and all minipix units run FPP 9.4 stable.
forest-minipix2 and forest-minipix3 were offline during the March 2026 data collection pass. Platform, version, playlist, and model data are not available for these players. On-site verification required.
forest-pix4 (Huts) has 3 inactive DDP outputs (NDB26, NDB2, NDB21). These NDBs may have been physically reassigned to other zones or decommissioned. Verify before removing from config to avoid accidental data loss.
DDP Output Configuration
Each player drives one or more NDB controllers over the local network using the DDP protocol. Output channel counts are fixed at 8,192 or 8,193 channels per universe. Active/inactive status reflects whether FPP was able to communicate with the NDB at the time of data collection.
forest-pix1 — Flowers (10.50.0.11)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | NDB6 | NDB6 | 10.50.0.55 | DDP | 8,193 | Active |
| U2 | NDB23 | NDB23 | 10.50.0.72 | DDP | 8,193 | Active |
forest-pix2 — Fire (10.50.0.12)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | NDBballs | NDB3 | 10.50.0.52 | DDP | 8,193 | Active |
| U2 | NDBhem1 | NDB14 | 10.50.0.63 | DDP | 8,193 | Active |
| U3 | NDBhem2 | NDB24 | 10.50.0.73 | DDP | 8,193 | Active |
| U4 | NDBhem3 | NDB18 | 10.50.0.67 | DDP | 8,193 | Active |
| U5 | NDB1sticks | NDB22 | 10.50.0.71 | DDP | 8,193 | Active |
forest-pix3 — Mushrooms (10.50.0.13)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | NDB1 path | NDB1 | 10.50.0.50 | DDP | 8,193 | Active |
| U2 | NDB4 main | NDB4 | 10.50.0.53 | DDP | 8,193 | Active |
| U3 | NDB8 island | NDB8 | 10.50.0.57 | DDP | 8,193 | Active |
| U4 | (secondary) | NDB1 | 10.50.0.50 | DDP | 8,193 | Duplicate IP |
NDB1 (10.50.0.50) appears in both U1 and U4. Confirm whether outputs use different channel start offsets (intentional multi-universe split) or whether U4 is a configuration artefact that should be removed.
forest-pix4 — Huts (10.50.0.14)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | NDB6 hut 1 | NDB11 | 10.50.0.60 | DDP | 8,192 | Active |
| U2 | NDB9 hut 2 | NDB9 | 10.50.0.58 | DDP | 8,192 | Active |
| U3 | NDB10 hut3 | NDB10 | 10.50.0.59 | DDP | 8,192 | Active |
| U4 | — | NDB26 | 10.50.0.75 | DDP | 8,192 | Inactive (ping fail) |
| U5 | — | NDB2 | 10.50.0.51 | DDP | 8,192 | Inactive |
| U6 | — | NDB21 | 10.50.0.70 | DDP | 8,192 | Inactive |
U4–U6 are inactive. NDB26, NDB2, and NDB21 do not respond. These outputs may have been physically reassigned to other zones (NDB2 and NDB21 appear in the Garden Centre player’s config). Do not delete without confirming no cross-zone use.
forest-pix5 — Spring (10.50.0.15)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | — | NDB20 | 10.50.0.69 | DDP | 8,192 | Active |
| U2 | NDB7 | NDB17 | 10.50.0.66 | DDP | 8,192 | Active |
| U3 | — | NDB13 | 10.50.0.62 | DDP | 8,192 | Active |
| U4 | — | NDB34? | 10.50.0.62 | DDP | 8,192 | Inactive |
NDB17 (U2) is labelled “NDB7” in the FPP config — this is a label mismatch. U4 is listed with an uncertain NDB number and shares the IP of U3 (
10.50.0.62) — verify whether U4 is a duplicate entry or a separate device.
forest-minipix1 — Clocks (10.50.0.20)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | NDB33 | NDB33 | 10.50.0.82 | DDP | 8,192 | Active |
| U2 | Ndb33 | NDB28 | 10.50.0.77 | DDP | 8,192 | Active (label mismatch) |
U2 label mismatch: FPP shows the label as “Ndb33” but the actual NDB IP resolves to NDB28 (
10.50.0.77). NDB28 is also referenced by forest-minipix2 (Rain). Confirm physical location and correct label.
forest-minipix2 — Rain (10.50.0.21)
Player was offline during data collection. The NDB output config below is based on prior records. Verify on next site visit.
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | NDB7 | NDB7 | 10.50.0.56 | DDP | 8,192 | Unverified |
| U2 | NDB34 | NDB34 | 10.50.0.83 | DDP | 8,192 | Unverified |
| U3 | NDB28 | NDB28 | 10.50.0.77 | DDP | 8,192 | Unverified (label conflict) |
forest-minipix3 — Garden Centre (10.50.0.22)
Player was offline during data collection. Output config is based on prior records. Note: NDB2 and NDB21 are also listed as inactive outputs on forest-pix4 — confirm current zone ownership.
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Start Channel | Status |
|---|---|---|---|---|---|---|---|
| U1 | NDB27 | NDB27 | 10.50.0.76 | DDP | 8,193 | Offset | Unverified |
| U2 | NDB2 | NDB2 | 10.50.0.51 | DDP | 8,193 | Offset | Unverified |
| U3 | NDB21 | NDB21 | 10.50.0.70 | DDP | 8,193 | Offset | Unverified |
All outputs on forest-minipix3 use offset start channels (universe size 8,193). Verify channel mapping before adding new outputs to this player.
forest-minipix5 — Monsters (10.50.0.24)
| Output (U#) | NDB Label | NDB # | NDB IP | Protocol | Channels | Status |
|---|---|---|---|---|---|---|
| U1 | — | NDB15 | 10.50.0.64 | DDP | 8,192 | Active |
| U2 | — | NDB32 | 10.50.0.81 | DDP | 8,192 | Active |
Playlists & Sequences
Each player has a primary “startup” playlist and a secondary “Valentines” playlist. Sequence file sizes are from the FPP /api/sequence/list endpoint. All .fseq files are stored locally on each player.
| Player / Zone | Primary Playlist | Primary Sequence | Valentines Playlist | Valentines Sequence | Total Sequences | Notable Files |
|---|---|---|---|---|---|---|
| forest-pix1 Flowers |
startup-show | SummerFinal.fseq |
Valentines | VSummer.fseq |
16 |
Flowers.fseq 10 MBSummerFinal.fseq 14.85 MBVSummer.fseq 17.61 MBRainWave.fseq 8.28 MBRain.fseq 3 MB
|
| forest-pix2 Fire |
Startup | FireFinal.fseq |
Valentines | VFire.fseq |
6 |
FatherTimeFire.fseq 18.47 MBFireFinal.fseq 6.8 MBVFire.fseq 12.02 MBRainFinal.fseq 11.41 MB
|
| forest-pix3 Mushrooms |
Startup | MushroomFinal.fseq |
Valentines | MushroomFinal.fseq (same) |
24 | Includes test/development files. Valentines playlist reuses the standard sequence — no separate V-prefix variant deployed. |
| forest-pix4 Huts |
Start | Huts.fseq |
Valentines | VHuts.fseq |
15 | — |
| forest-pix5 Spring |
Startup | SpringFInal.fseq |
Valentines | VSpring.fseq |
7 | VSundial.fseq 12.94 MB |
| forest-minipix1 Clocks |
Start | ClocksFinal.fseq |
Valentines | VClocks.fseq |
14 | — |
| forest-minipix2 Rain |
— | — | — | — | — | Offline during data collection |
| forest-minipix3 Garden Centre |
— | — | — | — | — | Offline during data collection |
| forest-minipix5 Monsters |
Startup | MonstersFinal.fseq |
Valentines | VMonsters.fseq |
15 | — |
Typo in forest-pix5 sequence name: The active sequence is
SpringFInal.fseq (capital “I” before “nal”). This matches the filename exactly on disk — do not rename unless all playlist references are updated simultaneously.
Temperature Sensors
Sensor data from /api/sensors. NUC players expose ACPI, Wi-Fi, and package thermal sensors; RPi players expose a single CPU sensor. All readings taken during normal show operation. Elevated temperatures on NUCs are expected under load.
| Player | Platform | Sensor | Typical Reading | Notes |
|---|---|---|---|---|
| forest-pix1 | Debian NUC | ACPITZ |
~40°C | Chassis/ACPI thermal zone |
IWLWIFI_1 |
~42°C | Wi-Fi adapter temperature | ||
X86_PKG_TEMP |
~47°C | Intel CPU package temp — highest under sequence load | ||
| forest-pix2 | Debian NUC | ACPITZ |
~39°C | Chassis/ACPI thermal zone |
IWLWIFI_1 |
~41°C | Wi-Fi adapter temperature | ||
X86_PKG_TEMP |
~45°C | Intel CPU package temp | ||
| forest-pix4 | Debian NUC | ACPITZ |
~38°C | Chassis/ACPI thermal zone |
IWLWIFI_1 |
~40°C | Wi-Fi adapter temperature | ||
X86_PKG_TEMP |
~44°C | Intel CPU package temp | ||
| forest-pix5 | Debian NUC | ACPITZ |
~37°C | Chassis/ACPI thermal zone |
IWLWIFI_1 |
~40°C | Wi-Fi adapter temperature | ||
X86_PKG_TEMP |
~43°C | Intel CPU package temp | ||
| forest-pix3 | RPi 4 | CPU |
~41°C | Single SoC thermal sensor. RPi 4 throttles above 80°C. |
| forest-minipix1 | RPi 3B+ | CPU |
~40°C | Running at capacity — monitor for thermal throttling if ambient temp rises. |
| forest-minipix5 | RPi 3B+ | CPU |
~36°C | Single SoC thermal sensor. |
All temperatures are within safe operating ranges. NUC X86_PKG_TEMP readings of 43–47°C under full sequence load are normal for passively cooled Intel NUC6 hardware. Alert threshold recommended at 70°C for NUCs and 75°C for RPi units.
Full NDB Assignment Summary
Master mapping of all known NDB controllers, their zone assignments, and which FPP player drives them. Entries marked “Unconfirmed” have no verified zone assignment in the FPP API data.
| NDB # | IP | Zone | FPP Player | Label in FPP | Notes |
|---|---|---|---|---|---|
| NDB1 | 10.50.0.50 | Mushrooms | forest-pix3 | NDB1 path | Also appears as U4 duplicate — verify |
| NDB2 | 10.50.0.51 | Garden Centre / Huts | minipix3 / pix4 (inactive) | NDB2 | Conflict: pix4 has it as inactive output; minipix3 as active |
| NDB3 | 10.50.0.52 | Fire | forest-pix2 | NDBballs | — |
| NDB4 | 10.50.0.53 | Mushrooms | forest-pix3 | NDB4 main | — |
| NDB5 | 10.50.0.54 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB6 | 10.50.0.55 | Flowers | forest-pix1 | NDB6 | — |
| NDB7 | 10.50.0.56 | Rain | forest-minipix2 | NDB7 | Player offline — unverified |
| NDB8 | 10.50.0.57 | Mushrooms | forest-pix3 | NDB8 island | — |
| NDB9 | 10.50.0.58 | Huts | forest-pix4 | NDB9 hut 2 | — |
| NDB10 | 10.50.0.59 | Huts | forest-pix4 | NDB10 hut3 | — |
| NDB11 | 10.50.0.60 | Huts | forest-pix4 | NDB6 hut 1 | Label reads “NDB6” — mismatch with NDB# |
| NDB12 | 10.50.0.61 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB13 | 10.50.0.62 | Spring | forest-pix5 | — | Also listed as U4 IP on pix5 — possible duplicate |
| NDB14 | 10.50.0.63 | Fire | forest-pix2 | NDBhem1 | — |
| NDB15 | 10.50.0.64 | Monsters | forest-minipix5 | — | — |
| NDB16 | 10.50.0.65 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB17 | 10.50.0.66 | Spring | forest-pix5 | NDB7 | Label mismatch: labelled “NDB7” in FPP |
| NDB18 | 10.50.0.67 | Fire | forest-pix2 | NDBhem3 | — |
| NDB19 | 10.50.0.68 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB20 | 10.50.0.69 | Spring | forest-pix5 | — | — |
| NDB21 | 10.50.0.70 | Garden Centre / Huts | minipix3 / pix4 (inactive) | NDB21 | Conflict: pix4 inactive output; minipix3 active |
| NDB22 | 10.50.0.71 | Fire | forest-pix2 | NDB1sticks | — |
| NDB23 | 10.50.0.72 | Flowers | forest-pix1 | NDB23 | — |
| NDB24 | 10.50.0.73 | Fire | forest-pix2 | NDBhem2 | — |
| NDB25 | 10.50.0.74 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB26 | 10.50.0.75 | Huts (inactive) | forest-pix4 | — | Ping fail — may be reassigned or decommissioned |
| NDB27 | 10.50.0.76 | Garden Centre | forest-minipix3 | NDB27 | Player offline — unverified |
| NDB28 | 10.50.0.77 | Rain / Clocks | minipix1 & minipix2 | Ndb33 / NDB28 | Label conflict — physical device shared between two players |
| NDB29 | 10.50.0.78 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB30 | 10.50.0.79 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB31 | 10.50.0.80 | Unconfirmed | — | — | Not referenced in any FPP output config |
| NDB32 | 10.50.0.81 | Monsters | forest-minipix5 | — | — |
| NDB33 | 10.50.0.82 | Clocks | forest-minipix1 | NDB33 | — |
| NDB34 | 10.50.0.83 | Rain | forest-minipix2 | NDB34 | Player offline — unverified. Also referenced as uncertain output on pix5. |
| NDB35 | 10.50.0.84 | Unconfirmed | — | — | Not referenced in any FPP output config |
Issues & Action Items
| # | Issue | Affected | Detail | Priority | Status |
|---|---|---|---|---|---|
| 1 | Duplicate DDP output | forest-pix3 → NDB1 (.50) | NDB1 appears as U1 (“NDB1 path”) and U4 (secondary). Confirm if different channel offsets are intentional or remove the duplicate. | High | Open |
| 2 | Label mismatch — NDB28 | NDB28 (.77) | Physical device at 10.50.0.77 is labelled “Ndb33” in minipix1 and “NDB28” in minipix2. Both players reference the same IP. Clarify ownership and correct labels. | Medium | Open |
| 3 | Label mismatch — NDB17 | forest-pix5 U2 | NDB17 (10.50.0.66) is labelled “NDB7” in the FPP output config. Rename to “NDB17” to match the IP registry. | Low | Open |
| 4 | Label mismatch — NDB11 | forest-pix4 U1 | NDB11 (10.50.0.60) is labelled “NDB6 hut 1” in FPP. This conflicts with NDB6 (10.50.0.55) in the Flowers zone. Rename to “NDB11 hut 1”. | Low | Open |
| 5 | Inactive outputs — pix4 | forest-pix4 U4–U6 | NDB26, NDB2, and NDB21 are inactive on pix4. NDB2 and NDB21 are active on forest-minipix3. Confirm if these were reassigned and clean up pix4 output config. | Medium | Open |
| 6 | Duplicate IP on pix5 U3/U4 | forest-pix5 | U3 (NDB13) and U4 (NDB34?) both reference 10.50.0.62. U4 is inactive. Verify if this is a misconfigured entry and remove if so. | High | Open |
| 7 | Players offline | forest-minipix2, forest-minipix3 | Both players were unreachable during the March 2026 data collection. On-site power and network check required. Playlist, version, and model data unavailable. | High | Open |
| 8 | forest-pix3 Valentines gap | forest-pix3 | Valentines playlist reuses MushroomFinal.fseq rather than a dedicated V-prefix sequence. All other zones have a unique Valentines sequence. Confirm if intentional or if VMushrooms.fseq was never deployed. | Low | Open |
| 9 | Unconfirmed NDBs | NDB5, 12, 16, 19, 25, 29, 30, 31, 35 | These NDB IPs are not referenced by any FPP player. Walk site to confirm if devices exist at these addresses or if the IP range can be released. | Medium | Open |
| 10 | Sequence filename typo | forest-pix5 | SpringFInal.fseq (capital “I”) is active in production. Do not rename without updating all playlist references simultaneously. | Low | Open |