Is enabling motion on beacon same as enabling motion on nearables (stickers)? Android SDK

BLE Beacons
1

Hi I came across with this codes on github and was wondering if there’s any difference for the coding between enabling motion on beacon and enabling motion on sticker. If there’s any difference, can you all help me out in pointing out the difference.

Code for enabling motion on beacon:

 // First step after connection is to enable motion detection on beacon. Otherwise no motion notifications fill be sent.
connection.edit().set(connection.motionDetectionEnabled(), true).commit(new BeaconConnection.WriteCallback() {
    @Override public void onSuccess() {
 
    // After on beacon connect all values are read so we can read them immediately and update UI.
    setMotionText(connection.motionDetectionEnabled().get() ? connection.motionState().get() : null);

    // Motion sensor sends status updates on physical state change.
    enableMotionListner();
}
2

Estimote Beacons broadcast the iBeacon packet by default, and iBeacon packet as designed by Apple is just the UUID, major, and minor, nothing about sensors. So in order to access the motion sensor data, you need to connect to the beacon, and keep the connection open for as long as you want to be able to access the data.

Stickers on the other hand broadcast our own packet (we call it the “Nearable” protocol), which includes sensor data directly in the packet. This means there’s no need to connect, you can just walk past a sticker and catch the sensor data. Additionally, it’s not just motion detection (i.e., is it moving or not), there’s also full x+y+z accelerometer data in it. So you can also know how much is the sticker accelerating and in which relative direction.