Why Walls Change Bluetooth Coverage
Bluetooth Low Energy (BLE) beacons transmit at 2.4 GHz, a frequency that behaves more like light than radio in many respects: it struggles to pass through solid objects and loses energy each time it does. When a beacon signal crosses a wall, the received signal strength indicator (RSSI) drops by a measurable amount. That drop is not uniform — it depends entirely on what the wall is made of, how thick it is, and whether it contains any hidden layers such as metal mesh, moisture barriers or services.
The attenuation caused by a wall is typically expressed in decibels (dB). A single internal partition made of plasterboard on a timber stud might reduce the signal by roughly 3 to 5 dB, whereas a dense concrete block wall could easily account for 10 to 15 dB or more. Because RSSI values used in proximity detection often sit in the range of -40 to -80 dBm, losing 10 dB through one wall can be the difference between a phone registering a beacon reliably and failing to see it at all.
Cumulative loss matters as well. Two plasterboard partitions in sequence do not simply double the single-wall figure; the total attenuation is the sum of each barrier's loss plus any additional free-space path loss over the increased distance. In a corridor with rooms on both sides, a beacon placed in one room may be undetectable two rooms away even if the straight-line distance suggests it should be within range.
It is also worth understanding that walls do not just attenuate the signal — they reflect and scatter it. A portion of the radio energy bounces back, and some travels along alternative paths around doorways and junctions. This creates multipath interference: the receiving device sees multiple copies of the same signal arriving at slightly different times, which can cause the RSSI value to fluctuate even when the phone and beacon are both stationary. For deployments that rely on stable RSSI readings, this fluctuation is a practical problem rather than a theoretical one.
Venue Scenarios and Better Placement Choices
Retail environments
Modern retail units often use lightweight partition walls to define changing areas, stockrooms and promotional zones. These typically cause moderate attenuation, but the real difficulty arises when a beacon is placed in a back room and expected to trigger a notification at the shop front. Even if the distance is only a few metres, the partition plus any racking or merchandise in between can push the signal below the detection threshold. The practical response is usually to place a second beacon closer to the entrance rather than increasing the transmit power of the first, because higher power shortens battery life and may cause unintended overlap with neighbouring zones.
Museums and heritage buildings
Museum spaces present some of the most challenging wall conditions. Historic buildings frequently feature solid brick or stone walls that are substantially thicker than modern equivalents. A Victorian museum gallery wall might be 300 mm or more of solid brick, producing attenuation that makes cross-wall detection impractical with standard beacon hardware. In these settings, each gallery or room generally needs its own beacon or set of beacons, and zone boundaries are effectively defined by the architecture itself. This is not necessarily a disadvantage: thick walls can act as natural zone separators, reducing the risk of a visitor in one gallery triggering content intended for the next.
Events and temporary venues
Temporary event partitioning — fabric panels, modular walls, draped sections — tends to have a lower and less predictable impact on Bluetooth signals. Some materials are essentially transparent to 2.4 GHz, while others incorporate metallic coatings or dense foam that can cause surprising levels of attenuation. Because event layouts change frequently and wall materials may not be documented, the only reliable approach is to measure on-site during the build phase rather than assuming behaviour based on appearance alone.
Using walls to your advantage
Not all wall effects are problematic. In some deployments, walls provide useful signal containment that helps define proximity zones without requiring complex software boundaries. A beacon placed inside a meeting room, for example, may naturally be undetectable in the corridor outside because of the wall attenuation — which means the zone is physically constrained rather than relying solely on an RSSI threshold that could drift. When planning a deployment, it is worth noting which walls provide this incidental containment and designing the zone map around them.
When Power Changes Are Not the Answer
Assuming all walls behave the same
One of the most frequent errors is treating wall attenuation as a single fixed value across a site. In practice, a building often contains a mixture of construction types: plasterboard partitions, blockwork, glazed screens, and older sections with entirely different materials. Even walls that look identical may differ internally — a partition running alongside a lift shaft, for instance, might contain additional reinforcement or fire-rated layers that are not visible. Each wall type should be treated as a separate variable until measured.
Placing beacons without on-site measurement
Desktop planning tools and floor plans are useful for initial beacon placement, but they cannot account for the actual attenuation profile of a specific building. The only reliable method is a walk-test: install a beacon at the proposed location, then measure the RSSI at relevant points on the other side of each wall using the same model of phone or receiver that visitors will use. Record the values, note the wall construction, and compare the results against your zone thresholds. This process should be repeated if anything in the environment changes — new racking, seasonal decorations, or relocated furniture can all alter the signal path.
Over-relying on increased transmit power
When a signal is too weak after passing through a wall, the instinct is often to raise the beacon's transmit power. This can work in some cases, but it introduces trade-offs: higher power reduces battery life, increases the risk of zone overlap in open areas, and may not solve the problem if the attenuation is severe. In most cases, adding another beacon on the correct side of the wall is a more robust solution than trying to push a signal through a barrier it was not designed to cross.
Key checks before going live
- Walk every planned zone boundary with a test device and confirm that RSSI values match your threshold settings on both sides of each relevant wall.
- Test with at least two different phone models, because device antennas vary and a wall that allows adequate signal to one handset may block another.
- Check for fluctuation: stand still for 30 seconds on the far side of a wall and watch whether the RSSI value jumps around. High variance indicates multipath interference, which may require a wider threshold margin or a different beacon position.
- Document the wall type and measured attenuation in your installation records so that future adjustments or additions can be planned without re-measuring from scratch.
- Verify that walls intended to contain a zone actually do so by testing from adjacent spaces — particularly corridors, stairwells and rooms above or below.
Accepting the limits
There are situations where walls simply make a proposed beacon layout unworkable. If a zone requires reliable detection through two or more substantial walls, the deployment is likely to produce inconsistent results regardless of hardware adjustments. In those cases, the honest response is to reconsider the zone design — either by adding more beacons, narrowing the detection requirement, or accepting that certain areas will need an alternative approach such as NFC or QR codes placed at the point of interaction.
