Person
The Person integration ties together one or more presence-detection entities so that WoowTech can reason about who is at home rather than merely which devices are present. Every person you define becomes its own entity, and that entity carries a single location state computed from whatever device trackers you have attached to it.
How the location state is decided
A single person can be followed by several trackers at once — for example the router that sees their phone on the Wi-Fi, a Bluetooth beacon in their car, and a GPS-based companion app. Because those sources can disagree, WoowTech resolves the person's state using a fixed order of preference:
- First it examines any network-based (non-GPS) trackers — routers, Bluetooth presence, and similar — that currently report
home. If more than one qualifies, the one updated most recently is chosen. - If none of those report
home, it falls back to the GPS-capable trackers, again favoring the freshest update. - When everything reports away, the person is set to
not_homebased on the most recently updated tracker.
The practical effect is this: while you are at the house, stationary network trackers take precedence over GPS, which prevents the location from flapping when GPS drifts indoors. Once you head out, GPS becomes authoritative and the network trackers serve only as a backstop.
Creating a person from the interface
The quickest route is the built-in management screen. Open Settings > People, choose Add person, and then:
- Enter a display name and, optionally, attach a photo.
- Decide whether this person may sign in to WoowTech.
- If sign-in is permitted, set a username, a password, the access level, and whether the account holds administrator rights.
- Select the device trackers that should drive this person's presence.
Defining people in YAML
The integration is already active whenever default_config: appears in your configuration.yaml — that is what enables the UI flow above. If you would rather declare people directly in YAML, use a person: block:
person:
- name: Mariko
id: mariko_2741
device_trackers:
- device_tracker.mariko_pixel
- device_tracker.mariko_car
Configuration keys
| Key | Required | Meaning |
|---|---|---|
id |
yes | A stable, unique string that identifies the person internally. |
name |
yes | The label shown for the person throughout the interface. |
user_id |
no | Associates the person with an existing WoowTech login account. |
device_trackers |
no | A list of tracker entity IDs whose states drive this person's location. |
Actions
| Action | What it does |
|---|---|
person.reload |
Re-reads the YAML person definitions without restarting WoowTech. |
Adding a picture
To give someone a photo, open their page in the interface and either click to browse for an image or drag a file straight onto the page. After uploading you can crop the image to frame it however you like.
Person
The Person integration ties together one or more presence-detection entities so that WoowTech can reason about who is at home rather than merely which devices are present. Every person you define becomes its own entity, and that entity carries a single location state computed from whatever device trackers you have attached to it.
How the location state is decided
A single person can be followed by several trackers at once — for example the router that sees their phone on the Wi-Fi, a Bluetooth beacon in their car, and a GPS-based companion app. Because those sources can disagree, WoowTech resolves the person's state using a fixed order of preference:
- First it examines any network-based (non-GPS) trackers — routers, Bluetooth presence, and similar — that currently report
home. If more than one qualifies, the one updated most recently is chosen. - If none of those report
home, it falls back to the GPS-capable trackers, again favoring the freshest update. - When everything reports away, the person is set to
not_homebased on the most recently updated tracker.
The practical effect is this: while you are at the house, stationary network trackers take precedence over GPS, which prevents the location from flapping when GPS drifts indoors. Once you head out, GPS becomes authoritative and the network trackers serve only as a backstop.
Creating a person from the interface
The quickest route is the built-in management screen. Open Settings > People, choose Add person, and then:
- Enter a display name and, optionally, attach a photo.
- Decide whether this person may sign in to WoowTech.
- If sign-in is permitted, set a username, a password, the access level, and whether the account holds administrator rights.
- Select the device trackers that should drive this person's presence.
Defining people in YAML
The integration is already active whenever default_config: appears in your configuration.yaml — that is what enables the UI flow above. If you would rather declare people directly in YAML, use a person: block:
person:
- name: Mariko
id: mariko_2741
device_trackers:
- device_tracker.mariko_pixel
- device_tracker.mariko_car
Configuration keys
| Key | Required | Meaning |
|---|---|---|
id |
yes | A stable, unique string that identifies the person internally. |
name |
yes | The label shown for the person throughout the interface. |
user_id |
no | Associates the person with an existing WoowTech login account. |
device_trackers |
no | A list of tracker entity IDs whose states drive this person's location. |
Actions
| Action | What it does |
|---|---|
person.reload |
Re-reads the YAML person definitions without restarting WoowTech. |
Adding a picture
To give someone a photo, open their page in the interface and either click to browse for an image or drag a file straight onto the page. After uploading you can crop the image to frame it however you like.
Start writing here...