It doesn’t, Ilgaz. This is also where I went wrong on my first project. Hermetry does not calculate zones from position or from BLE beacons, and there is no geofence polygon. The tag, or the gateway that hears it, decides the room itself and sends the zone name. The ready-made staff tracking solution is built exactly this way: the zone key is either a zone name or outside.For your scale, my suggestion is BLE. UWB is for sub-metre accuracy; at room level it doesn’t pay off. The setup works like this:

1. One fixed BLE receiver per room (an ESP32 is enough, plugged into a socket). All of them send the RSSI of the tags to a local server or a Pi.
2. For each tag, the Pi picks the room that heard it strongest in the last 10-15 seconds, and adds hysteresis (don’t switch to a new room unless it is at least 6 dB stronger), otherwise the chair at the door will jump between two rooms.
3. The Pi connects as a gateway and reports each tag as a child device:

v1/gw/telemetry
{
  "pompa-07":   {"values": {"zone": "A-3-314", "zone_id": 3314, "battery": 81}},
  "sandalye-12": {"values": {"zone": "A-2-208", "zone_id": 2208, "battery": 64}}
}

I added zone_id on purpose: zone is text, and text keys don’t keep a chart history, only the last value is shown. For the question “where was the pump yesterday” you need a numeric code.On the Sites & Assets side, create the rooms with kind Room or with your own ZONE type, and keep their codes the same as the names the gateway sends. For the tree dashboard and lists, the matching is again done by the gateway.The ready-made solution’s page describes the model very well, you can adapt from there: Personel takibi.