Skip to content

Add warning to prevent flicker #5494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: current
Choose a base branch
from
Open

Add warning to prevent flicker #5494

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e103368
Add warning to prevent flicker
sanchosk Oct 19, 2025
aa62e92
Fixed the styling to match the expected checks
sanchosk Oct 19, 2025
4ea5164
Removed training spaces
sanchosk Oct 19, 2025
a8c08e4
Trailing spaces?
sanchosk Oct 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion content/components/light/esp32_rmt_led_strip.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,10 @@
num_leds: 30
chipset: ws2812
name: "My Light"
```

Check failure on line 20 in content/components/light/esp32_rmt_led_strip.md

View workflow job for this annotation

GitHub Actions / build 

Fenced code blocks should be surrounded by blank lines [Context: "```"]

**Important note** In some specific cases, the RMT component might cause flicker of longer LED strips. The fix seem to be to disable the wifi power saving by setting
[power_save_mode](/components/wifi/#power-save-mode) to none in [wifi component](/components/wifi).
Copy link
Contributor

@coderabbitai coderabbitai bot Oct 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix markdown formatting and grammar issues.

  1. Markdown linting error: Line 20 ends the code fence, but line 21 immediately follows without a blank line. Markdown fenced blocks should be surrounded by blank lines (addresses pipeline failure MD031).
  2. Grammar: "The fix seem to be" should be "The fix seems to be" (subject-verb agreement).
  3. Capitalization: "wifi" should be "Wi-Fi" per standard branding.
  4. Text flow: The note awkwardly breaks across lines 21–22. Reformat for clarity.

Apply this diff:

 ```yaml
 light:
   - platform: esp32_rmt_led_strip
     rgb_order: GRB
     pin: GPIOXX
     num_leds: 30
     chipset: ws2812
     name: "My Light"

-Important note In some specific cases, the RMT component might cause flicker of longer LED strips. The fix seem to be to disable the wifi power saving by setting


<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 GitHub Actions: Lint</summary>

[error] 20-20: markdownlint: MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines.

</details>
<details>
<summary>🪛 GitHub Check: build</summary>

[failure] 20-20: 
Fenced code blocks should be surrounded by blank lines [Context: "```"]

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

In content/components/light/esp32_rmt_led_strip.md around lines 20–22, fix the
markdown and wording: ensure the fenced code block is surrounded by a blank
line, change "The fix seem to be" to "The fix seems to be", capitalize "Wi-Fi"
everywhere, add a colon after "Important note", reword "flicker of longer LED
strips" to "flicker on longer LED strips", and format the power_save_mode value
as inline code and the Wi‑Fi component name consistently while keeping the
existing links.


</details>

<!-- This is an auto-generated comment by CodeRabbit -->

## Configuration variables

Check failure on line 23 in content/components/light/esp32_rmt_led_strip.md

View workflow job for this annotation

GitHub Actions / build 

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "## Configuration variables"]

- **pin** (**Required**, [Pin](#config-pin)): The pin for the data line of the light.
- **num_leds** (**Required**, int): The number of LEDs in the strip.
Expand Down
Loading