9.3

Important Note: Github recently updated their download URL's to timeout after 5 minutes. If you are having problems downloading 9.3 due to the timeout, you can grab the files from https://fpp.kulplights.com/ . We are trying to find a better long term solution while we also hope that GitHub will reverse this change.

NOTE: The OS level has changed slightly from 2025-09. There were some security patches to the base OS that were incorporated. Updating the OS level is optional, but encouraged.

Enhancements

• Allow plugins to optionally monitor their settings for changes so they can update themselves at runtime instead of requiring fppd restart. (plugins will need updates to use this)
• Update FSEQFile to not load large variable headers into memory until needed/requested
• Developers: Use gold/mold linkers if they are installed, faster builds

Bug Fixes (since 9.2)

• Fix crash if output is recreated while a sub-overlay model is using it
• Fix ethtool information display for persistent net interface names
• Fix temperature in header to respect localization settings for F vs C
• Fix some issues with panelSize setting after upgrade from 8.x
• Prevent some configuration of GPIO pins that are being used by capes
• Fix some issues that may prevent eeprom signings
• Fix for UDP sending Ping announcements for inactive network interfaces
• Fix to prevent git development branches as showing as new releases
• Fix BBShiftString starting wrong PRU on BBB, fixes K128 issues
• Fix more issues with flashing to Beaglebone Black RevD 16GB eMMC
• Fix some issues with backups to remote FPP instances
• Fix crash if Start Playlist command is used without an index parameter or without specificing the playlist
• Fix crash with overly large custom models (limit the size)
• Fix some crashes with Panels with Pi Panel Hats with invalid configuration
• Fix crash if custom overlay models have spaces instead of numbers or blanks
• Fix crash if GPIO input pin cannot be configured as an input
• Attempt to detect if BBB PRU cannot be started and display a "Please Reboot" warning instead of crashing
• Fix crash if FPP Command json has a "null" instead of an empty string
• Fix crash if using "fpp -g" to set GPIO pin without first using -G to set it to output
• Fix crash if UDP outputs are reloaded while some slow/offline controllers had flipped to "curl" for monitoring
• Fix crash generating stats if model overlays file is too large
• Fix crash if Falcon v5 receiver status packet cannot be properly parsed/processed
• Fix crash if uploading a new fseq file if that sequence is playing (prevent the upload)

Installation Instructions

If you have a system running 9.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 8.x or older, due to incompatibilities with the underlying libraries, an "OS Level" upgrade is required.

• Re-image - you can backup your 8.x configuration, create a new image, and restore the configuration.
• In-place upgrade - This requires you to have the latest FPP 7.5 or newer and all updates already running on the device. On the "About" page in FPP, there is an "Upgrade OS" choice selection where the appropriate 9.3_2025-11 image can be selected. FPP will automatically download the fppos file and install the upgrade. It will take a LONG time. When done, it should reboot into 9.3. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file.

NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series use this image

• FPP-v9.3-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v9.3-BBB.img.zip

For PocketBeagle2 use this image

• FPP-v9.3-BB64.img.zip

9.2

Important Note: Github recently updated their download URL's to timeout after 5 minutes. If you are having problems downloading 9.2 due to the timeout, you can grab the files from https://fpp.kulplights.com/ . We are trying to find a better long term solution while we also hope that GitHub will reverse this change.

NOTE: The OS level has changed slightly from 2025-08. There were some security patches to the base OS that were incorporated. Updating the OS level is optional, but encouraged.

Enhancements

• Support for flashing to eMMC on new BeagleBone Black RevD boards
• Add more information to "gpioinfo" command/troubleshooting to better show which pins are in use
• Increase number of header UI colors available
• Add advanced option to disable jgrowl alerts in the UI
• Support for PRU based serial output on PB2
• New advanced option for handling audio/sequence timing offsets that will work better with multisync/remotes.
• Add support for Subscribing to mulitple MQTT Topics
• Add ability to delete individual presetRows on Control Channel output type
• Multisync - show temp in F for Falcon if UI set to that

Bug Fixes (since 9.1)

• Fix querying of GPIO pins on PocketBeagle2 when GPIO is set for output
• Avoid warnings in log related to closed file descriptors when FPP is shutdown
• Fix problems with Current Monitoring stopping when String config is saved requiring and FPPD restart
• Fix HTTPVirtualDisplay not working with security policies
• Fix display issue where ArtNet universe 0 gets mapped to universe 1
• Fix issue with ColumnSelector widget on MultiSync page populating twice
• Fix crash closing media if media wasn't found to start off with
• Fix websocket handling in proxies
• Fix font-src CSP defaults to ensure WLED loads correctly under proxy
• Fix /git URL not working
• Clean up formatting and add buttons to control channel outputs
• If the media_duration.cache files becomes unparsable or corrupt, remove it and recreate.
• BBShiftPanel - Add an extra clock tick for the clock signal to allow it to propogate better
• Fix Command Editor - if command argument is labelled to allowBlanks, record that and when reconstructing the list from a remote, add the blank in
• Fix FileManager - Prevent cancelled uploads from deleting the uploads directory entirely
• Fix GPIO - If we fail to get a file for the GPIO edges, reconfigure back to normal so polling will work correctly

Installation Instructions

If you have a system running 9.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 8.x or older, due to incompatibilities with the underlying libraries, an "OS Level" upgrade is required.

• Re-image - you can backup your 8.x configuration, create a new image, and restore the configuration.
• In-place upgrade - This requires you to have the latest FPP 7.5 or newer and all updates already running on the device. On the "About" page in FPP, there is an "Upgrade OS" choice selection where the appropriate 9.2_2025-09 image can be selected. FPP will automatically download the fppos file and install the upgrade. It will take a LONG time. When done, it should reboot into 9.1. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file.

NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series use this image

• FPP-v9.2-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v9.2-BBB.img.zip

For PocketBeagle2 use this image

• FPP-v9.2-BB64.img.zip

9.1

Important Note: Github recently updated their download URL's to timeout after 5 minutes. If you are having problems downloading 9.1 due to the timeout, you can grab the files from https://fpp.kulplights.com/ . We are trying to find a better long term solution while we also hope that GitHub will reverse this change.

NOTE: The OS level has not changed since 9.0 and remains at 2025-08. There is no need to do an fppos update if coming from 9.0.

Enhancements

• Add kmsprint commands to Video troubleshooting tab
• Add GPIO commands to troubleshooting for Beagles
• UDP outputs now hides irrelevant fields
• Move Colorlight firmware and link check settings to Panel page and make it per-panel setting
• Add "H-Flip" options for OLED displays

Bug Fixes (since 9.0)

• Fix issues with Falcon v5 controllers behind FPP proxy
• Fix issues with ShellInABox SSH access for FPP behind proxy
• Vendor eeprom upgrade lists can properly filter for PocketBeagle 2 based eeproms
• Fix issues with hostapd (Access Point Mode) not stopping and spa_supplicant not starting on network restart
• Fix "Test" options for Pixel Strings on BB64 platform
• Fix table sorter on MultiSync page not retaining sort order
• Fix link to enable rsync from backups page
• Fix visibility of various panel options with Pi Matrix capes
• Fix update of used Channel Ranges when outputs are reloaded
• Fix removal of auto-created Pixel Overlay Models if output is disabled
• Fix requiring FPPD restart if VirtualMatrix reconfigured
• Fix requiring FPPD restart if VirtualDisplay reconfigured
• Fix detection of Pi5 internal RTC clock
• Fix potential crash if "Play Media" command is used to play the same media many times in quick succession
• Fix FalconV5 controllers showing on MultiSync page as "Unknown System"
• Fix DHCP provided IP's not properly being proxied
• Fix crash if video is being output to Pixel Overlay Model and the model is destroyed
• Minor adjustments to BBShiftPanel output to increase brightness
• Fix restoration of "Blank Screen" settings after fppos update
• Fix display of BB64 based fppos files for MultiSync "Copy OS Upgrade Files" option

Installation Instructions

If you have a system running 9.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 8.x or older, due to incompatibilities with the underlying libraries, an "OS Level" upgrade is required.

• Re-image - you can backup your 8.x configuration, create a new image, and restore the configuration.
• In-place upgrade - This requires you to have the latest FPP 7.5 or newer and all updates already running on the device. On the "About" page in FPP, there is an "Upgrade OS" choice selection where the appropriate 9.1_2025-08 image can be selected. FPP will automatically download the fppos file and install the upgrade. It will take a LONG time. When done, it should reboot into 9.1. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file.

NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series use this image

• FPP-v9.1-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v9.1-BBB.img.zip

For PocketBeagle2 use this image

• FPP-v9.1-BB64.img.zip

FPP 9.0

FPP 9.0

Enhancements

• Official support for new PocketBeagle 2
  • Most capes for original PocketBeagle can now work with the PocketBeagle 2
  • New BBShiftPanel driver for PocketBeagle 2 for driving LED Panels
• SD Cards auto-expand storage space on first reboot (second boot)
• ColorLight updates
  • New ability to drive multiple ColorLight matrices from single FPP instance (requires multiple ethernet adapters)
  • Preliminary support for v13 ColorLight firmware (works in SOME cases)
  • Try to autodetect ColorLight firmware versions and if receivers are present, Advanced Mode UI settings to override detection
• UI Updates:
  • Update available icon now in upper menu when an update is available
  • Channel Input and Channel Output configuration now updates immediately and no longer requires an FPPD restart
  • Many settings (not all) are now reflected immediately instead of requiring an FPPD restart
  • Changes to Command presets no longer require an FPPD restart
  • Active Overlay Model Effects are now displayed on the Effects page (and can be stopped there as well)
  • DHCP leases from FPP will automatically display as Proxied on Proxies page
  • Help menu re-organized with help pages put into categories on a new "Get Help" page
  • Playlist cards now display total length and number of items
  • Localization settings moved from "System" and "Time" tabs to separate Localization tab
  • Services (like Samba/MQTT/etc...) moved to new "Services" tab
• New features for Capes/Hats/Outputs
  • Capes can now provide "Device Tree Overlay" files to pre-configure onboard peripherals as part of kernel boot. Results in faster boot and clearer logs
  • Ability for capes to use "nice names" (like "DMX1") instead of linux names like "ttyS4" for serial outputs
  • Many new Panel interleave types for Beagle based Panel drivers (Octoscrollers, PocketScrollers, etc...)
  • OLEDs on Capes now provide additional status messages during boot
  • Capes can specify which GPIO pins to show or hide on GPIO lists to prevent users from adjusting GPIO's that are used internally
• Security updates
  • Many settings are no longer exposed in the HTML page if not required for that page
  • Content-Security-Policy header is now set to prevent malicious javascript from accessing sites that are not authorized
• Output Processors Updates:
  • New "Clamp Value" output processor to make sure channel values do not exceed a set value
  • New "Scale Value" output processor for scaling all channels by a common factor
  • Output Processors can now be configured with Model names instead of just channel ranges
• New MQTT broker configuration to allow FPP instance to become an MQTT broker
• New support for CH340 based USB relays
• Support for Raspberry Pi Compute Module 5

Major Changes/Incompatibilities

• The "FPD" dongle output for driving PixelNet is now deprecated and will be removed in the future
• Many of the "Remote XXXX" FPP commands (like "Remote Playlist Start") are deprecated and will be remove in the future. Use the normal FPP command with the Multisync checkbox and target set
• FPP now only includes the "In Kernel" WIFI drivers. Some older WIFI adapters may no longer work
• FPP's backend HTTP service which was on port 32322 is now only bound to localhost and is unavailable from external hosts/scripts

Upgrade Instructions

Due to incompatibilities with the underlying libraries, an "OS Level" upgrade is required.

• Re-image - you can backup your 8.x configuration, create a new image, and restore the configuration.
• In-place upgrade - This requires you to have the latest FPP 7.5 or newer and all updates already running on the device. On the "About" page in FPP, there is an "Upgrade OS" choice selection where the appropriate 9.0_2025-08 image can be selected. FPP will automatically download the fppos file and install the upgrade. It will take a LONG time. When done, it should reboot into 9.0. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. Note: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series including Pi B, Pi B+, Pi 3, Pi 3+, Pi 4 and Pi Zero use this image

• FPP-v9.0-Pi.img.zip

For Beaglebone Black, Beaglebone Green, Original PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v9.0-BBB.img.zip

For PocketBeagle2 use this image

• FPP-v9.0-BB64.img.zip

9.0-beta1

Beta1 Notes

FPP 9.0 is very similar to FPP8 and is based on the same OS level (Debian 12). Thus, there are not a lot of large "under the cover" changes. However, there are a bunch of new features/changes that do require testing.

One primary focus we'd like to test is WIFI drivers. At this point, 9.0 has been updated to the latest Linux kernels which supposedly include much improved WIFI drivers. Many of the external drivers do not compile with the latest kernels yet and thus have not been included in the 9.0-beta1 images. We like extensive testing to determine if we need to continue to try and build/include the external drivers.

Another area of focus is the Panel matrices. This page is being completely re-done to support multiple matrices. There are things that don't work yet but will be fixed/updated in the upcoming weeks. However, testing to help identify bugs/issues would be appreciated.

The PocketBeagle 2 support includes an entirely new platform. There may be areas in the code/ui that are specifically looking for "BeagleBone Black" or similar and may not display all the appropriate options for the PB2. If you have PB2 based devices, any help identifying issues would be helpful.

Enhancements

• Support for PocketBeagle 2
  • New "BB64" platform defined for PocketBeagle2 and future 64bit Beagles
  • Most existing capes for the PocketBeagle 1 will work. Exception at this point is BBSerial based outputs. (tty based serial outputs work)
  • New BBShiftPanel driver optimized for PocketBeagle 2 to drive panel matrices at higher speed
  • PB2 based capes can provide device trees for uboot/linux to load to provide better hardware integration and faster boot
• Effects
  • WLED effects updated to latest code. More effects, bug fixes, etc...
  • Running Overlay Model Effects (including WLED effects) are now displayed on the Effects page and can be stopped from there
  • Effects page - add filters for ESEQ and FSEQ
• Panel Matrices
  • Support for Colorlight v13 firmware - auto detected, all cards in chain must have same firmware
  • Expose a bunch of new options and interleave settings for PiHat based Matrix hats
  • Ability to configure multiple LED Panel matrices
    • Allows for multiple ColorLights or ColorLight + Hat/Cape
• Security Updates:
  • Implement "Content Policy Control" headers (work in progress)
  • Remove some settings from returned page headers (work in progress)
• Help menu completely reorganized with a "Help" page dedicated to the various help topics
• Output Processors - ability to use a model for a channel range
• PWM/Servo configuration - LED's can now be "reversed" to handle common anode LED's
• eFuse - log sequence and timestamp when triggered to help determine what is causing it
• File Manager - better handling of subdirectories that may be placed there via SMB or other

Major Changes/Incompatibilities

• Linux Kernel
  • Beagles are updated to the latest Linux 6.15 kernel
  • Pi is updated to the latest 6.12 kernel
  • Only "Kernel" wifi drivers are provided
• FPPMon
  • FPP 9 includes all new bootstrap packages, style sheets, scripts, etc.... FPPMon has not been updated to handle those yet. Thus, FPPMon may not be able to control devices that are not on the local network.

Upgrade Instructions

• Re-image - you can backup your 8.x configuration, create a new image, and restore the configuration.
• In-place upgrade - This requires you to have the latest FPP 7.5 or newer and all updates already running on the device. On the "About" page in FPP, there is an "Upgrade OS" choice selection where the appropriate 9.0-beta1_2025-05 image can be selected. FPP will automatically download the fppos file and install the upgrade. It will take a LONG time. When done, it should reboot into 9.0-beta1. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. Note: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series including Pi B, Pi B+, Pi2, Pi 3, Pi 3+, Pi 4, Pi 5, and all Pi Zeros use this image

• FPP-v9.0-beta1-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle 1, and Beaglebone Green Gateway use this image

• FPP-v9.0-beta1-BBB.img.zip

For PocketBeagle 2 use this image

• FPP-v9.0-beta1-BB64.img.zip

8.5

Note: FPPOS level has been updated to 2025.02. This was done to include some OS level security patches such as updates to rsync and others that have critical security vulnerabilities.

Enhancements

• "Alpha Level" support for PocketBeagle2
  • This is a work in progress and will likely have many more updates on the "8.5-bb64" branch as work continues
  • Currently supports "BB48String" based capes such as the K4-PB, K8-PB, K40-PB and Scott Hanson's PB_16 and others
• Allow plugins to get a notification on playlist insertion so it can prepare necessary changes (may require plugin rebuilds/re-install)
• Volume button labels
• Add Help menu item for reporting bug
• Add dmesg reporting to "Troubleshooting" on all platforms
• Move file manage filters setting to bottom of screen
• Collect stats on a few additional settings
• Add support for PCF8563 RTC

Bug Fixes (since 8.4.1)

• Don't crash if invalid start channel is set for various outputs
• If plugin script disappears while fppd is running (example: plugin uninstalled) don't polute logs with stack traces
• Return proper 404 for api/file/sequence if no file given
• Fix some scaling issues with PlaylistEntryImage
• Fix bug in DPI and BBBShiftString that may only allow 49 pixels on unlicensed capes instead of 50
• Fix /api/sequence to only return fseq file
• Relax file name sanitization on deletes in file manager
• Add fpp user to dialout group
• Fix description on Tethering page to not reference connman as we no longer use it
• Fix extra display of channel counts on Other page
• Fix reporting of mixer devices from cards with more than one mixer
• Fix saving of PWM outputs
• Fix install of Kiosk mode after fppos update
• Fix some out of memory conditions when creating backups

Installation Instructions

If you have a system running 8.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process. However, that will not get the OS level updates that address various security vulnerabilities. It is recommended to do the FPPOS update instead.

For users of FPP 7.x or older, it is strongly recommended to do a full "OS Level" upgrade or re-image instead of attempting to upgrade directly from any older FPP version. There are several new features that will not work if an OS level upgrade is not done. There are two ways to do so:

• Re-image - you can backup your 7.x configuration, create a new image, and restore the configuration.

• In-place upgrade - this requires you to have FPP 5.5 and all the updates for 5.5 or FPP 6.x/7.x already running on the device. Download the appropriate "fppos" file to your computer. Make sure the file extension is still fppos (some browsers will rename it). Upload it to the "File Manager" on the FPP instance. Then go to the about page. Under the normal "Manual Upgrade", a new Upgrade OS button should appear. Click it and wait a LONG time. When done, it should reboot into 8.3. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. An alternate method to do an in-place upgrade if you are only upgrading one device AND the device has internet connectivity, is to select the 8.3 fppos (download) file and then click on the Upgrade OS button. This will download the fppos file and then install it as mentioned above. This will still take a LONG time and if you are doing this on more than one device, you will essentially be downloading the same file multiple times so is probably not the best way.

• NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series use this image

• FPP-v8.5-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v8.5-BBB.img.zip

For PocketBeagle2 use this image:

• FPP-v8.5-alpha5-BB64.img.zip

8.4

NOTE: The OS level has not changed since 8.3. There is no need to do an fppos update if coming from 8.3.

Enhancements

• Add Advanced option to stop Colorlight outputs from being disabled if ethernet link is down when fppd starts
• Update rpi_ws281x to support newer Pi 3A+/3B/3B+/CM3
• Update UDPOutput to support a "blocking" mode to slow down packet output to allow slower controllers to keep up better. (Advanced UI setting)
• Schedule Preview - mark items that will be skipped in red and note priority reason

Bug Fixes (since 8.3.0)

• Fix crash when manually stopping playlist using ArtNet/SMPTE plugins as timecode generator
• Fix crash using HTTP to detect some AlphaPix controllers
• Fix pixel output on right half of K128
• Fix crashes on SanCloud BeagleBone Enhanced due to to gpiochip label differences
• Fix api/scripts//run
• Fix api/events/:eventId/trigger
• Fix failed plugin install messaging
• Fix HDMI audio out on Pi's
• Fix crash if efuse enable pin cannot be configured. Warn and continue, but don't crash
• Fix a potential crash if PLAYLIST_STOPPED command preset is called
• Fix crash if Chase/Cycle custom pattern is selected, but pattern is empty
• Fix crash if pixel configuration or other configuration json is invalid during output setup
• Fix tooltips on MQTT page being truncated
• Fix some crashes with dynamic playlists that are empty
• Fix some crashes with invalid pixel overlay model configurations
• Fix crashes with RGBMatrix (panel hats for Pi) on older armv6 Pi's
• Fix a crash when sending invalid WLED effect commands
• Fix a crash if fseq file is corrupt

Installation Instructions

If you have a system running 8.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 7.x or older, it is strongly recommended to do a full "OS Level" upgrade or re-image instead of attempting to upgrade directly from any older FPP version. There are several new features that will not work if an OS level upgrade is not done. There are two ways to do so:

• Re-image - you can backup your 7.x configuration, create a new image, and restore the configuration.

• In-place upgrade - this requires you to have FPP 5.5 and all the updates for 5.5 or FPP 6.x/7.x already running on the device. Download the appropriate "fppos" file to your computer. Make sure the file extension is still fppos (some browsers will rename it). Upload it to the "File Manager" on the FPP instance. Then go to the about page. Under the normal "Manual Upgrade", a new Upgrade OS button should appear. Click it and wait a LONG time. When done, it should reboot into 8.3. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. An alternate method to do an in-place upgrade if you are only upgrading one device AND the device has internet connectivity, is to select the 8.3 fppos (download) file and then click on the Upgrade OS button. This will download the fppos file and then install it as mentioned above. This will still take a LONG time and if you are doing this on more than one device, you will essentially be downloading the same file multiple times so is probably not the best way.

• NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series use this image

• FPP-v8.4-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v8.4-BBB.img.zip

8.3

NOTE: The OS level has changed. On the Beaglebone, there are minor changes to help with WIFI tethering. On the Pi, in addition to the tethering updates, there are new "external" WIFI drivers (for Pi 4 and lower, not available on Pi 5) that may work better for some USB WIFI adapters if you are not using the Pi's onboard WIFI.

Enhancements

• Troubleshooting page updated to display scan of WIFI networks that are available
• Load vendor image for menu asynchronously to avoid pause if image cannot be downloaded
• Add fold output processor that reverses a strand in the middle and interleaves the pixels
• Change start and channel count on "Other" output tab to number input type to prevent any characters from being entered
• "External" WIFI adapters added to Pi image (Pi 4 and older) to match with Beaglebone images

Bug Fixes

• Bunches of updates to make sure tethering is enabled if no connection, even if the OS takes a significantly long time to detect and load the WIFI drivers
• Update some IP address validation to allow leading zeros
• Make sure socket send buffers are set to a reasonable size, set smaller receive buffers to save memory
• Fix problems with Hats with multiple GPIO expanders now working on a Pi3
• Fix playlist item display on status page for mobiles
• Fix a bunch of unnecessary statements being logged to syslog
• Fix some race conditions and locking problems in the "Warnings" API's that could cause the frontend to pause/hang
• Fix some crashes if the eeprom and cape don't physically match and sensors that the eeprom say to use don't actually exist
• Update volume sliders to trigger only on value change and rate limit api volume call
• Fix crashes on BBShiftString capes if differential receiver is set for v4/v5 but the cape doesn't have v5 listener hardware
• Limit USBDMX to 512 channels to prevent overrun/crash

Installation Instructions

If you have a system running 8.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 7.x or older, it is strongly recommended to do a full "OS Level" upgrade or re-image instead of attempting to upgrade directly from any older FPP version. There are several new features that will not work if an OS level upgrade is not done. There are two ways to do so:

• Re-image - you can backup your 7.x configuration, create a new image, and restore the configuration.

• In-place upgrade - this requires you to have FPP 5.5 and all the updates for 5.5 or FPP 6.x/7.x already running on the device. Download the appropriate "fppos" file to your computer. Make sure the file extension is still fppos (some browsers will rename it). Upload it to the "File Manager" on the FPP instance. Then go to the about page. Under the normal "Manual Upgrade", a new Upgrade OS button should appear. Click it and wait a LONG time. When done, it should reboot into 8.3. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. An alternate method to do an in-place upgrade if you are only upgrading one device AND the device has internet connectivity, is to select the 8.3 fppos (download) file and then click on the Upgrade OS button. This will download the fppos file and then install it as mentioned above. This will still take a LONG time and if you are doing this on more than one device, you will essentially be downloading the same file multiple times so is probably not the best way.

• NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series use this image

• FPP-v8.3-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v8.3-BBB.img.zip

8.2

NOTE: The OS level has not changed. If running OS level 2024.10, there is no need to update the OS. However, there was a bug in the fppos update from FPP 7.x on the Raspberry Pi that would cause downloading of logs to fail. If you had updated from 7.x on the Pi using the fppos update, you need to use the new 8.2 fppos update to correct the OS install.

Enhancements

• Add ability for Multisync plugins to respond to incoming multisync packets
• Add Stop Media and Stop All Media commands
• Simplify Virtual Matrix creation using "Auto Create" by removing pixel size option, auto scale to screen size

Bug Fixes

• Fix "Total" current display on capes with less than 8 ports
• Fix various crashes
• Fix race condition at boot where Timezone may not be fully configured
• Fix race condition at boot where OLED push buttons may not be configured
• Fix problems configuring Access Point mode if rfkill disables the wlan adapater
• Fix plugin install script log output not adding new line where needed
• Fix crash when using Play Media command
• Fix problems drawing Virtual Matrices into Sub Buffers
• Fix recognition of "Composite-1" KMS devices

Installation Instructions

If you have a system running 8.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 7.x or older, it is strongly recommended to do a full "OS Level" upgrade or re-image instead of attempting to upgrade directly from any older FPP version. There are several new features that will not work if an OS level upgrade is not done. There are two ways to do so:

• Re-image - you can backup your 7.x configuration, create a new image, and restore the configuration.

• In-place upgrade - this requires you to have FPP 5.5 and all the updates for 5.5 or FPP 6.x/7.x already running on the device. Download the appropriate "fppos" file to your computer. Make sure the file extension is still fppos (some browsers will rename it). Upload it to the "File Manager" on the FPP instance. Then go to the about page. Under the normal "Manual Upgrade", a new Upgrade OS button should appear. Click it and wait a LONG time. When done, it should reboot into 8.2. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. An alternate method to do an in-place upgrade if you are only upgrading one device AND the device has internet connectivity, is to select the 8.2 fppos (download) file and then click on the Upgrade OS button. This will download the fppos file and then install it as mentioned above. This will still take a LONG time and if you are doing this on more than one device, you will essentially be downloading the same file multiple times so is probably not the best way.

• NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series including Pi B, Pi B+, Pi 2, Pi 3, Pi 3+, Pi 4, Pi 5, Pi Zero, and Pi Zero 2 use this image

• FPP-v8.2-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v8.2-BBB.img.zip

8.1

NOTE: The OS level has changed. To get all of the updates, you will need to use the fppos upgrade method or use a new image.

Enhancements

• Allow proxying of WebSocket connections
• Add device type/model to Log banner to aid in debugging/reproducing issues
• Remove some unnecessary reboots from the network settings page
• BeagleBone - update Linux kernel to 6.11 (OS Level Change)
• BeagleBone - update wifi drivers, fix 8192cu driver (OS Level Change)
• Add ability to enable WPA3/SAE Wifi authentication
• eFuse capes - Advanced mode ability to configure automatic retries
• Asynchronously ping UDP controllers for faster startup, particularly if many are offline

Bug Fixes

• Update file item count in File Manager on item deletion
• Fix detection of RGBMatrix (Pi LED panels) at boot and don't load snd_bcm2835
• Fix NTP not able to update time if NTP server specified
• Workaround for controllers that are not putting their IP address in the ping/discovery packets
• Fix Command Presets layout when warning alerts are present
• Fix "Test Pattern" button on Beagle based capes not starting test pattern
• Fix "Insert Random Item from Playlist" not being random
• Fix problems with Remotes staring video if they need to jump to the middle of the video
• Delay Pi power warning until it occurs multiple times
• Fix many issues on Channel Outputs page if Cape EEPROM does not contain a "provides" attribute
• Fix Kiosk mode no able to be disabled
• Fix issues with GPIO expanders on Pi5 not being properly numbered
• Fix problems starting sequences that are greater than 2G in size
• Only display "Icon for help" message if help messages actually exist
• Fail/Warn (instead of hang) if RGBMatrix configured on Pi5
• Fix some crashed when background threads add/update timers (MQTT reconnect main offender)
• Fix some crashes if VLC fails to start (log instead of crash)

Installation Instructions

If you have a system running 8.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.

For users of FPP 7.x or older, it is strongly recommended to do a full "OS Level" upgrade or re-image instead of attempting to upgrade directly from any older FPP version. There are several new features that will not work if an OS level upgrade is not done. There are two ways to do so:

• Re-image - you can backup your 7.x configuration, create a new image, and restore the configuration.

• In-place upgrade - this requires you to have FPP 5.5 and all the updates for 5.5 or FPP 6.x/7.x already running on the device. Download the appropriate "fppos" file to your computer. Make sure the file extension is still fppos (some browsers will rename it). Upload it to the "File Manager" on the FPP instance. Then go to the about page. Under the normal "Manual Upgrade", a new Upgrade OS button should appear. Click it and wait a LONG time. When done, it should reboot into 8.1. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file. An alternate method to do an in-place upgrade if you are only upgrading one device AND the device has internet connectivity, is to select the 8.1 fppos (download) file and then click on the Upgrade OS button. This will download the fppos file and then install it as mentioned above. This will still take a LONG time and if you are doing this on more than one device, you will essentially be downloading the same file multiple times so is probably not the best way.

• NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

Selecting an image

For Raspberry Pi series including Pi B, Pi B+, Pi 3, Pi 3+, Pi 4, Pi 5, and Pi Zero use this image

• FPP-v8.1-Pi.img.zip

For Beaglebone Black, Beaglebone Green, PocketBeagle, and Beaglebone Green Gateway use this image

• FPP-v8.1-BBB.img.zip