What the work must achieve
Bluetooth Low Energy beacons and Wi-Fi access points share the 2.4 GHz ISM band. Because both technologies occupy the same slice of spectrum, they compete for airtime. The practical consequence for beacon deployments is not a binary "works or fails" outcome but a measurable reduction in received signal strength and an increase in packet loss, particularly on the three fixed advertising channels that beacons rely on.
Wi-Fi in the 2.4 GHz band uses channels spaced 5 MHz apart, but each channel occupies roughly 22 MHz of bandwidth. In the UK, channels 1 through 13 are available. This means adjacent channels overlap substantially. The standard non-overlapping set is channels 1, 6 and 11, though some network engineers also use channel 13 in specific configurations. When an access point transmits on channel 1, its energy spreads well beyond the nominal 2412 MHz centre frequency.
BLE advertising uses three fixed channels: 37 at 2402 MHz, 38 at 2426 MHz and 39 at 2480 MHz. Channel 38 sits squarely within the footprint of Wi-Fi channel 1. Channel 39 falls within the footprint of Wi-Fi channel 13. Channel 37 sits just below channel 1 but can still receive interference from out-of-band emissions, particularly from high-power access points nearby. Unlike BLE data connections, which use adaptive frequency hopping across 37 channels to avoid congestion, advertising packets have nowhere else to go. If a Wi-Fi transmission occupies the air at the moment a beacon advertises on channel 38, that packet is simply lost.
The severity of the effect depends on two factors that are often confused: channel assignment and traffic load. An access point configured on channel 1 but carrying almost no traffic will cause far less disruption than one on the same channel serving a dense cluster of connected devices. Measuring the channel plan alone tells you where overlap exists. Measuring airtime utilisation tells you whether that overlap actually matters.
Make decisions using comparable evidence
Retail Environments
Most UK retail premises run corporate Wi-Fi for point-of-sale systems, stock management tablets and guest Wi-Fi. Access points are typically ceiling-mounted at regular intervals, often on channels 1, 6 and 11 in a repeating pattern. Beacons mounted on the same ceiling grid will frequently sit within a metre or two of an access point. In this configuration, beacon advertising packets on channel 38 or 39 are competing directly with Wi-Fi frames that are transmitted at significantly higher power. The observable effect is increased RSSI variance: a phone standing still near a beacon will report fluctuating signal readings rather than a stable value, which degrades zone detection reliability.
Museums and Galleries
Museum environments often have lower Wi-Fi density than retail, but the challenge shifts to exhibit-specific access points or media servers that stream content to nearby devices. A single access point serving an interactive exhibit may generate sustained, heavy traffic on one channel. If beacons for that gallery zone advertise on the overlapping BLE channel, visitors may experience delayed or missed notifications. The practical response is to map which Wi-Fi channels are heavily loaded in each gallery and note which BLE advertising channels are affected, then factor that into beacon placement and zone threshold calibration.
Events and Temporary Venues
Temporary event Wi-Fi is often deployed rapidly, with access points set to auto-channel selection. During peak periods, channel assignments can shift as the network adapts to interference from neighbouring stands or external sources. A beacon pilot that works reliably during setup may degrade once the event opens and Wi-Fi traffic climbs. For event deployments, it is worth confirming whether the Wi-Fi provider locks channel assignments or uses dynamic channel selection, and if the latter, agreeing on a monitoring approach during live operation.
Coexistence Strategies That Actually Help
- Request the Wi-Fi channel plan before finalising beacon placement. Knowing which channels are in use and where allows you to predict which BLE advertising channels will be under pressure in each zone.
- Measure airtime utilisation, not just channel allocation. A spectrum analyser or Wi-Fi survey tool that shows percentage of time the channel is occupied gives a far better picture of real interference than a channel list.
- Separate beacon and access point mounting positions where possible. Even 1.5 to 2 metres of physical separation reduces the near-field impact, though it does not eliminate channel-level overlap.
- Calibrate zone thresholds in situ with the Wi-Fi network running under typical load. RSSI values measured with Wi-Fi disabled are misleading for operational planning.
- Consider 5 GHz Wi-Fi migration for devices that support it. Moving client devices to 5 GHz reduces 2.4 GHz airtime contention, which indirectly benefits beacon reliability. This is a network-team decision, but raising it early can produce a better outcome for both systems.
Residual risk and lifecycle decisions
Assuming Different Protocols Mean No Interference
A persistent misconception is that because Wi-Fi and BLE use different modulation schemes and protocol stacks, they do not interfere. They do not decode each other's packets, but they cannot occupy the same frequency simultaneously. A Wi-Fi transmission masks any BLE packet in the same frequency band at that moment, regardless of protocol. The interference is physical, not logical.
Blaming Beacons for Wi-Fi-Caused Problems
When zone detection becomes unreliable or notifications arrive inconsistently, the instinct is often to question the beacons themselves. If the environment has not been assessed for Wi-Fi coexistence, the root cause may be channel overlap rather than beacon hardware or placement. Checking Wi-Fi channel usage and airtime should be an early diagnostic step, not a last resort.
Measuring Without Load
Running a beacon survey before the Wi-Fi network is live, or during a quiet period, produces optimistic results. RSSI readings and packet delivery rates measured under these conditions will not reflect operational reality. Wherever possible, calibrate with representative traffic on the network.
Overlooking Client-Side Variation
Different smartphone models have different Wi-Fi and Bluetooth radio front-ends and antenna designs. Some handle coexistence better than others. A deployment that performs adequately on one device model may show higher packet loss on another. This is a reason to test with a range of common handsets rather than a single reference device.
Key Checks Before Going Live
- Obtain the current 2.4 GHz channel plan from the network team or Wi-Fi provider, including channel width settings (20 MHz vs 40 MHz, as wider channels increase overlap).
- Run a spectrum or airtime survey during a representative busy period, noting which channels exceed roughly 30 to 40 percent utilisation in beacon zones.
- Identify which BLE advertising channels (37, 38, 39) overlap with the busiest Wi-Fi channels in each area.
- Measure RSSI variance at fixed points with Wi-Fi at operational load. High variance indicates coexistence pressure.
- Confirm whether the Wi-Fi network uses dynamic channel selection and, if so, what the implications are for beacon performance if channels shift during operation.
- Document findings alongside the beacon asset register so that future troubleshooting can distinguish between coexistence issues and other causes such as battery depletion or physical obstruction.
Wi-Fi coexistence does not make beacon deployments unworkable, but it does introduce a variable that must be measured rather than assumed away. In most UK retail and venue environments, the effect is manageable once the channel plan and traffic load are understood and factored into placement and calibration decisions.
