From broadcast packet to receiver reading
Received Signal Strength Indicator (RSSI) is the value your receiving device reports when it picks up a beacon's broadcast. It is expressed in negative decibels relative to a milliwatt (dBm) and, crucially, it is a relative observation rather than a calibrated distance reading. A manufacturer's stated range is measured under controlled conditions: open space, no obstructions, fixed antenna orientation and a single reference receiver. Your venue will not match those conditions.
Measuring RSSI in a real environment means going to the actual space where the beacons will operate and collecting signal readings at the positions and times that matter to your use case. The purpose is not to discover a universal formula but to build a site-specific picture of how the signal behaves in that particular room, corridor or shop floor. That picture then informs placement, zone boundaries and the thresholds your software will use to trigger actions.
The relationship between RSSI and distance follows a logarithmic decay curve in free space, but in a real interior that curve is distorted by reflections, absorption and multipath interference. Two points at the same physical distance from a beacon can report different RSSI values simply because one is in a direct line of sight and the other is behind a display case. This is why on-site measurement cannot be skipped or replaced by a spreadsheet model.
Why a Single Reading Is Insufficient
One measurement at one point tells you almost nothing useful. RSSI fluctuates even when the receiver and beacon are stationary, because of minor changes in the radio environment — someone walking past, a door closing, or the receiver's internal radio adjusting its gain. A practical measurement session collects multiple samples at each test point and records the spread, not just the average. That spread tells you whether a zone boundary will be reliable or whether it will flicker.
A repeatable venue test
Preparing for a Measurement Walk
Before you start, define what you are trying to achieve. In a retail setting, you might need to know at which RSSI threshold a phone near the entrance reliably detects the welcome beacon without triggering for someone walking past outside. In a museum, you may need to confirm that a beacon placed beside an exhibit reaches the viewing position but does not bleed into the neighbouring exhibit's zone. The use case determines where you place your test points and what thresholds you are investigating.
You will need a beacon configured to the transmit power and advertising interval you intend to use in production, a receiving device (typically a smartphone running a logging app or a dedicated BLE scanner), and a method of recording your position. A floor plan marked with test points works well. Some teams use a simple grid, others place points at the specific locations where visitors are expected to stand or walk.
Conducting the Measurement
At each test point, hold the receiving device in the orientation a visitor would typically use — phone in hand, screen facing the user, at roughly chest height. Record a set of consecutive RSSI samples. How many depends on your required confidence, but tens of readings per point are common in pilot work. Note the exact position, the device orientation, and any immediate environmental factors: a trolley parked nearby, a door open or closed, stock on shelves.
Move to the next point and repeat. Pay particular attention to the boundaries you care about: the edge of a zone, the transition between one beacon's coverage and another's, and positions where line of sight is partially blocked. These boundary points are where RSSI is most variable and where your zone logic will be tested.
Timing and Environmental Conditions
Radio conditions in a busy venue change throughout the day. A measurement taken in an empty shop on a Sunday morning will not represent Saturday afternoon. Where operationally feasible, take readings during conditions that match your peak usage. At minimum, note the difference between empty and occupied states so you can factor that variance into your threshold decisions.
Limits, confidence and fallback rules
Mistakes That Undermine Measurement
- Measuring with a different transmit power or interval than production. Changing either parameter alters the RSSI at every distance. If your production beacons will broadcast at a lower power to conserve battery, your high-power measurements will be misleading.
- Using only one receiver. Different devices report different RSSI values at the same position. Measuring with a single phone and assuming all visitor devices will behave similarly introduces a systematic blind spot. (How and why devices differ is covered in the adjacent article on RSSI variability across devices.)
- Ignoring device orientation. A phone's BLE antenna is not omnidirectional. Rotating the device can change the reported RSSI by several dBm. If your visitors will hold phones in varied orientations, your measurement set should reflect that.
- Recording only the mean. The average RSSI at a point might look stable while the actual readings swing widely. Without the spread (standard deviation, min and max), you cannot judge whether a threshold will trigger reliably or erratically.
- Measuring once and treating it as permanent. Furniture moves, stock changes, seasonal displays go up. A measurement is a snapshot. Plan to re-measure when the physical layout changes meaningfully.
Limitations to Accept Upfront
RSSI measurement in a real environment will not give you centimetre-accurate positioning. It gives you a probabilistic sense of which zone a device is likely in, with a known margin of uncertainty. If your use case requires precise location — for example, picking one specific product on a dense shelf — RSSI alone is unlikely to suffice regardless of how carefully you measure.
Measurements are also specific to the hardware combination you test. Swapping the beacon model or the receiver device changes the numbers. Treat your measurements as tied to that specific hardware set and re-measure if you change any component.
Key Checks Before Relying on Your Data
- Confirm the beacon's firmware-reported transmit power matches what you configured, rather than assuming the setting took effect.
- Verify that the advertising interval on the beacon during measurement matches your production plan.
- Check that your logging app reports raw RSSI rather than a smoothed or filtered value, unless you intend to test a specific filtering approach.
- Compare a subset of your readings against a second receiver to understand the scale of device-to-device difference in your environment.
- Revisit at least one test point after changing a single variable — such as opening a door or moving a large object — to confirm that your measurement method is sensitive enough to detect the environmental change you care about.
Once you have a reliable set of site-specific RSSI measurements, you are in a position to set zone thresholds that reflect how the signal actually behaves in your space rather than how it behaves in a manufacturer's test chamber. Those thresholds then feed into your filtering and smoothing logic, which is where the next article in this sequence picks up.
