Add sensors configuration docs

[DTTerastar]

Summary\n- document sensors configuration and GPIO/LED settings\n- link settings page to the new sensors page\n- add a UI screenshot\n\n## Testing\n- not run (docs-only)

Summary by CodeRabbit

• Documentation
  • Added comprehensive guide for configuring LEDs and GPIO sensors (PIR, Radar, Switches, Buttons) for the ESPresense device
  • Reorganized documentation for improved accessibility and navigation

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Documentation reorganization: LED and GPIO sensor configuration details are moved from the settings page to a new dedicated sensors documentation page, with a cross-reference link added to maintain discoverability. No code changes introduced.

Changes

Cohort / File(s)	Summary
Documentation Reorganization configuration/sensors.md, configuration/settings.md	New sensors documentation file created with comprehensive LED and GPIO sensor configuration guidance (addressable LEDs, PIR, Radar, Switches, Buttons, and tips). Settings page updated to remove sensor configuration details and add cross-reference link to new sensors page.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Possibly related PRs

• Split settings #187: Reorganizes configuration documentation by splitting settings content into separate focused documentation pages, aligning with the same documentation structure improvement approach.

Poem

🐰 Our docs now hop in tidy ways,
Sensors tucked in their own page,
Settings lean, the links guide true,
Configuration clear and new! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly matches the main change: adding documentation for sensors configuration (GPIO and LED settings).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch wip

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

configuration/sensors.md (1)

24-24: "GPIO pin number" is standard technical terminology.

Static analysis flagged "GPIO pin number" as redundant since "PIN" technically stands for "Personal Identification Number". However, in embedded systems and electronics documentation, "GPIO pin number" is widely understood standard terminology that clearly communicates the concept. No change needed.

Also applies to: 37-37, 45-45, 55-55, 65-65

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bc8902f and 78b02d1.

⛔ Files ignored due to path filters (1)

• images/sensors_screen.png is excluded by !**/*.png

📒 Files selected for processing (2)

• configuration/sensors.md
• configuration/settings.md

🧰 Additional context used

🪛 LanguageTool

configuration/sensors.md

[style] ~24-~24: This phrase is redundant (‘N’ stands for ‘number’). Consider using “pin”.
Context: ... etc.) * Pin (-1 to disable) - GPIO pin number for the LED data line, or -1 to disable...

(PIN_NUMBER)

---

[style] ~37-~37: This phrase is redundant (‘N’ stands for ‘number’). Consider using “pin”.
Context: ...IR motion pin (-1 for disable)** - GPIO pin number for PIR sensor, or -1 to disable * **PI...

(PIN_NUMBER)

---

[style] ~45-~45: This phrase is redundant (‘N’ stands for ‘number’). Consider using “pin”.
Context: ...ar motion pin (-1 for disable)** - GPIO pin number for radar sensor, or -1 to disable * **...

(PIN_NUMBER)

---

[style] ~55-~55: This phrase is redundant (‘N’ stands for ‘number’). Consider using “pin”.
Context: ... Switch pin (-1 for disable) - GPIO pin number for the switch, or -1 to disable * **Sw...

(PIN_NUMBER)

---

[style] ~65-~65: This phrase is redundant (‘N’ stands for ‘number’). Consider using “pin”.
Context: ... Button pin (-1 for disable) - GPIO pin number for the button, or -1 to disable * **Bu...

(PIN_NUMBER)

🔇 Additional comments (3)

configuration/sensors.md (2)

1-73: Excellent documentation structure and content!

The new sensors documentation page is well-organized, comprehensive, and clearly explains all LED and GPIO sensor configuration options. The hierarchical structure, consistent formatting, and helpful tips section make this easy to follow.

---

13-13: Image file exists and is properly included.

The referenced image sensors_screen.png is present in the images/ directory.

configuration/settings.md (1)

47-47: Good cross-reference to maintain discoverability.

The link to the new sensors page is clear and maintains easy navigation to the relocated LED and GPIO sensor configuration documentation. The relative link format [Sensors](sensors) is correct for Jekyll pages in the same directory.