You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plugin is production release quality and I have tested it on both the latest released version of FPP and the current nightly build.
My plugin does not interfere with core FPP functionality, stability, or real-time sequence playback, and installs cleanly (or refuses with an explanation) on hardware it can't support.
My plugin is not malicious and does not and will not in future exfiltrate data or run unexpected remote code.
My pluginInfo.json carries a privacy block (the eight keys in the schema) that honestly describes what the plugin sends, collects, senses, opens and changes - required for every listing. The Privacy disclosure builder writes it for you, and the Plugin preview shows the install dialog FPP will build from it.
I understand inclusion is at the FPP developers' discretion and is not guaranteed.
@GraphicHealer found 3 issue(s) this must be fixed before the plugin can be listed:
🛑 Blocker - exec-bit - scripts/fpp_install.sh is not executable - commit it +x (git update-index --chmod=+x)
🛑 Blocker - exec-bit - scripts/fpp_uninstall.sh is not executable - commit it +x (git update-index --chmod=+x)
⚠️Best practice - no-restart-flag - registers command type(s) via commands/descriptions.json but doesn't request an fppd restart at every lifecycle point that needs one - install: scripts/fpp_install.sh present, no restart/reboot flag; uninstall: scripts/fpp_uninstall.sh present, no restart/reboot flag.
This plugin's code itself looks fine for FPP 10 - structurally safe to hot-load/unload without a restart there. The flag is still needed because pluginInfo.json's versions[] serves this exact branch/build to FPP majors before 10 too, which have no plugin load/unload feature at all - those installs still need a full fppd restart to pick up install/uninstall.
Add ( set +u; source "${FPPDIR:-/opt/fpp}/scripts/common" && setSetting restartFlag 1 ) || true to each script listed above (creating fpp_install.sh/fpp_uninstall.sh if missing - only fpp_upgrade.sh is optional, and only needs it if you already have one); only drop it once you split off a separate FPP 10+-only branch/sha in versions[]
Push a fix to your repo, then comment /recheck here (no need to edit this issue) to re-run the scan. If you believe these checks are wrong and want a maintainer to look anyway, comment /submit instead.
Activity
github-actions commentedon Oct 25, 2026
🛑 Automated plugin check: needs changes
Plugin: fpp-plugin-FauxLite
Repo: https://github.com/GraphicHealer/fpp-plugin-FauxLite
Owner:
GraphicHealerCategory: Messaging, Signage & Countdown
@GraphicHealer found 3 issue(s) this must be fixed before the plugin can be listed:
🛑 Blocker - exec-bit - scripts/fpp_install.sh is not executable - commit it +x (git update-index --chmod=+x)
🛑 Blocker - exec-bit - scripts/fpp_uninstall.sh is not executable - commit it +x (git update-index --chmod=+x)
( set +u; source "${FPPDIR:-/opt/fpp}/scripts/common" && setSetting restartFlag 1 ) || trueto each script listed above (creating fpp_install.sh/fpp_uninstall.sh if missing - only fpp_upgrade.sh is optional, and only needs it if you already have one); only drop it once you split off a separate FPP 10+-only branch/sha in versions[]Push a fix to your repo, then comment
/recheckhere (no need to edit this issue) to re-run the scan. If you believe these checks are wrong and want a maintainer to look anyway, comment/submitinstead.GraphicHealer commentedon Oct 25, 2026
/recheck
github-actions commentedon Oct 25, 2026
✅ Automated plugin check: passed
Plugin: fpp-plugin-FauxLite
Repo: https://github.com/GraphicHealer/fpp-plugin-FauxLite
Owner:
GraphicHealerCategory: Messaging, Signage & Countdown
@GraphicHealer no blocking issues found. A maintainer will still review this by hand before it's added to
pluginList.json.github-actions commentedon Oct 25, 2026
📦 Listing PR: #301
Closing this issue - further discussion happens on the PR now. Merging it is a separate decision for a maintainer to make.