search

Aircoookie / WLED

Control WS2812B and many more types of digital RGB LEDs with an ESP8266 or ESP32 over WiFi!
https://kno.wled.ge
MIT License
14.57k stars 3.12k forks source link

Output not enabled when streaming from FPP #2927

Closed ReamsIT-Darren closed 11 months ago

ReamsIT-Darren commented 1 year ago

What happened?

I have several ESP32s running WLED to control lighting and am using FPP to stream the data to the controllers. The controllers are switched on using a smart plug and they all have Turn LEDs on after power up / reset to false. I have two different versions of WLED running, those running 0.13.0-b4 work perfectly, as soon as the FPP starts streaming the output is displayed, those with 0.13.3 seems will not switch the display on when the stream starts from FPP, instead I have to connect to the WLED controller and press the switch to enable output.

To Reproduce Bug

Setup an ESP32 with WLED 0.13.3 and a string of LEDs Set Turn LEDs on after power up / reset to false power off the esp32 Power up the ESP32 Run FPP on the network to the controller (I have used Xlights to create the sequence) Start the sequence

Lights will not come on until using the GUI to switch them on

Expected Behavior

I would expect the detection of a stream of 1.31 data to the controller to turn the outputs on.

Install Method

Binary from WLED.me

What version of WLED?

WLED 0.13.3 (build 2208222

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

softhack007 commented 1 year ago

Hi, could you explain a bit what is FPP ? Thanks.

ReamsIT-Darren commented 1 year ago

Yes Falcon Player is an application that can be used to drive light shows, a sequence is uploaded to it (In my case from Xlights) and I have FPP running on a Raspberry Pi. It then controls the running of the sequences and controls the messages sent to the WLED devices (or other control devices on the network).

Its Git Hub is here: https://github.com/FalconChristmas/fpp

softhack007 commented 1 year ago

Do you know which kind of protocol Falcon Player is using to control WLED? Maybe E1.31 ?

ReamsIT-Darren commented 1 year ago

Yes, it is E1.31, sorry I thought I had put that in the original description but seems I had forgotten to add it

softhack007 commented 1 year ago

Yes, it is E1.31, sorry I thought I had put that in the original description but seems I had forgotten to add it

Thanks, just saw that e1.31 is actually mentioned in your report - overlooked that.

Did you un-check turn LEDs on after power up/reset on the led settings page? Do you explicitly turn off LEDs from the web UI (on/off button) before starting to stream?

ReamsIT-Darren commented 1 year ago

Within the settings page on both versions of WLED I have turn LEDs on after power up/reset unchecked. I do not use the Web UI after power up to disable the LEDs, they will only start to work once I go into the Web UI and turn them on.

blazoncek commented 1 year ago

What kind of DMX mode have yo selected? It has to be one of single RGB or multi RGB. And try selecting Force max brightness.

ReamsIT-Darren commented 1 year ago

DMX Mode is multi RGB, I will try force max brightness once the current displays finish

ReamsIT-Darren commented 1 year ago

I don't believe I have changed any settings, but today as soon as FPP started playing back the lights were working, I had two days of it not working and failing each time I tested but today it is working each time I test. Maybe keep open for a couple of days but will close this if the bug does not appear again.

processor83 commented 1 year ago

I have two esp32 that freeze and need hard reset with e1.31 never happened on b4

ReamsIT-Darren commented 1 year ago

OK, I now know how to cause the issue, it seems if I open the WLED app at all on a phone (I do not have to select the controllers) it instantly turns the latest two ESPs with WLED 0.13.3 automatically switch the strings off

softhack007 commented 11 months ago

Closing, as there was no activity on this report for a long time. Additionally it seems that the original problem of the author did not re-appear.