iBeacon Zone Updates Trigger Incorrectly

[jamesgoodhouse]

iOS device model, version and app version

Model Name: iPhone 12 Pro
Software Version: 18.2.1
App version: 2024.1

Home Assistant Core Version
core-2025.1.4

Describe the bug
I have iBeacons at my house and have Home Assistant configured to trigger enter/exit zone updates as described in the documentation. The updates work flawlessly when I'm at home, however, once I leave my house, I frequently experience unexpected zone updates even though there are no iBeacons in the vicinity. The location update logs also show many erroneous iBeacon Region Entered events.

To troubleshoot, I updated the UUID for my iBeacons and modified both the major and minor values, but this did not fix things.

To Reproduce

1. Configure one or more iBeacons at home with a UUID and major and minor version
2. Add the following entry to your configuration.yaml:

homeassistant:
  customize:
    zone.home:
      track_ios: true
      beacon:
        uuid: 468f6d93-44c6-4af1-803d-5bbc3f46687f
        major: 123
        minor: 456

3. Verify location updates work locally by unplugging and plugging in your iBeacon
4. Leave home and eventually you will see iBeacon location updates for zone entry in your logs even though no beacons are around.

Expected behavior
Location updates only trigger for my specific UUID and major/minor versions for my iBeacons while at home.

Screenshots
N/A

Additional context
I'm not 100% certain, but if I uninstall the app and reinstall, or deleter the server and then re-add, the issue seems to go away for a period of time. Sometimes for a few days, but once it starts happening, it will toggle home/away constantly while I am away.

[adipierro]

Also see the same issue

[jamesgoodhouse]

Also see the same issue

@adipierro: Do you have more than one zone configured out of curiosity? I have a single other zone configured (non-passive). I don't know it matters, but just curious on if we can narrow down any parameters for when this happens for people or not.

There's another report of this occurring for a user on the community forum.