How-to get Motion UUID of a beacon?

The API service is not returning the Motion UUID for beacons with Motion Detection turned on. How can it be obtained from the API?

Sylvain Audet

It’s not in the API, but it’s actually quite easy to figure it out!

Motion UUID = regular UUID, but with the first bit negated.

For example, if your regular UUID is “B9407F30-F5F8-466E-AFF9-25556B57FE6D”, then the first byte (“B9”) in binary notation = 10111001. Let’s flip the first bit, so now that byte is 00111001, which is “39” in hex notation. So the Motion UUID for that UUID will be “39407F30-F5F8-466E-AFF9-25556B57FE6D”.

How do you plan to use Motion UUID?

Thank you Piotr. Would be nice to have it part a future API release but at least you gave us a workaround to figure it out.

We have implemented support for beacon’s motion UUID into our app in order to have the choice whether to use a nearable device OR a beacon to detect movement.

1 Like

Yup, agreed having it in the API would be better, we’ll look into that (:

You got me curious about the motion detection in your app! Any chance you could share what does the app do, how do you use the motion information?

With great pleasure Piotr! :slight_smile:

Our app detects if the received beacon UUID is a motion one, meaning the beacon is moving (item picked up by user, door open, etc.). If so, we perform a pre-defined action (customizable from within our backend) that is associated to this beacon (based on motion UUID/major/minor). The pre-defined actions allows us to interact directly with the user in real-time.