Zone condition in automations fail for person entity with non-gps device tracker: no latitude

[Soukyuu]

The problem

I have set up my person entity with two device trackers:

• my mobile phone with the home assistant companion app (type = gps)
• my mobile phone sourced via the Fritz!Box tools integration (type = stationary)

I have also set up an automation which fires a notification, but only if I am home. This step fails with the following error message:

In 'zone' condition: error matching person.ivan with zone.home: entity person.ivan has no 'latitude' attribute

The docs do mention that for the matching to work it needs a tracker which has gps. I'd have expected my person entity to satisfy the condition, as it has both.

Or at least reject setting the person entity as the entity to match for if it's ambiguous...

What version of Home Assistant Core has the issue?

core-2023.3.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Automation

Link to integration documentation on our website

https://www.home-assistant.io/docs/scripts/conditions/#zone-condition

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[serl]

Hello! I'm new here, just in case 😁

I had the same error while interacting directly with a device tracker.

I resorted to use "state" instead of "zone". To say it in yaml, I had:

  - condition: zone
    entity_id: device_tracker.xxx
    zone: zone.home

And now I have:

  - condition: state
    entity_id: device_tracker.xxx
    state: home

I think it should work with person as well.

For the devs: I think that in my case "zone" worked yesterday and it stopped after the latest update. In my case it's the tracker in macos.

[powturns]

Looks to be a duplicate of or related to 51788 / 69683 / 81850

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Soukyuu]

Well, not quite solved. I can't seem to be able to select a person entity for a zone trigger anymore, so the issue won't occur in the same manner, but now I lost the possibility to use a GPS based tracker outside my home and a more accurate network tracker for detecting I'm home - without using a template that is.

[G0ldenSp00n]

A good work around for now is just using a state check on the person entity and checking if they are home. But this really does seem like a bug that should be fixed.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Soukyuu]

Sadly not fixed. Still using the workaround of checking the state

[surrealix]

Weighing in here to say I have a similar issue. My devices have the reporting set to zone-only, and now they don't appear in the entities drop-down. I'm also using the state workaround.

[tfranzel]

Just a quick update so that the bot isn't closing this. This bug still applies to 2024.3.0

This seems to me like a pretty fundamental functionality that almost anybody using HA would be interested in.

Forcing the companion app to report gps coords (instead of "zones only") as a workaround is not a very privacy centric approach. The device_tracker "workaround" is not really that hot anymore after 3 years of this being known. If the zone feature is supposed to be "gps-only", at the very least it should be documented as such.

I don't quite understand why this super basic issue is raised again and again and basically ignored while a lot more esoteric features are being pumped out. Makes me wonder.

Is there an existing approach or path to address this? Is it even possible without breaking other things? I would be willing to give it a try.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Soukyuu]

Bug is still present.