...

Just attach the tag to the asset and, after a few additional steps explained below in this guide, you will be able to track its approximate location.

...

Scenario explanation

We can script and automate the KNOT so that as soon as the tag appears within the KNOT's Bluetooth range, RouterOS would structure a message (which would have the tag's MAC address in it), and would send it to the server.

As a result, if 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 and that way you can figure out an approximate position of the tag.. Of course, by that logic, if the Bluetooth operating ranges overlap and the tag is within the overlapped area (at the same time within KNOT-A and KNOT-B Bluetooth ranges), both KNOTs will send the data and the server will show

Let's say, you have a warehouse. What you can do, is you can scatter the KNOTs across the warehouse so that the KNOT's Bluetooth ranges do not overlap with the neighboring KNOTs. You need to test the Bluetooth range in your environment/topology to figure out how far the Bluetooth range goes, as it can be much lower than expected if you have a lot of 2.4 GHz interference or materials that can impact the signal strength, like concrete. For example, in line of sight, with no interference, the distance at which the KNOT is able to capture the tag's broadcasted payload, can be up to 180 meters (KNOT — ~180 meters — TG-BT5-OUT). But you also have to keep in mind that with more distance, more packets will be lost on the way.

...