Closed leoherzog closed 2 years ago
The solution is already available in my fork, dev branch. May be incorporated into master at some (not so far) point.
This is a limitation of ESP8266 and can be slightly mitigated by disabling some features during compile.
Confirmed that this issue is not present on the ESP32.
Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. Thank you for using WLED!
This issue is still present on the ESP8266
@leoherzog which version are you talking about?
@Aircoookie this will most likely need a JSON buffer 10k in size if @leoherzog is using the latest code. ArduinoJson Assistant calculates 10000 bytes minimum size (but we have mitigated nested col arrays, so perhaps a bit less is needed).
Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. Thank you for using WLED!
This issue is still present on the ESP8266 with v0.13.1
I've added the following line at the begining of populatePalettes
as a workaround and seems ok now.
function populatePalettes(palettes)
{
if (palettes === null) palettes = [];
This seems valid for my ESP8266 with only 5 segments... But I guess, given the feeling it's a very edgy case, it won't be fixed?
@igorsantos07 You are missing key information. The underlying issue has been fixed.
Describe the bug On a fresh boot of WLED 0.12.0, if I add 11 additional segments via UI or API, the
palettes
key becomesnull
and the Web UI throws errors.To Reproduce Boot WLED, create 11 additional segments. In my case, I have 60 LEDs and each segment is 5 in length.
Fresh boot:
WLED version
Additional context
Fresh boot state:
Immediately after I go to the "Effects" tab and add 11 more segments; 0-5, 5-10, 10-15, etc: