v0.3.4 - Neutral state labels

Changed

• The "outside usual area" sensor no longer reads "Safe" / "Unsafe". It was
  using Home Assistant's safety device class, which labels the states that way.
  Being outside a usual area isn't a safety judgement, so the sensor now shows
  Inside / Outside with a map-marker icon instead of a check or alert.

  Display only. The state is still on when the member is outside their
  usual area and off otherwise. Entity ids, attributes, availability and
  history are unchanged, so existing automations keep working.

  One thing that can change: anything that selected this sensor by
  device_class: safety — an auto-generated dashboard group, a template filter —
  will no longer match it. Select it by entity id instead.

Requires

Nothing new. Same as 0.3.3.

v0.3.3 - Position freshness

Added

• position_fresh attribute on the "outside usual area" sensor and the
  device tracker, next to position_age_seconds. true when the member's
  position was recently confirmed, false when PositionGuard is reporting
  their last known place. If the API doesn't send the field, the attribute is
  left out rather than set to false.

Changed

• A member who goes quiet inside a saved area now stays at_area. This is a
  change in PositionGuard itself, live since September 19, and it shows up here
  without any change to the integration: a phone that stops reporting while
  inside a saved area used to go stale after about 50 minutes, which made the
  "outside usual area" sensor unavailable. PositionGuard now keeps reporting
  at_area for up to 24 hours, and drops it on the first report from outside
  the area. The sensor stays available and off through that period.

  This changes behavior for existing automations. A sensor that used to go
  unavailable when someone's phone went quiet at home will now stay off.
  If an automation should only act on a recently confirmed position, add a
  condition on position_fresh being true, or on position_age_seconds.

  Availability itself still follows the stale status only. A member who goes
  quiet while away from every saved area still becomes unavailable, as in
  0.3.2.

Fixed

• README: a stale "outside usual area" sensor was described as off. It has
  been unavailable since 0.3.2. To automate on staleness, read
  safety_status on the device tracker, which stays available and reads
  stale.
• Tests now pin both rules: a held at_area member stays available, and the
  device tracker stays available with safety_status: stale.

Requires

PositionGuard API, September 2026 or later, for position_fresh. Against an
older API the attribute is simply absent and everything else behaves as in
0.3.2.

v0.3.2 - Per-area member counts

Added

• Per-area member counts. Each area in a group now gets a sensor with the
  number of members currently inside it, plus a count of members whose position
  is stale. Coordinate-free — the sensor reports how many, never where. Useful
  for occupancy automations: member_count == 0 is a reliable "everyone's out"
  trigger.

Changed

• A member whose position has gone stale now reports as unavailable
  instead of off. Previously a phone that hadn't reported recently looked
  identical to a member who was safely inside their usual area, so a sensor
  could alternate between "safe" and "outside" for someone who hadn't moved.
  Stale now means "no current data", which is what unavailable is for.

  This changes behavior for existing automations. Anything treating off
  as "safe" — template sensors, conditions, history graphs — will now see
  unavailable during stale periods. Add an availability check if your
  automation should only act on a known state.

  The raw position age remains in the entity attributes if you want to gate on
  freshness yourself.

Fixed

• Test suite regression: list_group_area_counts was mocked without async
  support, failing every coordinator refresh test.

Requires

PositionGuard API with Safety Zones enabled. Per-area counts require the
/groups/{id}/area-counts endpoint (backend, August 2026 or later).

v0.3.0 - Safety Zone status: outside-usual-area sensor + tracker attributes

What's new in v0.3.0

New: Safety Zone status. A dedicated binary_sensor.<member>_outside_usual_area per member per group, enabled by default. on only for a confirmed out-of-zone status — a stale position never triggers it, and if the server has no safety data for a member (feature not yet enabled on their account, or they're muted or in a public group), the sensor goes unavailable rather than pretending
everything is fine.

When available, three new attributes ride along on the existing tracker entities: safety_status (at_area / in_zone / out_of_zone / stale), safety_area (their own matched place, when you're allowed to see it), and position_age_seconds.

See the README's new "Getting notified when someone is outside their usual area" section for a copy-paste automation example.

Docs: added a multi-instance / multi-site support section covering running the integration across multiple HA instances.

Compatibility

Requires Safety Zone status enabled on the member's PositionGuard account (rolling out now with the iOS 2.0 / Android 0.9.0 release).
No configuration changes — entity IDs and setup are unchanged from v0.2.6.
The new binary sensor is enabled by default; disable it in entity settings if you don't want it.

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant

HACS will offer the update to existing installs automatically.

v0.2.6 - HACS to offer only published releases.

What's new in v0.2.6

HACS offered the default branch (main) alongside published releases in
the download dialog, so an install could end up tracking the branch and
never receive release-update notifications (manual redownload still
worked). Set hide_default_branch so HACS only offers published releases.

Compatibility

Requires Home Assistant 2026.3 or later
No configuration changes — entity IDs and setup are unchanged from v0.2.5.

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant

v0.2.5 - Resilience to brief network interruptions

What's new in v0.2.5

Presence is now more resilient to brief network interruptions. A single failed
update no longer momentarily shows family members as unavailable — entities hold
their last known state and recover on the next update. Sustained outages still
correctly show members as unavailable.

Compatibility

Requires Home Assistant 2026.3 or later
No configuration changes — entity IDs and setup are unchanged from v0.2.4.

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant

v0.2.4 - Fix for depreciated TrackerEntity import path

What's new in v0.2.4

Fix depreciated TrackerEntity import path.

Compatibility

Requires Home Assistant 2026.3 or later
All functionality unchanged from v0.2.3

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant

v0.2.3 - Refines dark mode icon

What's new in v0.2.3

Refines the dark-mode PositionGuard brand icon to use a transparent
background for better contrast and visual integration with Home Assistant's
dark theme.

No functional changes from v0.2.2 — purely a branding/icon refinement.

Compatibility

Requires Home Assistant 2026.3 or later
All functionality unchanged from v0.2.1

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant

v0.2.2 New Brand Icons

What's new in v0.2.2

Updates the PositionGuard branding assets with the new PG logos, including
updated light and dark mode icon variants.

No functional changes from v0.2.1 — purely a branding/logo update.

Compatibility

Requires Home Assistant 2026.3 or later
All functionality unchanged from v0.2.1

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant

v0.2.1 — HACS metadata

What's new in v0.2.1

Adds the hacs.json metadata file required for HACS distribution. Declares
minimum Home Assistant version 2026.3.0 (required for the new brand/
directory icon support introduced in v0.2.0).

No functional changes from v0.2.0 — purely a packaging fix.

Compatibility

• Requires Home Assistant 2026.3 or later
• All functionality unchanged from v0.2.0

Installation

Available as a custom repository in HACS:

1. HACS → three-dot menu → Custom repositories
2. Repository URL: https://github.com/positionguard/positionguard-homeassistant
3. Category: Integration
4. Install, then restart Home Assistant