home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.99k stars 31.03k forks source link

Cannot use ZHA group when only a single device is added to that group #122961

Open DarthSonic opened 3 months ago

DarthSonic commented 3 months ago

The problem

I cannot use ZHA group when only a single device is added to that group. So for example if I have a single light bulb "fooLight" in a group "fooGroup", I cannot select fooGroup in Automations or Node Red, only the fooLight directly. This is not very practical when I plan to add more devices to that group (I have to first setup the single device in automations, than chage to group if more than one device) or if I remove some device from that group (automation gets invalid if only a single device is left in group).

What version of Home Assistant Core has the issue?

core-2024.7.4

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

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] commented 3 months ago

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)

Hedda commented 3 months ago

FYI, this issue is also reported and discussed the the external zha library here (which zha depends on) -> https://github.com/zigpy/zha/issues/47

issue-triage-workflows[bot] commented 2 weeks 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.

DarthSonic commented 2 weeks ago

This is still not working and has major impact when you remove devices from a group that is used in multiple automations, scripts and flows and a single device is left in that group. Then you must update als references to that group to use only the single device directly.