Indoor Bluetooth presence systems often fail for a very simple reason. Someone takes an RSSI number, treats it like a tape measure, and then builds room logic on top of that mistake. That is where trouble starts.<\/p>\n\n\n\n
RSSI is useful. We use it all the time in Bluetooth presence work. But RSSI is not distance in the literal, dependable, wall-proof sense many teams want it to be. It is a radio-strength hint, shaped by packet timing, antenna behavior, body blocking, reflections, channel conditions, and plain old indoor messiness. Bluetooth itself still broadcasts legacy advertising on up to three primary advertising channels, and those events are intentionally perturbed in time to reduce collisions. That helps the protocol, but it also means the receiver is not observing one clean, stable signal from one clean direction. (1)(2)<\/a><\/sup><\/p>\n\n\n\n For Lansitec deployments, this matters a lot because B-Mobile and B-Fixed are powerful systems precisely when they are used for what RSSI does well: presence, proximity, room-level inference, and rough positioning. Lansitec\u2019s own guidance is refreshingly honest here. In B-Mobile, a gateway can often hear a beacon in the next room, but the signal is usually much weaker, and the RSSI gap between the \u201ccorrect room\u201d and the adjacent room can be up to 20 dBm. The same guidance also says single-point positioning is suitable for room-level and rough tracking, not exact indoor coordinates.<\/p>\n\n\n\n RSSI tells you how much signal power arrived at the receiver for a given packet. It does not<\/strong> tell you, by itself, the real physical path the signal took, whether the packet was partially body-shadowed, whether it arrived after bouncing off metal shelving, or whether the sample came from channel 37, 38, or 39 under slightly different RF conditions. Texas Instruments notes that, in BLE, only the RSSI of the last received packet is reported, with no averaging across channels, and that correlating RSSI directly to distance is not easy because antenna design and polarization affect it heavily. TI also cites expected RSSI accuracy around \u00b14 dBm in the referenced implementation. (2)<\/a><\/sup><\/p>\n\n\n\n That \u00b14 dBm point may sound small. Indoors, it isn\u2019t.<\/p>\n\n\n\n When Lansitec says an adjacent-room difference can be up to 20 dBm, that sounds comfortable. But \u201cup to\u201d is doing a lot of work there. In clean cases, yes, the right room should look clearly stronger. In borderline cases, especially with open doors, glass, corridors, thin partitions, forklifts, people, and metal cabinets, that margin shrinks fast.<\/p>\n\n\n\n So the right mental model is this: RSSI is evidence of nearness, not proof of exact distance.<\/strong><\/p>\n\n\n\n We\u2019ve seen three recurring mistakes.<\/p>\n\n\n\n First, teams use a single threshold like \u201cstronger than -70 dBm means inside the room.\u201d Clean on paper. Fragile in a real building.<\/p>\n\n\n\n Second, they ignore timing. In B-Fixed, Lansitec states the tracker\u2019s Bluetooth receiving<\/a> window is three seconds, and the beacon transmission interval should not be longer than one second, with 800 ms, 500 ms, or less recommended. It even notes that, with a 100 ms interval, the tracker can receive multiple samples in a 3-second window, drop the highest and lowest RSSI, and average the rest. That is not a cosmetic detail. It is exactly how you make RSSI less noisy.<\/p>\n\n\n\n Third, they expect one radio technology to do two jobs. Presence detection is one job. Fine-grained positioning is another. Silicon Labs\u2019 current Bluetooth Channel Sounding guidance is blunt on this point: existing Bluetooth location solutions<\/a> often rely on RSSI and\/or AoA\/AoD, but Channel Sounding uses time- and phase-based methods and is expected to be significantly more accurate than RSSI-based measurements. (3)<\/a><\/sup><\/p>\n\n\n\n In other words, don\u2019t ask coarse RSSI presence logic to behave like precision ranging.<\/p>\n\n\n\n This is where Lansitec\u2019s portfolio is actually quite well segmented.<\/p>\n\n\n\n In B-Mobile<\/a><\/strong>, fixed Bluetooth gateways<\/a> listen for mobile beacons<\/a> on people or assets. Lansitec recommends an 800 ms advertising interval for fast-walking people, notes indoor transmission distance is typically around 10 to 30 meters, and explicitly warns that next-room reception is common but weaker. Presence detection here is best understood as: the person is near this gateway or in this zone<\/em>, not the person is exactly 4.2 meters from the east wall<\/em>.<\/p>\n\n\n\n In B-Fixed<\/a><\/strong>, the architecture flips. Fixed beacons<\/a> are installed in known places and mobile trackers<\/a> listen for them. Here again, Lansitec describes single-point presence detection as rough tracking and gives the familiar log-distance formula for RSSI-based estimation. Useful? Yes. Absolute truth? No. The same document also explains why shorter advertising intervals improve stability: more packets arrive inside the receive window, so the system can reject outliers and average the rest.<\/p>\n\n\n\n That means a good Lansitec deployment should interpret RSSI in layers:<\/p>\n\n\n\n That third step is where many systems cheat… and where users lose trust.<\/p>\n\n\n\n Here is the practical rule we\u2019d use in a Lansitec presence deployment: Never decide room presence from one packet. Decide it from a short window of packets plus a margin against the runner-up receiver.<\/strong><\/p>\n\n\n\n For example:<\/p>\n\n\n\n That logic matches the spirit of Lansitec\u2019s own deployment guidance. B-Mobile says one gateway can work for a relatively small room, but corridor and lobby placement is more economical when the real question is whether someone left the room, not precisely where they are inside it. It also says putting a gateway in every room improves accuracy. That\u2019s exactly right. More certainty usually comes from geometry and placement, not from squeezing one more decimal place out of RSSI.<\/p>\n\n\n\n If your building has many small rooms and you truly need room confirmation, a gateway-per-room design is often the clean answer. If your goal is to know whether someone has left a room or entered a corridor, fewer gateways<\/a> in corridors and lobbies may be enough, and cheaper. Lansitec says as much in its B-Mobile deployment Q&A.<\/p>\n\n\n\n For industrial areas, workshops, or hazardous spaces, Lansitec guidance recommends denser deployment, often around every ten meters, depending on site conditions. Again, that is a geometry decision, more than a software trick.<\/p>\n\n\n\n This is also why product choice matters:<\/p>\n\n\n\n A mature system does not always say \u201cinside room A.\u201d<\/p>\n\n\n\n Sometimes it should say:<\/p>\n\n\n\n That may sound less bold, but it is much more credible. And credibility is what keeps operations teams from turning alerts off after two frustrating weeks.<\/p>\n\n\n\n RSSI is enough when your question is:<\/p>\n\n\n\n RSSI is not enough when your question is:<\/p>\n\n\n\n The Bluetooth SIG\u2019s current positioning guidance reflects this nicely. It says Bluetooth Channel Sounding can be combined with RSSI, with RSSI handling presence, proximity, and coarse ranging at longer distances and Channel Sounding increasing accuracy as devices get closer. (4)<\/a><\/sup><\/p>\n\n\n\n That is a smart architecture, and honestly, it matches what experienced deployers have learned the hard way.<\/p>\n\n\n\n If you are building on Lansitec B-Mobile or B-Fixed, treat RSSI as a decision input<\/strong>, not a distance output<\/strong>.<\/p>\n\n\n\n Use it to rank receivers. Use it to infer room presence when the margin is clear. Use windows, averaging, and hysteresis. Use denser placement when the operational question is stricter. Use configurable proximity gateways<\/a> when the outcome is an alert, not a map coordinate. And when the job truly needs sub-meter or decimeter confidence, stop forcing RSSI to do precision work and move to Lansitec AoA or UWB. Lansitec\u2019s own positioning portfolio exists for exactly that reason.<\/p>\n\n\n\n RSSI is not distance. But interpreted properly, it is still incredibly valuable.<\/p>\n\n\n \n\t\tCan RSSI still be used for room-level presence?\t<\/p>\n\tWhat RSSI Means in BLE Indoor Positioning<\/h2>\n\n\n\n
Common RSSI Mistakes in Indoor Positioning Systems<\/h2>\n\n\n\n
How to Use RSSI Correctly in BLE Presence Detection<\/h2>\n\n\n\n
\n
Best Practices for Using RSSI in Indoor Tracking<\/h2>\n\n\n\n
\n
Why Beacon Placement Matters More Than RSSI Thresholds<\/h2>\n\n\n\n
\n
How to Interpret BLE Presence Data Correctly<\/h2>\n\n\n\n
\n
When RSSI Works and When You Need More Accurate Positioning<\/h2>\n\n\n\n
\n
\n
How to Improve BLE Indoor Positioning Accuracy<\/h2>\n\n\n\n
Frequently Asked Questions<\/h2>\n\t
About RSSI Indoor Positioning<\/h3><\/div>\n