iBeacon problems - confirmed

Couple issues with iBeacon support:

I’ve confirmed it doesn’t work like OwnTracks when dealing with multiple beacons. That is if you set the HA config for a major/minor both of 0 it doesn’t mean “match all devices with the same UUID”. So in a large house with several beacons required you have challenges.

By setting the same UUID/major/minor what happens is when you move from one beacon to another due to range/proximity you will get a zone exit/enter event (in this case two exits are notified due to the bug in the app pending next release with a fix). This causes the need to “debounce” the device tracker to ensure not instant automation triggers due to this.

So what would be nice is to either set it up to work like OT; and ignore the major/minors to match on only UUID or to allow multiple iBeacons to be set per zone.

The good news is I’m really close to presence utopia :wink: iBeacons and using the iTunes wake for a ping test has gotten me to 99% and multiple beacons should get me to 5 9’s which is good enough for the wife to accept my hobby :wink:

Does anybody know if the iOS app’s behavior around major/minor is still the same? I am in the same situation as you and would like to avoid any manual “debouncing”…

Yes, same situation – no update to the app yet.