Zone detection

Know exactly which room or area a tag is in, without precise coordinates. Zone detection gives you room-level presence tracking by assigning network zones to hotspots, perfect for indoor environments where GPS isn't available and you care more about "which room" than exact coordinates.

How it works

You assign a network zone to a hotspot or place a reference beacon with a network zone assignment in the area. When a tag is detected, the system reports which network zone the tag is in based on the strongest hotspot signal.

Network zone information is included in position events alongside coordinates (when available). You get both; it's not either/or.

Setting up network zones

There are two ways to assign network zones to hotspots:

Option 1: Direct hotspot assignment

In the Console, open a hotspot's detail page.
Set the network zone.
All tags detected by that hotspot will be reported in that network zone.

Option 2: reference beacons

Register a tag and mark it as a reference beacon.
Assign a network zone to the tag.
Place the tag near the hotspot.
The hotspot automatically inherits the tag's network zone assignment.

Reference beacons are more flexible; you can reassign network zones by moving tags without reconfiguring hotspots. See reference beacons for details.

Network zones vs coordinate zones

Zone detection creates network zones: proximity-based zones determined by which hotspot detects the tag. These are different from coordinate zones, which are geographic boundaries drawn on the map in Blecon Track.

Both zone types appear in the zones list and work with alert rules. Network zones are created in the Console and assigned to hotspots or reference beacons; coordinate zones are drawn on the map in Blecon Track.

Network zone timeout

When a tag leaves a network zone, there's a configurable delay before the exit is reported (default: 70 seconds). This prevents false transitions from signal fluctuations.