Opening `/index` with removed or broken LED hat reboots the device (LN882H/BL602)

[C0rn3j]

trafficstars

Firmware:

• Version: 1.18.111
• Device: (eWeLink) RGBCW GU10 LED Bulb Five Channel PWM (EW-GU10-E)
• Chip/model: BL602
• Device config:

{
  "vendor": "Tuya",
  "bDetailed": "0",
  "name": "Full Device Name Here",
  "model": "enter short model name here",
  "chip": "BL602",
  "board": "TODO",
  "flags": "1024",
  "keywords": [
    "TODO",
    "TODO",
    "TODO"
  ],
  "pins": {
    "2": "PWM;5",
    "3": "PWM;1",
    "14": "PWM;2",
    "20": "PWM;3",
    "21": "PWM;4"
  },
  "command": "",
  "image": "https://obrazki.elektroda.pl/YOUR_IMAGE.jpg",
  "wiki": "https://www.elektroda.com/rtvforum/topic_YOUR_TOPIC.html"
}

I have a GU10 bulb where I seemingly fried warm light with hot air.

If I set flag 12 (Flag 12 - [LED] Remember LED driver state (RGBCW, enable, brightness, temperature) after reboot)

I end up with this when accessing /index and the light reboots:

I have to manually go to /cfg and disable it, then I see the reason for reboot was BL_RST_SOFTWARE_WATCHDOG and temp jumped up to 150°C and it slowly goes down.

Regular usage seems to make temps jump up to 130°C, am not sure how accurate this is.

Fine boot:

My questions:

1. Would desoldering the broken warm light module (since there's many) make the rest work fine?

2. Why does remembering the settings fail in this way when leaving it off and setting everything manually works just fine?

[C0rn3j]

I have unfortunately run into this issue again, but this time with LN882H (note to self: #005) - it looks like any version from 1.17.650 to the current latest 1.18.123 suffers the problem.

That ate quite a bit of my time thinking I was chasing this issue down and not the #1671 I was actually trying to debug :/

I can reproduce this issue even with the LED hat removed.

How can I get the current values from Flag 12 - [LED] Remember LED driver state (RGBCW, enable, brightness, temperature) after reboot - I suspect a broken value in there that got saved and is trying to be loaded on boot is doing the thing and I don't want to clear it by unsetting the flag.

I am unsure if the LED hat on this device is in working state or not, it should be working fine however.

[C0rn3j]

Looks like I was partially(?) right, clearing the flag 12 alone did not help, I had to set specific light (turning on did not work) via Home Assistant (MQTT), then all cleared up on my #005 (OpenLN882H 1.18.123) LED, visiting /index was freezing/crashing it before.

So it looks like the LED saves a bad state under some circumstance, and then crashes whenever loading /index if it loads it.

But now I have another issue, where I disconnected the LED hat, turned the bulb on and played with the flag 12 saving the state, and now any visit to any page end up freezing the bulb, even after removing Flag 12 and rebooting.

I have to hard power on and off, after which it works for about 15 seconds, I can set light in HA, and then it freezes.

Which I suppose is different from the crash issue here?