Groups allow the user to combine multiple entities into one.
Check Developer Tools -> States and browse the Current entities: listing for all available entities.
# Example configuration.yaml entry group: kitchen: name: Kitchen entities: - switch.kitchen_pin_3 climate: name: Climate entities: - sensor.bedroom_temp - sensor.porch_temp awesome_people: name: Awesome People entities: - device_tracker.dad_smith - device_tracker.mom_smith
Set this to
true if the group state should only turn on if all grouped entities are on.
By default when any member of a group is
on then the group will also be
on. Similarly with a device tracker, when any member of the group is
home then the group is
home. If you set the
all option to
true though, this behavior is inverted and all members of the group have to be
on for the group to turn on as well.
The system can calculate group state with entities from the following domains:
When entities all have a single on and off state, the group state will be calculated as follows:
When a group contains entities from domains that have multiple
on states or only use
off, the group state will be
It is possible to create a group that the system cannot calculate a group state. Groups with entities from unsupported domains will always have an unknown state.
These groups can still be in templates with the
expand() directive, called using the
homeassistant.turn_off services, etc.