Resolving of Overlapping Groups Triggers the Same Entities Multiple Times

Johnson145 commented 9 months ago

The problem

I have several (cover) groups. They are not disjoint, i.e. the same (cover) entity is contained in multiple groups. If I trigger a service for all entities of the (cover) domain, the action gets triggered multiple times for the same entities. I would expect that the group resolving ensures to remove duplicates.

What version of Home Assistant Core has the issue?

core-2024.1.5

What was the last working version of Home Assistant Core?

not 100% sure, but probably this was the case all the time

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Potentially caused by the group integration.

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

cover:
  - platform: group
    name: group1
    unique_id: group1
    entities:
      - cover.cover1
      - cover.cover2

cover:
  - platform: group
    name: group2
    unique_id: group2
    entities:
      - cover.cover2
      - cover.cover3

Anything in the logs that might be useful for us?

No response

Additional information

Noticed this for the cover domain, because the physical switch makes a clicking noise each time it gets triggered. When I make a service call like

service: cover.open_cover
data: {}
target:
  entity_id: all

,the same switch clicks quite a few times right after another. I assume this is independent from the cover domain though.

My groups are defined in the yaml file, but not "the old style" and should therefore be equivalent to groups created via the helper UI (see provided sample snippet), right?.

Edits

I thought this is related to Assist, but it does seem to be a more general issue.
My groups are not defined "the old style" (compare group docs)

issue-triage-workflows[bot] commented 6 months ago

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.

Johnson145 commented 6 months ago

I've just updated Home Assistant to the latest version. The problem still exists.

issue-triage-workflows[bot] commented 3 months ago

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.

Johnson145 commented 3 months ago

Still the same...

issue-triage-workflows[bot] commented 3 days ago

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.

Johnson145 commented 3 days ago

Still the same...

home-assistant / core