Fix passive zone lookup in zone-only location privacy mode

[arrizer]

Bug

When the Location Sent setting is set to Zone Only, automations that trigger on entering a passive zone stop working while the same automations work correctly with Exact location.

Root cause

In zone-only mode, SubmitLocation derives the current zone by GPS lookup via RLMZone.zone(of:in:) rather than using the zone associated with the incoming region event (the event zone may be the one being exited, so a fresh lookup is needed). That lookup filtered using trackablePredicate:

.init(format: "TrackingEnabled == true && isPassive == false")

The isPassive == false condition meant that when the device was inside a passive zone, the lookup returned nil, causing the payload to report not_home to Home Assistant instead of the passive zone so no automation triggered.

In Exact mode this doesn't occur because raw GPS coordinates are sent and Home Assistant resolves the zone server-side, where passive zones are handled correctly.

Note that passive zones are monitored for region enter/exit events by the iOS app (ZoneManager filters only on TrackingEnabled, not isPassive), so the region event does fire, the zone is simply lost during the zone-only lookup step.

Fix

Remove isPassive == false from the filter in RLMZone.zone(of:in:), replacing trackablePredicate with a TrackingEnabled == true-only filter. This method performs a GPS-to-zone lookup and has no reason to exclude passive zones.

trackablePredicate is left unchanged and continues to be used correctly in GeocoderSensor.

[home-assistant]

Hi @arrizer

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[Copilot]

Pull request overview

Fixes zone-only location privacy mode so passive zones are correctly resolved client-side during GPS-to-zone lookup, preventing not_home payloads when inside a passive zone.

Changes:

• Updates RLMZone.zone(of:in:) to filter only on TrackingEnabled == true, allowing passive zones to be returned.
• Leaves trackablePredicate unchanged for existing usages (e.g., GeocoderSensor) where passive zones should remain excluded.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

CLA signed already

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@a21ebf0). Learn more about missing BASE report.

Additional details and impacted files

@@          Coverage Diff           @@
##             main   #4385   +/-   ##
======================================
  Coverage        ?       0           
======================================
  Files           ?       0           
  Lines           ?       0           
  Branches        ?       0           
======================================
  Hits            ?       0           
  Misses          ?       0           
  Partials        ?       0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.