Hardware Setup Length can't be saved after 659

[Undermozes]

What happened?

When you want to save a number above the 659 in the LED & hardware setup it resets again to 30.

Tried to set it to 720

After save, its again 30

To Reproduce Bug

Go to LED & Hardware setup
In Hardwaresetup LED outputs choose a length greater then 659.
After save, its set at 30 again

Expected Behavior

Go to LED & Hardware setup
In Hardwaresetup LED outputs choose a length greater then 659.
After save, its saved the number

Install Method

Binary from WLED.me

What version of WLED?

Nightly Release 20250326

Which microcontroller/board are you seeing the problem on?

ESP8266

Relevant log/trace output

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[DedeHai]

works just fine. maybe your config is broken.

[e8johan]

Mine behaves the same. What part of the config should I look in to?

Also, this happened in the latest version upgrade.

[willmmiles]

Mine behaves the same. What part of the config should I look in to?

Also, this happened in the latest version upgrade.

Can you send a backup of your config prior to setting the larger value? Are you also using an ESP8266? I'll see if I can replicate it locally. Offhand, "just doesn't save" usually means "the software couldn't apply the configuration" -- unfortunately we don't yet have a way to pass a "why not" message back.

[e8johan]

Sorry, no, I don't have a backup (which is annoying). I just upgraded through home assistant and never thought of that part.

I have a 900 LED strip that used to work. And I'm using and esp8266. Specifically this one: https://www.amazon.se/GLEDOPTO-LED-ljusremsa-APP-kontroll-belysningsl%C3%A4gen-g%C3%B6r-det-sj%C3%A4lv/dp/B0CB5C7GS6?pd_rd_w=fE94b&content-id=amzn1.sym.762f1299-afc8-404d-854b-e91ea0589751&pf_rd_p=762f1299-afc8-404d-854b-e91ea0589751&pf_rd_r=CV188HBVP4V9BX9KG8SQ&pd_rd_wg=FjJko&pd_rd_r=96495cb0-aa4f-438a-b8f4-e6c1d0780d0b&psc=1&ref_=pd_bap_m_grid_rp_0_0_sa with three of these in a chain: https://www.amazon.se/WS2812B-LED-remsa-Anpassningsbar-DIY-design-Heminredning/dp/B0BTVB7WRY?pd_rd_w=fE94b&content-id=amzn1.sym.762f1299-afc8-404d-854b-e91ea0589751&pf_rd_p=762f1299-afc8-404d-854b-e91ea0589751&pf_rd_r=CV188HBVP4V9BX9KG8SQ&pd_rd_wg=FjJko&pd_rd_r=96495cb0-aa4f-438a-b8f4-e6c1d0780d0b&pd_rd_i=B0BTVB7WRY&psc=1&ref_=pd_bap_m_grid_dv_rp_0_1_ec_ppx_yo2_mob_b_ts_rp_3_i. All powered by a 10A psu.

[DedeHai]

When I tested it back when this was raised I could not reproduce it, but I can confirm I saw this issue in 0.16.

[willmmiles]

Sorry, no, I don't have a backup (which is annoying).

Oh, I don't need a config from the old version, just whatever config you've got now. "Backup config" is the button in the settings screen to download it.

[willmmiles]

When I tested it back when this was raised I could not reproduce it, but I can confirm I saw this issue in 0.16.

Best guess offhand is that there's an OOM/fragmentation issue with ESP8266es and large setups. If that turns out to be the case, we should land #4791 first before getting too deep in to this one.

[DedeHai]

I don't think that PR fixes this IIRC I have seen it while running tests on that but I could be mistaken.

[willmmiles]

I agree, If this is an allocation problem, I don't think that PR will fix it. It's more that if we have to get in to changing when and where allocations are done to fix this case, there's a good chance it'd lead to a bunch of merge conflicts with #4791, so I'd prefer to merge that PR first before starting on any other changes to allocation planning.

[DDock]

I just wanted to chime in as after an update my "light bulb" I made stopped working. Found the same thing. It is made of 3 of the 256 matrix panels. Can only set a maximum of 659 when it would be 768. Was working perfectly before the update. I think Home Assistant initially did the update. Tried flashing the 0.15.1 firmware again and still have the same issue. I am using a ESP8266 as a controller.