WLED Segment Mismatch

[wernerhp]

The problem

HA switch entities don't match WLED Segments.

Segment Names

Segment names don't pull through to HA.

HA	WLED	Comment
Garage Door Light (WLED)	Power	This is expected ot be the Main segment. With Multiple Segments enabled, the color incorrectly shows as blue (Segment 0) instead of just indicating state on/off
Main	Blue	Segment 0 in WLED renamed to Blue, but pulls in as Main in HA. Expect Blue (or Segment 0 if the name can't be pulled in)
Segment 1	White	Segment 1 in WLED renamed to White, but pulls in as Segment 1 in HA. Expect White
Segment 2	Green	Segment 2; same comment as Segment 1
Segment 3	Gold	Segment 3; same comment as Segment 1
Segment 4	Black	Segment 4; same comment as Segment 1

Single Segment

WLED Power state matches Garage Door Light (WLED) in HA
WLED Segment 0 state pulls through as Main in HA, but the state does not match for a single segment.

Click to expand

POWER	HA	WLED
ON
OFF

Multiple Segments

The Main segment only seems to work when there are more than 1 segments enabled (see above screenshots where Main is always off)

Main does not match the color of Segment 0. Intead, Garage Door Light (WLED) shows the color of Segment 0
Expected: Main should show

POWER (ON) and Segment 0 (Blue) seem to be swapped around when there are multiple segments.

Click to expand

Power	HA	WLED
ON
OFF

What version of Home Assistant Core has the issue?

core-2024.8.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

wled

Link to integration documentation on our website

https://www.home-assistant.io/integrations/wled/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (wled) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of wled can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign wled Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

wled documentation
wled source
_{^{(message by IssueLinks)}}

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[wernerhp]

Bump

[mateuszdrab]

I agree that this is a weird issue, and generally the naming does not make sense.
The naming style that would make sense to me would be [WLED Light Name] [Segment Name], the aggregate entity should just be named [WLED Light Name]. No need to add main.

The current setup confuses me every time I look at it and the only fix to it is renaming the entities manually.

[mateuszdrab]

I had a play with the code of the wled components and can confirm that segment names are not pulled.

I made a few changes and commented out the logic that makes segment 0 take name of the entire WLED device and instead made the main entity take that name.

Looks like this

Makes much more sense to me, I will see if I can make it take the name of the actual segments.

[mateuszdrab]

If you want to try it yourself 24d893e

[wernerhp]

Thanks for looking into this!
The colours also didn't match up with the segments AFK for a bit, so can't test ATM.

[mateuszdrab]

Thanks for looking into this!
The colours also didn't match up with the segments AFK for a bit, so can't test ATM.

Interesting, I haven't noticed that on my side but to be honest I've only had more than one segment in my light for the past few days.

[wernerhp]

Click to expand images in the OP.

Here's the preset
wled_presets_Garage Door Light (BMW).json

[mateuszdrab]

Click to expand images in the OP.

Here's the preset
wled_presets_Garage Door Light (BMW).json

Unfortunately the behavior you're experiencing is correct.

Segment 0, Blue from WLED takes the name of the WLED device when it shows up in Home Assistant.
White, Green, Gold, Black are segments 1-4 and show in HA respectively.
The main entity is supposed to control the entire WLED device.

It makes little sense to me, after my modifications, the Blue entity would show as segment 0, aligning more with what you see in WLED and the main entity would take the name of the WLED device to imply it's controlling everything.

Does that clear it up a bit?

[wernerhp]

Yeah, ok, that makes sense. Your change seema sound.

What colour should the main segment represent though? It differs for single vs multi segment.