Duplicate devices in Default Lightlink Group

[lindhe]

The problem

There seems to be duplicate devices registered in the "Default Lightlink Group" (what that is, I am unsure of) in ZHA.

What version of Home Assistant Core has the issue?

core-2024.2.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

ZHA

Link to integration documentation on our website

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

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[bot]]

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

Code owner commands

Code owners of zha 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 zha 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)}}

---

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

[puddly]

Zigbee groups are made up of Zigbee endpoints, not devices. A single device can have multiple endpoints.

[lindhe]

I don't get what you mean. Does the screenshot not look anomalous?

[puddly]

Oh, you mean the coordinator device being listed twice? That's just a minor display bug for the frontend: https://github.com/home-assistant/frontend/

[lindhe]

Ok. Should I post the issue over there instead, or shall we wait for an admin to move it?

[pbpbpb01]

same issue here while also having response issues, so rather have this bug fixed to make sure it has no cascading effects

[issue-triage-workflows[bot]]

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.

[lindhe]

Waiting for response.

[DevSecNinja]

Also wondering what we should do with this group. I have my Conbee II twice in there. Is it safe to remove?

[dkathmann]

I'm having this issue too; my SkyConnect is listed three times. I also would like to know if this group can be deleted without any side effects.

[TheJulianJES]

It's not an issue. The coordinator is added to the LightLink group with all of its endpoints (1 and 2 at the moment). The LightLink group can be used by some devices and the coordinator should be in those groups to receive those commands (this is important for EZSP based coordinators).

There's no actual issue here. The UI could be a bit clearer that there are two separate endpoints from the same device in the group, but that can be seen in the "Remove Device" table.

[issue-triage-workflows[bot]]

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.