Issue with FPP and WLED Not Displaying Effects over DDP

[ricardo]

Hi everyone,

I've been using FPP (Falcon Player) connected via DDP protocol with a WLED, and everything was working perfectly until about two hours ago when it suddenly stopped. Here's the situation:

When I start a sequence on the FPP, it successfully connects to the WLED. I can see the "Live" message on the WLED interface, which also shows the IP of my FPP server.

This indicates that the WLED is receiving the data, and the FPP server is sending it as expected.

However, the effects are not being displayed. The lights remain completely off, as if the FPP isn't sending any visual data.

Interestingly, when the FPP isn't running, the WLED works perfectly fine with its own internal effects.


Here's what I've done so far to troubleshoot the issue:

1. I tested my FPP with a second WLED instance, and it still didn't work. Both WLED devices exhibit the same behavior, so the problem doesn't seem to be with the WLEDs.


2. I tested the WLED by sending data directly using xLights with the "Output-to-Lights" feature, and it worked perfectly. This confirms the WLEDs are functioning properly.


3. Based on this, the problem seems to be with the FPP sending data.



Has anyone experienced a similar issue or have any suggestions on what could be causing the FPP to fail in sending data correctly?

Thanks in advance!

[ricardo]

Update: Issue Resolved
I was able to resolve the issue! The problem was related to the compression mode I had chosen for the FSEQ file. Here's what I did:

• Changed the FSEQ compression mode from V2 Sparse to V2 Normal.
• In the xLights controller settings for WLED, I unchecked the option "Keep Channel Numbers".
• Enabled "Controller Sync" in the controller settings.
• Deleted all the existing FSEQ files and performed a Batch Render in xLights.
• Deleted the FSEQ files from the FPP and re-uploaded them.

After making these changes, the WLED started following the sequence sent by the Kulp32 perfectly again.
I hope this helps anyone who might face a similar issue in the future!