ESP32 random off - incl. debug log

Issues
1

My ESP32 with WLED 0.14.0-b1 turns it self off (and on) randomly. After toggling the power button in the UI, typically after 30-60s the system turns the LED strip off by it self. The UI is still active and under Info the up-time shows that there hasn’t been a reboot or something. I hope to find some help here.

I managed to upload adebug version of WLED 0.14, which gave me the following data. The first " Sending WS data" is me giving the ON input via the webfront end. The last " Sending WS data" came out of now where and is probably the bit that is ruining my WLED experience:

Wifi state: 3
State time: 0
NTP last sync: 999000000
Client IP: 192.168.0.100
Loops/sec: 2285
UM time[ms]: 0/1
Strip time[ms]: 0/1
Segments: 2 → 288B
Modes: 4187=748B
Data: 4187=748B
Map: 2*0=0B
JSON buffer locked. (11)

JSON buffer released. (11)
JSON buffer locked. (12)
JSON buffer size: 2076 for WS request (1150).
heap 197892

Sending WS data to a single client.
JSON buffer released. (12)
JSON buffer locked. (12)
JSON buffer size: 2076 for WS request (1150).
heap 197736

Sending WS data to multiple clients.
JSON buffer released. (12)
Local time: 19:41
Not-Found HTTP call:

URI: /presets.json
WS FileRead: /presets.json
JSON buffer locked. (17)
JSON buffer size: 2075 for request: 3
JSON buffer released. (17)

Not-Found HTTP call:
URI: /presets.json
WS FileRead: /presets.json
JSON buffer locked. (17)
JSON buffer size: 2075 for request: 3
JSON buffer released. (17)

JSON buffer locked. (14)
JSON buffer released. (14)
JSON buffer locked. (17)
JSON buffer size: 793 for request: 1
JSON buffer released. (17)

JSON buffer locked. (12)
JSON buffer size: 2076 for WS request (1153).
heap 197312

Sending WS data to multiple clients.
JSON buffer released. (12)
—DEBUG INFO—
Runtime: 960419
Unix time: 1684690883,419
Free heap: 199956

  • The above is captured from the “naked” ESP32 connected to my PC’s USB port, no addtional power. I get the same behaviour with this board hooked on my QuinLED digi UNO v3, trying two different power sources.
  • When the board was on version 0.13.3 (it was delivered like that 3 weeks ago) it showed the same behaviour.
  • I have no Macro’s or add-ons installed.
  • With or without the power-protection: same behaviour.
2

I disabled the WLED entity in HomeAssistant and this seems to solve the above issue.

The odd thing is that I didn’t make an automation or anything in HomeAssistant yet - I’ve only added the entity in order to be able to manually control WLED. Yet, undeniable, HomeAssistant was sending OFF commands to WLED - a later concern.

3

HA is polling WLED too often.
And the debug dump is without issues.

4

Had the same issue with HomeAssistant. I’m normally using ioBroker and wanted to give HomeAssistant a try but it always powered off my WLED lamps. So i disabled HomeAssistant.