Skip to content
BRUH Automation

Zones & Persons

Location plumbing: zones define the places your automations care about, and persons tie the humans of the house to the devices that reveal where they are. Both are normally UI-only — these services open them to Claude and automations.

The zone.home zone set in configuration.yaml isn’t editable — that’s a Home Assistant rule, and these services respect it.

Create zone

brain.create_zone

Create a new zone for location tracking.

Field Type Required Description
name text yes Name of the new zone.
latitude number yes Latitude of the zone center.
longitude number yes Longitude of the zone center.
radius number no Radius of the zone in meters (default 100).
icon icon no Icon for the zone.
passive boolean no Passive zones are only used for automations, not shown on the map. 
service: brain.create_zone
data:
  name: Gym
  latitude: 52.3702
  longitude: 4.8952
  radius: 150
  icon: mdi:dumbbell

🗣️ “Create a zone for the gym so automations know when I’m there.”

Update zone

brain.update_zone

Move, resize, rename, or restyle an editable zone. Only the fields you pass are changed.

Field Type Required Description
entity_id entity yes The zone to update.
name text no New name.
latitude number no New latitude of the zone center.
longitude number no New longitude of the zone center.
radius number no New radius in meters.
icon icon no New icon.
passive boolean no Passive zones are only used for automations. 
service: brain.update_zone
data:
  entity_id: zone.gym
  radius: 250

🗣️ “The gym zone keeps missing me in the parking lot — make it bigger.”

Delete zone

brain.delete_zone

Delete one or more UI-created zones.

Field Type Required Description
entity_id entity (list) yes Zone entities to delete. 
service: brain.delete_zone
data:
  entity_id:
    - zone.gym

🗣️ “Delete the gym zone.”

Create person

brain.create_person

Create a person, optionally linked to a Home Assistant user and with initial device trackers. Returns the person’s id as response data.

Field Type Required Description
name text yes The person’s name.
user_id text no Home Assistant user to link (from get_registry users).
device_tracker entity (list) no Initial device trackers for presence. 
service: brain.create_person
data:
  name: Alex
  device_tracker:
    - device_tracker.alex_phone

🗣️ “Add Alex to the house and track them with their phone.”

Delete person

brain.delete_person

Delete a UI-created person. YAML-defined persons are refused.

Field Type Required Description
entity_id entity yes The person entity to delete. 
service: brain.delete_person
data:
  entity_id: person.old_roommate

🗣️ “Remove the old roommate from presence tracking.”

Rename person

brain.rename_person

Rename a person. Only people created in the UI can be renamed; YAML-defined ones are refused.

Field Type Required Description
entity_id entity yes The person entity.
name text yes The new name. 
service: brain.rename_person
data:
  entity_id: person.alex
  name: Alexandra

🗣️ “Alex goes by Alexandra now — rename them.”

Add device tracker to person

brain.add_device_tracker_to_person

Attach one or more device trackers to a person for presence detection.

Field Type Required Description
entity_id entity yes The person entity.
device_tracker entity (list) yes Device trackers to attach. 
service: brain.add_device_tracker_to_person
data:
  entity_id: person.alex
  device_tracker:
    - device_tracker.alex_phone

🗣️ “Track Alex with their new phone.”

Remove device tracker from person

brain.remove_device_tracker_from_person

Detach one or more device trackers from a person.

Field Type Required Description
entity_id entity yes The person entity.
device_tracker entity (list) yes Device trackers to detach. 
service: brain.remove_device_tracker_from_person
data:
  entity_id: person.alex
  device_tracker:
    - device_tracker.old_phone

🗣️ “Stop tracking Alex’s old phone.”