Bluetooth Low Energy beacons operate in the 2.4 GHz industrial, scientific and medical (ISM) band, a frequency range they share with Wi-Fi, microwaves, Zigbee devices and a growing number of consumer electronics. In a controlled test chamber a beacon's signal behaves predictably, but in a real retail floor, museum gallery or exhibition hall the same signal meets walls, metal fixtures, overlapping radio networks and hundreds of moving bodies. Understanding what interferes with a beacon signal, and what to do about it, is the difference between a reliable deployment and one that produces erratic distance readings and missed triggers.
Variables that move the result
Every wall between a beacon and the receiving device attenuates the radio signal. The amount of loss depends on the material, its thickness and any internal structure such as metal mesh or moisture content. A standard internal plasterboard partition on a timber stud will reduce signal strength noticeably but rarely prevents detection altogether. A dense concrete block wall, particularly one that is load-bearing, can cut the received signal strength by a considerable margin, and a wall containing steel reinforcement or metal lath will cause a sharper drop still.
The practical consequence is not simply that the signal gets weaker. Because RSSI-based distance estimates assume a clean line-of-sight path, each wall introduces an additional, unaccounted-for loss that makes the beacon appear further away than it truly is. A beacon two metres from a phone but separated by a partition wall may report an RSSI value consistent with six or seven metres in open air. If your zone logic relies on a single distance threshold, that wall will silently shift where the boundary actually falls.
When surveying a site, note the material and approximate thickness of every wall within the area where beacons will operate. Mark walls that contain metal studs, foil-backed insulation or services trunking separately, because their effect is not simply a matter of degree — they can also create partial reflections that make the signal fluctuate as people move nearby.
What to check on site
- Identify wall types on your floor plan before placing any hardware.
- Expect calibration values gathered in one room to be unreliable in the next if the wall construction differs.
- If a zone boundary runs along a wall, test on both sides rather than assuming symmetry.
Metal Surfaces and Signal Reflection
Metal does not absorb Bluetooth signals in the way that dense masonry does. Instead, it reflects them. A beacon mounted directly on a metal shelf, a steel door frame or an aluminium ceiling grid will transmit part of its energy into free space and bounce the rest back towards itself and in other directions. The result is a pattern of constructive and destructive interference known as multipath, where the receiving device sees not one clean signal but several copies arriving at slightly different times and phases.
Multipath causes RSSI values to jump even when neither the beacon nor the phone is moving. A reading might fluctuate by several decibels from one second to the next, which in turn causes the estimated distance to swing unpredictably. For proximity triggers that depend on entering or leaving a zone, that fluctuation can produce repeated, rapid notifications — a visitor stands still near a metal exhibit case and the system toggles between "in zone" and "out of zone" several times a minute.
The standard mitigation is to keep a gap between the beacon and any metal surface. Most manufacturers recommend a minimum clearance, often in the region of a few centimetres, though the exact figure depends on the beacon's antenna design. Plastic mounting brackets, adhesive-backed foam pads or simply repositioning the beacon onto a non-metallic surface can all help. In environments where metal is unavoidable — industrial racking, cold-room cladding, shipping containers — the only realistic approach is to calibrate in situ and accept a wider margin of error in your zone logic.
Wi-Fi Coexistence and Channel Overlap
Wi-Fi and Bluetooth Low Energy both use the 2.4 GHz ISM band, but they divide it differently. Wi-Fi occupies wide 20 MHz or 40 MHz channels, while BLE transmits on narrow 2 MHz channels spaced across the same spectrum. BLE advertises primarily on three channels — 37, 38 and 39 — which sit at 2.402 GHz, 2.426 GHz and 2.450 GHz respectively.
Wi-Fi channels 1, 6 and 11 are the most common choices in UK deployments because they do not overlap with each other. However, Wi-Fi channel 1 extends from 2.401 GHz to 2.423 GHz, which covers BLE advertising channel 37. Wi-Fi channel 6 sits in the middle of the band and overlaps with BLE channel 38. Wi-Fi channel 11 reaches up to 2.462 GHz, overlapping with BLE channel 39. In practice, this means that in any building running 2.4 GHz Wi-Fi, at least one — and often all three — BLE advertising channels share spectrum with a Wi-Fi transmission.
BLE is designed to coexist with Wi-Fi through adaptive frequency hopping and brief transmit bursts, so moderate Wi-Fi traffic does not usually prevent beacons from being detected. Problems tend to arise in environments with dense, high-throughput 2.4 GHz Wi-Fi — large lecture theatres, conference venues with many access points or warehouses using older Wi-Fi handsets. In those settings, packet loss on one or more advertising channels can increase, which means the receiving device sees fewer beacon broadcasts per second and takes longer to register a zone entry.
If your venue has recently upgraded to Wi-Fi 6 or Wi-Fi 6E and shifted most client traffic to 5 GHz or 6 GHz bands, 2.4 GHz interference may have reduced without any changes to the beacon deployment. Conversely, adding more 2.4 GHz access points to improve coverage can make beacon detection less reliable. Check which channels your access points are using and whether 2.4 GHz is still carrying significant client traffic before assuming Wi-Fi is not a factor.
Other Bluetooth Devices and Interference
Any device actively transmitting on a nearby BLE channel can occupy the airtime that a beacon needs. In a retail environment the most common culprits are consumer devices: staff headsets, portable speakers, smartwatches, tracking tags on stock and visitors' own phones broadcasting BLE for various services. Each additional active transmitter in the same physical space increases the probability that a beacon's advertising packet will collide with another transmission and be lost.
Classic Bluetooth audio devices — headphones, hands-free kits — use wider channels and different modulation, but they still consume time on the 2.4 GHz band. A busy shop floor with several staff members wearing Bluetooth headsets may see a measurable increase in packet loss, particularly if the beacons are set to a low transmit power.
Interference from other BLE devices is harder to diagnose than Wi-Fi overlap because there is no central management interface to inspect. If you suspect congestion from other Bluetooth traffic, the practical approach is to increase the beacon's advertising interval slightly — sending packets more frequently gives the receiver more chances to hear one through the noise — or raise the transmit power if battery life allows. Both changes have operational trade-offs that should be weighed against the improvement in detection reliability.
BLE Beacon Interference Troubleshooting
When a beacon deployment produces inconsistent results — missed triggers, phantom zone entries or erratic distance readings — interference is one of several possible causes. A structured approach isolates the problem faster than adjusting settings at random.
Start by confirming the baseline. Take a beacon and a receiving device into a space with minimal radio traffic — a large open room away from Wi-Fi access points, metal and crowds — and log RSSI at known distances. Compare these readings to what you see in the problematic location. If the controlled readings are stable and the on-site readings are not, the environment is the cause.
Next, narrow down the source. Disable the venue's 2.4 GHz Wi-Fi temporarily, if operations allow, and observe whether packet loss or RSSI variance changes. If it does, Wi-Fi coexistence is a factor and you can investigate channel assignments or consider whether 2.4 GHz client traffic can be shifted. If there is no change, look for localised sources: metal fixtures near the affected beacon, other BLE devices in the immediate area or structural elements such as lifts or service ducts that may contain metal or moving parts.
Check the physical mounting. Beacons that have shifted since installation — slid along a rail, rotated on a magnetic mount, or had a nearby metal object moved closer — will behave differently from when they were calibrated. Photograph each beacon's mounting position during installation and compare to the current state during troubleshooting.
Finally, review the beacon configuration. If transmit power was reduced at some point to extend battery life, the signal may no longer have enough margin to overcome the local interference. If the advertising interval is very long, the receiver simply has fewer opportunities to detect the beacon in a noisy environment. Adjust one variable at a time and re-test, rather than changing multiple settings simultaneously.
Common mistakes during troubleshooting
- Changing beacon settings and receiver app logic at the same time, making it impossible to tell which change had an effect.
- Testing with a single phone model and assuming the result applies to all devices — different handsets have different antenna designs and BLE chipsets.
- Ignoring time-of-day variation; interference from Wi-Fi and other Bluetooth devices often changes with occupancy.
Signal Behaviour in Crowded Spaces
The human body is largely water, and water attenuates 2.4 GHz radio signals significantly. A single person standing between a beacon and a phone will reduce the received signal strength. A dense crowd — a queue at a till, a packed gallery opening, a conference breakout session — can block or scatter the signal to the point where a beacon three metres away reads as though it is ten or more.
This effect is not constant. As people move, the path between beacon and receiver opens and closes, causing RSSI to fluctuate rapidly. Zone-entry logic that requires a single RSSI reading to cross a threshold will fire repeatedly: the visitor steps into the zone, someone walks in front of the beacon, the reading drops below the threshold and the visitor appears to leave, then the path clears and they appear to enter again. The result is a stream of duplicate notifications or, if the system includes hysteresis to prevent that, a visitor who is physically inside the zone but never triggers it because the signal never sustains a reading above the entry threshold for long enough.
Designing for crowded environments means building in temporal filtering. Rather than reacting to a single RSSI reading, the receiving software should average readings over a short window — typically one to three seconds — or require several consecutive readings above the threshold before registering a zone entry. The trade-off is a slight delay in triggering, which is almost always preferable to rapid toggling or missed detections.
Placement also matters. Mounting beacons above head height — on ceiling grids, overhead trusses or the top of high shelving — keeps the line of sight clear of the densest part of the crowd. Beacons mounted at waist or knee height in a busy aisle will frequently be obscured. If overhead mounting is not possible, increasing transmit power or adding a second beacon at a different height to provide redundancy can improve consistency, at the cost of additional hardware and battery replacement effort.
When planning a deployment in a space that experiences wide variation in occupancy — a museum that is quiet on weekday mornings and busy at weekends, or a retail unit during a sale period — test during both conditions. Calibration performed in an empty room will not represent real-world behaviour, and zone boundaries that work for a handful of visitors may fail completely when the space is full.
