What RSSI Measures
The value is commonly reported in decibels relative to one milliwatt (dBm). In beacon deployments it is usually negative because the received power is below 1 mW, but the important point is comparison under controlled conditions rather than treating a particular number as universal.
A typical BLE beacon might produce an RSSI of around -30 dBm when the receiving device is centimetres away, dropping to roughly -70 dBm at a few metres and falling below -90 dBm near the limit of reliable detection. These figures are illustrative; the actual numbers in any real space depend on the beacon's transmit power, the receiving device's antenna, and the environment.
There is an important distinction that trips up many people during procurement and pilot planning. RSSI is not a measurement of distance. It is a measurement of signal power at the moment the receiver captures the broadcast. Two devices held at the same spot, at the same moment, reading the same beacon, will often report different RSSI values because their antennas and radio chipsets differ. A phone in a thick case will report a weaker RSSI than the same phone without a case.
Some beacon formats, such as iBeacon, include a field called the "Measured Power" alongside the identifier payload. This is a calibration value representing the expected RSSI at exactly one metre, recorded by the beacon manufacturer under controlled conditions. It exists to give the receiving app a reference point, not to guarantee that your venue will reproduce that number. Your walls, fittings and footfall will change the picture entirely.
| Use | What RSSI can support | Main caution |
|---|---|---|
| Presence | Whether a signal is detected above a tested threshold | Misses and device differences remain possible |
| Coarse zones | Relative near / middle / far decisions | Thresholds need local calibration and hysteresis |
| Trend monitoring | Changes from a fixed gateway or position | Environment and battery changes can shift the baseline |
| Exact distance | Not a dependable standalone measurement | RSSI-to-metres models have large environment-specific error |
Useful Ways to Apply RSSI
In deployed beacon systems, RSSI is used in three broad ways, each with different expectations of reliability.
Zone detection. The most robust use of RSSI is deciding whether a device is inside a defined area or not. Rather than calculating a distance, the system applies a threshold: if the RSSI from a particular beacon rises above a set value for a sustained period, the device is considered present in that zone. This tolerates the natural fluctuation of RSSI because the question is binary — in or out — not metric.
Relative comparison. When a device can hear multiple beacons simultaneously, comparing their RSSI values helps identify which beacon is nearest. This does not require any of the individual RSSI readings to be accurate in an absolute sense; it only requires them to be consistent relative to each other at that moment. Indoor navigation systems use this principle to determine which corridor or room a visitor is closest to.
Gateway-based tracking. Fixed BLE gateways mounted on ceilings or walls continuously scan for beacon broadcasts and log the RSSI of each detected device. Because the gateway's antenna and position never change, the RSSI readings from a single gateway are far more stable over time than readings from a variety of visitor phones. This makes gateways better suited to analytics use cases such as dwell-time measurement and footfall counting, subject to proper privacy controls.
For all three uses, the operational question is the same: what RSSI threshold corresponds to your physical boundary in your specific room, with your specific hardware, on a typical day? That answer only comes from on-site measurement.
Limits, Calibration and Testing
Treating RSSI as a distance reading
The single most common error is assuming that an RSSI value can be converted directly into metres using a simple formula. RSSI-to-distance conversion models exist, but they require calibration in the actual environment and still produce a range estimate with meaningful error margins. Presenting RSSI-based distance to end users as a precise figure will undermine trust the moment a visitor sees the number jump. Use RSSI for zones and relative proximity, not for pinpoint positioning, unless you are layering additional techniques such as trilateration with careful on-site calibration.
Ignoring receiver variation
test with a representative device set that reflects the phones, gateways or scanners expected in service
Confusing transmit power with received RSSI
A beacon's transmit power setting (often labelled TX or Tx Power) is the power level at which the radio broadcasts. RSSI is what the receiver actually measures. They are related but not the same thing. Turning up the transmit power will increase the RSSI measured at a given distance, but it will also increase interference with other beacons and reduce battery life. When reviewing beacon specifications, check whether the quoted figure is the transmit power or the measured RSSI at one metre — they are sometimes conflated in datasheets.
Assuming RSSI is stable over time
In an empty room after hours, RSSI from a fixed beacon to a fixed receiver is reasonably consistent. During opening hours, with people moving, trolleys passing and doors opening, the same setup will produce noticeably different readings. A crowd of people absorbs and reflects 2.4 GHz radio signals. If your pilot takes place in an unoccupied space, treat the resulting RSSI values as a baseline, not a production specification.
Key checks before relying on RSSI in a deployment
- Measure RSSI in the actual venue, at the actual beacon positions, with the actual receiver hardware, during representative operating hours.
- Record the beacon's transmit power setting and firmware version, as both affect output.
- Test with multiple receiver devices and note the variation.
- Check whether your beacon management platform applies any smoothing or filtering to raw RSSI values before passing them to your application — this changes how thresholds behave.
- Ask your integrator or platform provider what happens when RSSI fluctuates rapidly: does the system trigger multiple zone entries and exits, or does it enforce a dwell time before confirming a state change?
- Verify whether the "Measured Power" field in your beacon packets was set by the manufacturer or can be overwritten after your own on-site calibration.
RSSI is a useful signal, but only when treated as a noisy, environment-dependent proxy rather than a precise instrument reading. The next step in understanding how it becomes practically useful is examining how RSSI relates to estimated distance — and where that relationship breaks down.
