RuView pins its LED driver so ESP32 firmware builds again on ESP-IDF 5.4

What changed

RuView's ESP32 CSI node firmware now asks for espressif/led_strip ~3.0.3 instead of ^3.0.0. The old range allowed the component manager to pick led_strip 3.1.0, which calls rmt_tx_switch_gpio, an API added in ESP-IDF 5.5. A clean build on the project's ESP-IDF 5.4 toolchain therefore failed. The new range stays on 3.0.x patch releases.

PR #2192 merged on October 10 at 17:15 UTC. The CI pipeline then published automated release v3122 at 21:54 UTC. The release has no attached firmware binaries; this story covers the source dependency fix. No new device capability or hardware test is established. This is a separate change from the earlier 0.8.13 prerelease watchdog and hardware story.

Get started

If you build the firmware yourself on ESP-IDF 5.4, pull the current source and let the component manager resolve dependencies again. The resolved led_strip version should be 3.0.x.

Documentation-verified only. We did not build, flash or run the firmware, and no build commands are suggested here.

Experimental commentary — acceptance test

Acceptance: a clean ESP32-S3 build on ESP-IDF 5.4 resolves led_strip 3.0.x and completes. The maintainers report exactly this; we did not reproduce it. Limitation: moving to ESP-IDF 5.5 or later will need this pin revisited before newer led_strip releases can be used.

Limits and verification

• Source: the merged diff of one file, idf_component.yml, at commit a71634a, and the v3122 release record.
• The build result is reported by the maintainers, not reproduced by the newsroom.
• No firmware binary, Docker image test or hardware behaviour was checked.