Page History

...

The tags can be configured (using the MikroTik Beacon Manager app) to broadcast the payloads automatically, every "x" configured seconds or/and when a movement, tilt, or free-fall trigger is detected. That means the tag is able to "tell" all the surrounding "listenersscanners" (like the KNOT) information about itself. When the payload is broadcasted by the tag, and the tag is within the KNOT's operating range, the KNOT will see the payload under its Bluetooth interface. An example, would beIt would look like this:

/iot bluetooth scanners advertisements print
 # DEVICE    Columns: DEVICE, PDU-TYPE, TIME, ADDRESS-TYPE, ADDRESS, RSSI, LENGTH, DATA
#  DEVICE  PDU-TYPE        TIME                  ADDRESS-TYPE  ADDRESS                RSSI    LENGTH LENGTH DATA                                           
0 0 bt1         adv-noconn-ind  mar/07/2023 12:06:14 random11:47  public        20DC:8E2C:496E:E90F:43C0:F53D  -39dBm    -60dBm  22  15ff4f090100a2eafefffcff0400cf18806b2b000064
1  bt1 15 02011a0bff4c00090603d10a3708a2   adv-noconn-ind  mar/07/2023 12:11:57  public         
 1 bt1DC:2C:6E:0F:C0:3D  -51dBm      22  15ff4f09010079100000ffff0000cf188a6b2b000064
2  adv-indbt1     adv-noconn-ind   mar/07/2023 12:06:14 random11:58  public        602C:08C8:461B:F14B:F9:A5    BB:0A  -60dBm49dBm      22 15 02011a0bff4c0010060319b8236408         15ff4f090100168dfefffffffeffa51ae1362200005e
 

The payload itself

As a result, when you have 2 KNOTs (KNOT-A and KNOT-B), running the same script on a scheduler, and the tag moves between their Bluetooth operating ranges, you will have the data on the server indicating whether it was KNOT-A or KNOT-B that have sent the tag's payload. That will help you figure out the proximity of the tag. Whether the tag is broadcasting payloads in the KNOT-A zone, or in the KNOT-B zone.

...