MonitoringListener should return list of beacons that triggered enter/exit event

[nutfox]

When running a MonitorListener or RangingListener we discovered the following problem:
When starting it for a region with specified major and minor values, these values are returned. When starting it for the ALL_ESTIMOTE_BEACONS region (with Major and Minor set to null) the region that is passed to the callback methods contains null in Major and Minor.

This might as well be a feature request: How can I monitor/range for all major/minors for a given uuid - yet when the region is entered, I get the exact major and minor values of the region that triggered the event?

[wiktor]

Region object that is passed in the callback is the same that was given in startMonitoring/startRanging methods. This is working as intended since you want to be able to distinguish monitored/ranged regions.

In ranging you have this information. Take a look at RangingListener#onBeaconsDiscovered. Second param is list of beacons that are being seen in this region.

When it comes to monitoring and getting info which beacons triggered enter/exit events, it is on the way in the next release.

[nutfox]

Ok. We have the following requirement:
A number of locations - each with 1 or more beacons (>100) - when a user enters one of the locations our app must be notified about which location it is. Can this be done by defining the same region for all beacons and then using the beacon identification to assess which location the user is in?

[wiktor]

Yes, you can use single region for all your beacons that is 'new Region("regionId", null, null, null)' and differentiate them in your app.

You can also set your beacons' identifiers in order to match location. That is major/minor values could indicate a location. And you can monitor only those regions.