什么是正确的BeaconLayout的Estimote和万向标

问题描述

我想2.0版本Android的灯塔图书馆，以便能够正确地检测到这两种老式Estimote标（pre-2013模式，不支持iBeacon技术）和万向信标。我知道万向信标有加密标识符，所以这些不能被直接读出。但我至少会和大家分享code，可以检测，一个是各地。

I would like the 2.0 release of the Android Beacon Library to be able to properly detect both old style Estimote beacons (pre-2013 models that did not support iBeacon technology) and Gimbal beacons. I know that Gimbal beacons have encrypted identifiers, so these cannot be read directly. But I would at least like to share code that can detect that one is around.

下面是我：

code检测万向灯塔（不读加密的标识符）：

Code to detect a Gimbal beacon (without reading encrypted identifiers):

BeaconManager beaconManager = BeaconManager.getInstanceForApplication(this);
BeaconManager.getBeaconParsers().add(new BeaconParser().
       setBeaconLayout("m:0-3=ad7700c6"));
beaconManager.bind(this);

code检测2013年年中Estimote信标（不读的标识符，因为我不知道如何）：

Code to detect a mid-2013 Estimote beacon (without reading identifiers because I do not know how):

BeaconManager beaconManager = BeaconManager.getInstanceForApplication(this);
BeaconManager.getBeaconParsers().add(new BeaconParser().
       setBeaconLayout(""m:0-3=2d24bf16""));
beaconManager.bind(this);

是否有人（特别是Estimote或万向人）对上述的字节偏移的任何其他信息将允许解码从传输尽可能多的信息？在每一种情况下，我相信我们需要键入关闭蓝牙服务UUID，这可能是正确地重新与多个字节psented比我在上面的例子中$ P $的。我很想知道在广告发送的全程服务的UUID以及任何其他可读的领域。

Does anybody (especially folks from Estimote or Gimbal) have any additional information on the byte offsets above that will allow decoding as much information from the transmissions as possible? In each case, I believe we need to key off of the bluetooth service UUID, which is probably properly represented with more bytes than I have in the examples above. I would love to know the full service UUIDs as well as any other readable fields sent in the advertisements.

推荐答案

有关estimote

For estimote

beaconManager.getBeaconParsers().add(new BeaconParser().setBeaconLayout("m:2-3=0215,i:4-19,i:20-21,i:22-23,p:24-24"));

这篇关于什么是正确的BeaconLayout的Estimote和万向标的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！