-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
Update partition.rst #4561
base: current
Are you sure you want to change the base?
Update partition.rst #4561
Conversation
Provided an extra example for RGBIC + CCTIC ledstrips. It took me quite some time to find this myself so I thought the docs could use a extra example
WalkthroughThe pull request updates the Changes
Suggested ReviewersThank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
components/light/partition.rst (2)
93-105
: Enhance the example with additional context and complete patterns.While the example is technically correct, consider these improvements for better clarity:
- Add the total number of LEDs in the comment section
- Explain why RGBIC and CCTIC LEDs need to be addressed separately
- Show a more complete pattern instead of using "etc." For example:
# Example for joining multiple segments of one source. # For example when using RGBIC + CCTIC addressable LED strips. # These can have the RGBIC LEDs on the even addresses and the CCTIC LEDs on the odd addresses. +# Assuming a strip with 10 LEDs total (5 RGBIC + 5 CCTIC alternating) +# Note: Creating many single-LED segments may impact performance - platform: partition name: "Odd leds" segments: # first odd led - id: light1 from: 1 to: 1 # second odd led - id: light1 from: 3 to: 3 - # etc. + # third odd led + - id: light1 + from: 5 + to: 5 + # fourth odd led + - id: light1 + from: 7 + to: 7 + # fifth odd led + - id: light1 + from: 9 + to: 9 - platform: partition name: "Even leds" segments: # first even led - id: light1 from: 0 to: 0 # second even led - id: light1 from: 2 to: 2 - # etc. + # third even led + - id: light1 + from: 4 + to: 4 + # fourth even led + - id: light1 + from: 6 + to: 6 + # fifth even led + - id: light1 + from: 8 + to: 8Also applies to: 106-118
93-118
: Consider adding a performance note.Since this example creates many single-LED segments, it would be helpful to reference the existing performance note in the documentation or add a specific note about the trade-offs of this approach.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
components/light/partition.rst
(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
components/light/partition.rst (1)
Pattern **
: - Do not generate or add any sequence diagrams
🔇 Additional comments (1)
components/light/partition.rst (1)
90-92
: LGTM! Clear introduction of the example's purpose.The comments effectively explain the use case for RGBIC + CCTIC LED strips and the even/odd addressing pattern.
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Provided an extra example for RGBIC + CCTIC ledstrips. It took me quite some time to find this myself so I thought the docs could use a extra example
Description:
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable): esphome/esphome#
Checklist:
I am merging into
next
because this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
current
because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/index.rst
when creating new documents for new components or cookbook.