Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a trigger or condition inside automation setups.
zone integration uses YAML sequences to configure multiple zones:
# Example configuration.yaml entry zone: - name: School latitude: 32.8773367 longitude: -117.2494053 radius: 250 icon: mdi:school - name: Work latitude: 32.8753367 longitude: -117.2474053 # This will override the default home zone - name: Home latitude: 32.8793367 longitude: -117.2474053 radius: 100 icon: mdi:account-multiple
The friendly name of the zone.
The latitude of the center point of the zone.
The longitude of the center point of the zone.
The radius of the zone in meters.
The icon to show instead of name.
To only use the zone for automation and hide it from the frontend and not use the zone for device tracker name.
If no configuration is given, the
zone integration will create a zone for home. This zone will use location provided in the
configuration.yaml file and have a radius of 100 meters. To override this, create a zone configuration and name it ‘Home’.
Devices that are in the zone ‘Home’ will not appear on the map in the Home Assistant UI.
It is preferred to pick an icon to use for your zone. Pick any icon that you can find on materialdesignicons.com and prefix the name with
mdi:. For example
zoning is the state a
zone has when it is configured. A
zone doesn’t have another state; all configured zones are
zoning all the time.