how can I take major and minor after the beacon motion detection?
This is my code:
public void onTelemetriesFound(List<EstimoteTelemetry> telemetries)
for (EstimoteTelemetry tlm : telemetries)
showNotification("BEACON MOTION", "Rilevato movimento! ");
// here, i want take major e minor of the beacon in motion
You have listener set on telemetry packets. They don’t have major and minor fields like iBeacon, but use unique 16-byte identifier of a Beacon. You can use that ID to identify your beacon instead of UUID/major/minor.
Other option is to enable motion-only advertising. Beacon will only advertise when in motion, so you can listen for iBeacon packets and start your code as soon as listener gets it. Disadvantage of this solution is that you cannot tell if your are near beacon if it is not in motion.
That’s actually a bit of a complex question, since the major and minor are part of the iBeacon packet, and in your code, you’re scanning for Telemetry — a separate packet.
So we’ll need to answer a few questions:
First off, is the beacon also broadcasting iBeacon? If not, you’d need to enable that packet, too.
But like @pober mentioned, you can actually use the identifier to uniquely identify your beacons. And in this scenario, you could use the telemetry packet by itself.
Before this use, monitoring on two different regions.
Is there a way to be able to use iBeacon monitoring data for telemetry?
public void onServiceReady()
//Connect monitoring Beacon SeismoCloud
//Connect monitoring Beacon Vibration
Is there a common value between iBeacon and Telemetria?
This topic was already covered here: Indentification between iBeacon & telemetry
TLDR: There isn’t a common value between iBeacon and Telemetry. Those are independent packets, configured and advertised separately. In order to match them together you need to query cloud for your devices configuration and match UUID/major/minor (broadcasted in iBeacon) with unique device ID (broadcasted in telemetry packet). There is not enough space in either iBeacon and Estimote Telemetry packets to squeeze a common id. We advice to use Proximity SDK that is based on Estimote Location packet that is using same device ID as telemetry packets (this way you don’t need to use Cloud).