Bug: device_tracker.see service no longer updates person's "in_zones" attribute / zone count stays at 0 in 2026.7.0

[Gnu-Master]

The problem

Since updating to Core 2026.7.0, updating a virtual device tracker via the device_tracker.see service changes the person's state correctly to home, but it fails to update the person's in_zones attribute. As a result, the zone.home state does not increment and stays at 0, breaking all automations relying on the zone count.

Before 2026.7.0, using device_tracker.see with location_name: home and source_type: router correctly assigned the person to the home zone.

We did extensive troubleshooting and tried several workarounds, but none of them populated the in_zones attribute anymore:

1. Standard method: Using location_name: home and source_type: router.
2. GPS workaround 1: Removing location_name and sending the exact GPS coordinates of the home zone with source_type: gps and gps_accuracy: 10.
3. GPS workaround 2: Forcing both location_name: home AND hardcoded gps coordinates simultaneously.

In all 3 scenarios, the active tracker correctly switches to the virtual tracker, the person's state changes to home, and the latitude/longitude attributes are updated. However, in_zones remains completely empty, and zone.home stays at 0. It seems the zone geometry engine completely ignores tracker updates coming from the device_tracker.see service since 2026.7.0.

What version of Home Assistant Core has the issue?

core-2026.7.0

What was the last working version of Home Assistant Core?

core-2026.6.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

device_tracker / zone / person

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

alias: Anwesenheitserkennung über WLAN
description: Setzt Home bei WLAN-Verbindung im Heimnetz.
triggers:
  - entity_id: sensor.galaxy_s25_ultra_wi_fi_connection
    trigger: state
  - entity_id: sensor.wife_handy_wi_fi_connection
    trigger: state
actions:
  - choose:
      - conditions:
          - condition: state
            entity_id: sensor.galaxy_s25_ultra_wi_fi_connection
            state: WLAN-Network0815
        sequence:
          - data:
              dev_id: galaxy_s25_ultra_wlan_tracker
              location_name: home
              source_type: router
            action: device_tracker.see
      - conditions:
          - condition: not
            conditions:
              - condition: state
                entity_id: sensor.galaxy_s25_ultra_wi_fi_connection
                state: WLAN-Network0815
        sequence:
          - data:
              dev_id: galaxy_s25_ultra_wlan_tracker
              location_name: not_home
              source_type: router
            action: device_tracker.see
  - choose:
      - conditions:
          - condition: state
            entity_id: sensor.wife_handy_wi_fi_connection
            state: WLAN-Network0815
        sequence:
          - data:
              dev_id: wife_handy_wlan_tracker
              location_name: home
              source_type: router
            action: device_tracker.see
      - conditions:
          - condition: not
            conditions:
              - condition: state
                entity_id: sensor.wife_handy_wi_fi_connection
                state: WLAN-Network0815
        sequence:
          - data:
              dev_id: wife_handy_wlan_tracker
              location_name: not_home
              source_type: router
            action: device_tracker.see

Anything in the logs that might be useful for us?

Additional information

No response

[keybuk]

Similar issue with the Eero integration, when I'm at home, the zone shows 0 people and no persons:

latitude: 37.8
longitude: -122.4
radius: 128
passive: false
persons: []
editable: true
icon: mdi:home
friendly_name: Home

The person record shows the correct GPS location, but the source is an Eero device tracker so in_zones is empty:

editable: true
id: scotty
device_trackers:
  - device_tracker.scottys_iphone
  - device_tracker.scottys_iphone_wireless
  - device_tracker.scottys_watch_wireless
in_zones: []
latitude: 37.8
longitude: -122.4
source: device_tracker.scottys_iphone_wireless
user_id: ...
entity_picture: ...
friendly_name: Scotty
asleep: binary_sensor.scotty_asleep

As soon as I remove the Eero device trackers, I'm shown as at home correctly

[Dan1jel]

I also have issue but just with device_tracker via iPhonedetect integration. When i look at people, there are "home" but zone.home shows 0... Went back to previous core.

[raspberrycoulis]

I've got the same issue since updating. A simple automation to trigger a light scene failed, which uses our location to determine if we're home. Has worked fine since set up but suddenly failed after I updated today. Checked the automation and it thinks we're not in the "home" zone. However, checking the zone shows we are.

Hoping this can be fixed otherwise will need to change my automations to use an alternative device tracker as opposed to the person tracker.

Here's my YAML for the automation:

alias: Chill Time
description: Set the living room scene to Chill at 8:30pm every night
triggers:
  - trigger: time
    at: "20:30:00"
conditions:
  - condition: or
    conditions:
      - condition: zone
        entity_id: person.my_name
        zone: zone.home
      - condition: zone
        entity_id: person.wifes_name
        zone: zone.home
actions:
  - action: scene.turn_on
    metadata: {}
    target:
      entity_id: scene.chill
    data: {}
mode: single

[Stecia]

Same problem, zone.home displays the wrong number of persons actually present in the zone
-Chris-

[wiccan2]

I've also got the same problem, using the DDWRT tracker.

[gitnew12]

Also having this issue. Using Companion app, iPhone Detect (mDNS), Bermuda Bluetooth Tracker and Homekit helper for multiple users, all states are Home but zone.home still showing 0.

[Dan1jel]

Also having this issue. Using Companion app, iPhone Detect (mDNS), Bermuda Bluetooth Tracker and Homekit helper for multiple uses, all states are Home but zone.home still showing 0.

Here is probably a solution for now, i need to confirm when i get home but in 99% sure it works :) (if using IphoneDetect integration)

mudape/iphonedetect#162 (comment)

[gitnew12]

Upon further tinkering, in_zones seems to be the important attribute missing from all of this. I have a helper I expose to Homekit to trigger when I am home/away, and I had to adjust my template:

- device_tracker:
  - name: "Github: iPhone (HomeKit)"
    unique_id: github_iphone_homekit
    icon: mdi:cellphone-wireless
    in_zones: >
      {% if is_state('input_boolean.github_iphone_homekit', 'on') %}
        ['zone.home']
      {% else %}
        []
      {% endif %}

And that seems to at least fix this device_tracker. But this still leaves iPhone Detect not using the correct attribute. Thanks to @Dan1jel for providing link to a comment pointing this out. Still didn't try out the fork as I ended up rolling back to HA Core 2026.6.4 for now. Hoping @mudape (developer of iPhone Detect) pushes out an update in the coming days.

[gitnew12]

Pull request out for iPhone Detect here, waiting for maintainer to approve.

[Kunsi]

This is also broken in the aruba integration which is part of core.

[rmoesbergen]

Just to add that this is also broken in the MQTT device_tracker integration. in_zones is always empty.