ESP32-H2 with multiple lights crashes when second light is used

Author: chriiiishCreated Aug 11, 2026Updated Sep 18, 2026

The problem

The device has two addressable (SK6812) led strips attached to it. I can activate the first strip fine, but the second crashes the board.

So then I swapped the order of the lights in the yaml file. It appears that whichever light strip is the first item in the list works, but whichever is the second item fails.

(Crash detected in the Device Builder log viewer.)

Platform: ESP32
Installation: Home Assistant Add-on
ESPHome 2026.7.4 (compiled)
2026.7.4 (running)
Board: esp32-h2-devkitm-1

Decoded backtrace: 0x40802fb8: esp_cpu_wait_for_intr at /COMPONENT_ESP_HW_SUPPORT_DIR/cpu.c:64 0x40802fb8: esp_cpu_wait_for_intr at /COMPONENT_ESP_HW_SUPPORT_DIR/cpu.c:64 0x40802fa6: esp_cpu_wait_for_intr at /COMPONENT_ESP_HW_SUPPORT_DIR/cpu.c:57 (discriminator 1) 0x420959ae: prvCheckTasksWaitingTermination at /COMPONENT_FREERTOS_DIR/FreeRTOS-Kernel/tasks.c:4576 (inlined by) prvIdleTask at /COMPONENT_FREERTOS_DIR/FreeRTOS-Kernel/tasks.c:4301

Which version of ESPHome has the issue?

2026.7.4

What type of installation are you using?

Home Assistant Add-on

What platform are you using?

ESP32

Component causing the issue

ESP32-H2, SK6812 LED strip

YAML Config

yaml

# Board: Generic ESP32-H2 Board (Generic)
# Definition: definitions/boards/generic-esp32h2/manifest.yaml

esphome:
  name: kitchen-cupboard-bench-lights
  friendly_name: Kitchen Cupboard Bench Lights

esp32:
  variant: esp32h2
  framework:
    type: esp-idf

network:
  enable_ipv6: true
    
logger:

api:
  encryption:
    key: •
ota:
  - platform: esphome
    password: !secret kitchen_cupboard_bench_lights__ota_password

openthread:
  tlv: !secret thread_dataset_tlv

light:
  
  - platform: esp32_rmt_led_strip
    chipset: SK6812
    pin: GPIO13
    num_leds: 33
    rgb_order: GRB
    is_rgbw: true
    name: "Bench Cupboard LED Strip"
    
  - platform: esp32_rmt_led_strip
    chipset: SK6812
    pin: GPIO5
    num_leds: 33
    rgb_order: GRB
    is_rgbw: true
    name: "Bench Wall LED Strip"

Anything in the logs that might be useful for us?

txt

INFO Processing unexpected disconnect from ESPHome API for kitchen-cupboard-bench-lights @ fdbc:1fd3:7749:0:4eff:7ed3:3994:712a
WARNING Disconnected from API
INFO Successfully resolved kitchen-cupboard-bench-lights @ fdbc:1fd3:7749:0:4eff:7ed3:3994:712a in 0.000s
INFO Successfully connected to kitchen-cupboard-bench-lights @ fdbc:1fd3:7749:0:4eff:7ed3:3994:712a in 0.102s
INFO Successful handshake with kitchen-cupboard-bench-lights @ fdbc:1fd3:7749:0:4eff:7ed3:3994:712a in 0.323s
[E][esp32.crash:332]: *** CRASH DETECTED ON PREVIOUS BOOT ***
[E][esp32.crash:335]:   Reason: Fault - Unknown
[E][esp32.crash:339]:   Crashed core: 0
[E][esp32.crash:340]:   PC:  0x40802FB8  (fault location)
[E][esp32.crash:363]: Use: addr2line -pfiaC -e firmware.elf 0x40802FB8 0x40802FB8 0x40802FA6 0x420959AE

Additional information

Warnings and errors:

[E][esp32.crash:332]: *** CRASH DETECTED ON PREVIOUS BOOT ***
[E][esp32.crash:335]:   Reason: Fault - Unknown
[E][esp32.crash:339]:   Crashed core: 0
[E][esp32.crash:340]:   PC:  0x40802FB8  (fault location)
[E][esp32.crash:305]:   BT0: 0x40802FB8  (backtrace)
[E][esp32.crash:305]:   BT1: 0x40802FA6  (backtrace)
[E][esp32.crash:305]:   BT2: 0x420959AE  (stack scan)
[E][esp32.crash:363]: Use: addr2line -pfiaC -e firmware.elf 0x40802FB8 0x40802FB8 0x40802FA6 0x420959AE
[E][esp32_rmt_led_strip:175]: RMT TX timeout (x4)

Source: esphome/esphome

View original on GitHub View discussion on GitHub