-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support groups created via UI/Helpers #529
Comments
The difference, in my opinion, is that you are using Or is there a way to create a group via the HA UI that is an actual |
I don't see such option unfortunately. I don't know why when you create a group via helpers it doesn't create an entity in the group domain but a regular sensor. I have a mixed feelings regarding adding the support to "unpack" such groups. What if someone wants to actually see it as a single entity in the card? I will think about this more. I'm open as well for suggestions |
Fully understand your concerns. Maybe this can be implemented as an optional parameter |
I just stumbled upon this card and it looks amazing. Just one little thing about the groups functionality.
Describe what is wrong
Using existing HA groups to populate the individual entities would be amazing, as this would spare me from adding the same entities in multiple places.
My understanding is: I add the group as the only entity and this would populate all individual devices, according to
group.switches_batteries
in this explanation: https://github.com/maxwroc/battery-state-card#battery-groupsHowever, the new UI groups in HomeAssistant no longer follow the
groups.*
terminology but are added as asensor.*
Adding this sensor results in a single sensor being added, rather than all the containing entities.
How can I get this to work using the new UI groups from HomeAssistant?
Card configuration
Screenshot
Version
v2.1.1
The text was updated successfully, but these errors were encountered: