Person component, (group.all_persons)

Configuration Frontend
1

Hi, i am using the new person component and it works just fine, but;
What about implementing “group.all_persons”?
It would be in handy if all automations that uses presence is based on if there is people at home or not, or coming home/leaving.
Then all that has to be done is to add/remove persons from the person menu if there is any changes of the household members, instead of updating group.yaml by text editor.

Or it could be an even better solution if it was possible to add/remove persons from groups from the menu. Then one could make groups for spesific tasks like “if persons in X group is coming home, then do this”.

I’m not an python programmer, but it would be nice if someone sees the advantages of implenenting it :slight_smile:

Best regards HomEd

2

You could just make the group yourself. I setup persons, but don’t currently use it. My in use setup is a group for each person to combine the trackers (essentially the same as persons). Then I have another group that combines all of my people groups. These work just fine and I’d assume using the person.xxxx entities under a group would too.

3

Add a vote here: Group.all_people based on person component

2 Likes
4

Those auto-generated groups are likely going away.