Sudden F-Prop Issue

[aarondhess]

I've been running an F-prop successfully until a couple days ago.

What’s happening:

• The controller loads the FSEQ file successfully
• Logs show the sequence is recognized and stored in flash
• However, output behavior is incorrect (values appear to be changing unexpectedly / not matching intended static output)
• MY LIGHTS DONT TURN ON

Relevant log behavior:

• Configuration initially reported as invalid (“Invalid end token”)
• After reloading, config appears to load from SD → flash
• Logs show values being modified even when they should remain static
  • Channels per Pixel: 2 (when my config was set at 3)
  • String 1 Pixels: 0 (when my config was set to 180)
  • Brightness: 16 (when I was at 255)

What I’ve already tried:

• I loaded an empty sd card and my entire strip lit up with the on-board default config (rainbow with a vibration trigger to shif to to white), so my strip and the f-prop are functional
• I created a basic config with the online programming tool, I told it to run 20 pixels on white. Everything loaded, I got the steady blinking LED indicator light on the board, nothing turned on. I checked the log and it had set my pixel counts to zero.
• I've given up trying to run my own xlights fseq. I can't even get the basics to work anymore!

I recently upgraded to build 18, wonder if that's causing all the problems...