What the signal can and cannot indicate
As a Bluetooth beacon broadcasts, the received signal strength indicator (RSSI) drops as the receiving device moves further away. In an ideal open space, this follows a predictable logarithmic curve: signal strength falls off sharply at close range, then more gradually as distance increases. The underlying physics is free-space path loss, and in a textbook scenario you can plot RSSI against distance and fit a reasonably tidy line.
Real indoor environments are not textbook scenarios. Walls, shelving units, display cases, and the human body all absorb and reflect 2.4 GHz radio waves. The result is multipath interference: signals bounce off surfaces and arrive at the receiver from multiple directions, sometimes adding constructively, sometimes cancelling out. A phone held at waist height might read a very different RSSI value from the same phone held at head height, even at an identical distance from the beacon.
The practical upshot is that RSSI and distance have a general relationship—closer devices tend to report higher (less negative) values—but you cannot convert a single RSSI reading into a reliable distance figure without first measuring that specific environment. Any formula that claims to turn raw RSSI into metres without on-site calibration is omitting the most important variable: the physical space itself.
Most deployment guides and beacon protocols, such as Apple's iBeacon specification, sidestep the distance problem entirely by defining proximity zones rather than precise distances. An iBeacon frame, for example, transmits a measured power value at one metre, and the receiving device compares the observed RSSI against that reference to classify the beacon as immediate, near, or far. These are rough categories, not measurements.
Control the variables you can control
Zone triggers rather than distance calculations
The most robust way to use RSSI in a retail shop, museum, or event venue is to define a signal-strength threshold that corresponds to a zone boundary, then trigger an action when a device crosses it. A museum might place a beacon near an exhibit and set a threshold so that when a visitor's phone reports an RSSI stronger than roughly -70 dBm (illustrative figure; actual values depend on the beacon model, transmit power, and surroundings), the audio guide for that exhibit loads. The team does not need to know whether the visitor is 1.2 metres or 1.8 metres away—only that they are close enough for the content to be relevant.
Calibrating for your space
When a project does require a rough distance estimate—perhaps for indoor navigation or queue-length detection—the standard approach is to perform a simple on-site calibration:
- Mount the beacon in its intended position, with its final transmit-power setting and advertising interval.
- Take RSSI readings at several known distances (for example, 0.5 m, 1 m, 2 m, 4 m, 8 m) using the actual phone models your visitors or staff will carry.
- Record multiple samples at each point and average them to smooth out momentary fluctuations.
- Plot the results and fit a path-loss model or simple lookup table for that specific beacon-and-location combination.
This calibration must be repeated whenever the physical layout changes significantly. Moving a display case, adding seasonal stock, or even rearranging seating can shift the RSSI-to-distance curve enough to break an uncalibrated system.
Trilateration and its practical limits
Indoor navigation systems sometimes use RSSI values from three or more beacons to estimate a device's position through trilateration. In principle, each beacon's RSSI gives a circle of possible locations; where the circles overlap is the estimated position. In practice, the RSSI noise and multipath effects mean the circles are fuzzy and the estimated position can jump by several metres from one reading to the next. Smoothing algorithms (such as Kalman filters) help, but the fundamental input—RSSI—remains imprecise. Trilateration using RSSI alone is best suited to coarse "which zone am I in" navigation rather than turn-by-turn directions.
Acceptance bands and operational monitoring
Assuming a universal formula
The single most common error is applying a generic path-loss equation to an unmeasured environment and treating the output as a real distance. Different building materials, ceiling heights, and even humidity levels shift the curve. If a supplier or integrator presents a distance-estimation system without discussing on-site calibration, ask specifically how the RSSI-to-distance mapping was derived for your venue.
Ignoring antenna orientation and body shielding
Beacon antennas are not perfectly omnidirectional. A beacon mounted flat against a ceiling tile will radiate more strongly downwards than sideways. Similarly, a person carrying a phone in a trouser pocket presents a different obstruction to the signal than someone holding the phone in front of their face. During calibration, test the orientations and carrying positions that your users will actually use, not just the most convenient one for the engineer.
Over-relying on a single reading
Because RSSI fluctuates—sometimes by several dBm from one packet to the next—any decision based on a single reading will be noisy. Practical systems average over a short window (for example, five to ten consecutive packets) before acting on the value. When defining zone thresholds, build in hysteresis: set the entry threshold slightly stronger than the exit threshold so the system does not flicker back and forth at the boundary.
Key checks before going live
- Has RSSI been measured at known distances in the actual deployment location, not a test room?
- Have multiple phone models been tested, or is the system calibrated for only one device?
- Are beacon transmit power and advertising interval locked to the values used during calibration?
- Does the system average multiple RSSI samples before triggering an action?
- Is there a plan to recalibrate when the physical layout changes?
- Are zone thresholds documented so that future maintainers understand why a particular dBm value was chosen?
RSSI is a useful signal for proximity detection. It becomes unreliable the moment it is treated as a precise measuring tool. Understanding the rough, environment-dependent nature of the RSSI-to-distance relationship—and designing your system around zones, thresholds, and on-site calibration rather than raw distance formulas—is the practical starting point for any beacon deployment that actually works in a real building.
