Make main light the primary entity when keep_main_light is on in WLED#45148
Draft
mik-laj wants to merge 2 commits intohome-assistant:nextfrom
Draft
Make main light the primary entity when keep_main_light is on in WLED#45148mik-laj wants to merge 2 commits intohome-assistant:nextfrom
mik-laj wants to merge 2 commits intohome-assistant:nextfrom
Conversation
home-assistant
Bot
added
has-parent
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the WLED integration documentation to explain how segment entities are created and named, and how enabling the “Keep Master Light” option affects which light entity is considered primary.
Changes:
- Reworks the segment documentation into a dedicated “Using WLED segments” section, including naming behavior for segment 0.
- Adds/expands documentation for the “Keep Master Light” option and its impact on entity naming/primary entity selection.
- Refactors the “Supported functionality” light entity description to reference the segment behavior section.
| The **WLED** integration provides the following entities. | ||
| If WLED has 1 segment defined (the default), that one segment controls the | ||
| whole LED strip. Home Assistant creates a single light {% term entity %} named | ||
| after the device (e.g., "Garage Door Light") to control the strip. |
Comment on lines
+105
to
+107
| of the device and is named after the WLED device (e.g., "Garage Door | ||
| Light"). It controls the overall power and brightness of the entire strip. | ||
| - **Segment 0** gets its own named {% term entity %} (e.g., "Garage Door Light |
Comment on lines
+78
to
+82
| If WLED has 2 or more segments, each segment gets its own light | ||
| {% term entity %}, as well as its own color palette, speed, intensity, freeze, | ||
| and reverse {% term entities %}. Additionally, a master light {% term entity %} | ||
| is created. This master {% term entity %} controls the strip power and overall | ||
| brightness applied to all segments. |
|
|
||
| The integration creates the following light {% term entities %}: | ||
|
|
||
| - **Segment lights**: one light {% term entity %} per segment, controlling its color, effect, speed, and brightness. |
Comment on lines
+58
to
+59
| Keep Master Light: | ||
| description: Keep the master light entity even when there is only 1 segment. See [Keep Master Light option](#keep-master-light-option) for details. |
21 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.