Can a barometer really tell which floor I’m on?

Yes, as a relative indicator. Pressure shifts slightly as you move a few meters up or down, which is usually enough to separate floors once you calibrate “floor bands” for that building. Lansitec explicitly recommends using the tracker’s built-in barometer to measure floor height and differentiate floors. For hardware examples, Lansitec lists barometer support and altitude-related specs on Helmet Sensor and NB-IoT/LTE-M Badge Tracker pages.

Won’t weather changes mess up barometer floor detection?

Weather changes pressure slowly, over hours. Floor changes happen quickly, in seconds. In practice, you handle this by anchoring to a reference floor (or a baseline) and using smoothing plus hysteresis so the system reacts to fast changes, not slow drift. Sensor vendors also talk about long-term drift characteristics, which is why we treat the barometer as “relative and filtered,” not absolute altitude.

How do I calibrate floor heights with barometer data?

A pragmatic method we’ve used: - Record stable pressure readings on each floor (30–60 seconds per floor). - Store either absolute pressure bands per floor, or pressure differences relative to a chosen reference floor. - Re-anchor occasionally (daily, weekly, or after big HVAC changes) if your environment is sensitive. For the underlying pressure-altitude relationship, NCAR’s note is a good reference.

What happens near stairwells or elevators where ghosting is worst?

That’s where a barometer helps most. RSSI gets chaotic near vertical openings, so you use conservative rules: - Require 2–3 consecutive confirmations before switching floors. - Add hysteresis so a person climbing stairs doesn’t bounce off the floor on every step. The “why” is also covered in Lansitec’s own multi-floor guidance and deployment notes.

My beacons can’t go as low as -26 dBm. What do I do?

Still reduce power as far as your model supports, then fix the rest with placement and zoning: - Move beacons away from stair cores, elevator shafts, and atriums. - Tighten zones so overlap stays local on the same floor. - Use a barometer to break ties when RF leaks anyway. Lansitec’s -26 dBm note is a site-specific recommendation, not a universal requirement.

What beacon interval should I use for reliable detection while people move?

Match the tracker’s listening behavior. Lansitec notes a 3-second Bluetooth receiving window and recommends keeping beacon intervals at 1 second or less, with 800 ms and 500 ms as practical starting points. This gives you enough packets to make stable decisions without waiting ages.

Do I need a barometer if I already separate beacon IDs by floor?

If your building has clean RF separation, maybe not. But in real sites with shafts, metal structures, or open voids, cross-floor bleed shows up sooner or later. The barometer acts as the “second vote” that prevents those occasional teleports. Lansitec recommends both approaches: floor-specific beacon identification plus barometer-based height differentiation where needed.

Precisione del posizionamento indoor: guida essenziale al tracciamento su più piani senza salti di piano

24 marzo 2026
Notizia

24 marzo 2026
Notizia

A practical playbook for BLE beacon power tuning + barometer-based floor hints.

What Is Floor Jumping in Indoor Positioning Systems?

Ghosting happens when your tracking engine “sees” fari from the wrong floor. Stairwells, elevator shafts, hollow metal decking, and open atriums make it worse. RSSI alone can’t save you.

So we use a two-layer approach:

Contain RF per floor by reducing beacon Potenza di trasmissione and designing coverage like zones.
Break ties with height using a barometer signal from the wearable.

This is not theoretical. Lansitec’s own B-Fixed deployment notes call out multi-floor interference and tell you exactly what to tweak. ⁽¹⁾

How to Fix Multi-Floor BLE Tracking Errors

1) How to Assign Unique Beacon IDs Per Floor, before you touch RF

Don’t let floors look identical.

A simple, scalable rule:

Give each floor its own beacon group (IDs that never overlap across floors).
Keep a predictable naming scheme so your backend can interpret “Floor 2, Zone 7” instantly.

Lansitec explicitly recommends deploying different fari for different floors to identify floors. ⁽¹⁾

2) How to Reduce BLE Beacon Signal Bleed Between Floors so it stops bleeding upstairs

This is the fastest ghosting reducer.

In a multi-floor chemical factory example (hollowed metal floors), Lansitec recommends reducing beacon signal transmission power to -26 dBm to avoid interference between floors. ⁽¹⁾

Reality check: not every beacon supports -26 dBm. But the principle holds: turn it down until the next floor mostly disappears.

From the same B-Fixed document, one beacon spec lists RF power options roughly -21 dBm to +5 dBm. If your beacon bottoms out at -20/ -21 dBm, you still win by being deliberate about placement.

Quick field loop (we use this a lot):

Start low TX.
Walk hotspots (stairs, elevator lobbies, void edges).
If Floor 2 fari still show up strongly on Floor 1, lower TX again or move the beacon a few meters away from the shaft.
Repeat until cross-floor receptions become rare and weak.

3) Best BLE Beacon Interval per Reliable Indoor Tracking

Many ghosting incidents actually start here: the tracker doesn’t listen continuously.

In Lansitec’s B-Fixed tracking principles:

The tracker’s Ricezione Bluetooth window is 3 seconds.
The beacon transmission interval should not exceed 1 second, or the tracker may miss it.
Lansitec suggests 800 ms, 500 ms, or less as a practical range.

That interval also helps your backend stabilize floor decisions without waiting forever for packets.

4) Using Barometer Sensors for Accurate Floor Detection

RF containment gets you 80% of the way. Barometer gets you the last 20%, especially near stairs.

Two Lansitec wearables you can use as “height hint sources”:

LoRaWAN Helmet Sensor: barometer supported, 10 cm altitude accuracy. ⁽²⁾
NB-IoT & LTE-M Badge Tracker (NBM2): barometer + accelerometer, detects altitude changes around ±1 m (as stated on the product page). ⁽³⁾

Use the barometer as a relative floor discriminator, not as absolute altitude. You care about “Floor 3 vs Floor 4,” not “312.6 meters above sea level.”

If you want a formal basis for converting pressure to altitude (and why temperature matters), NCAR’s note on pressure altitude walks through the standard equations and constants. ⁽⁵⁾

5) How to Combine BLE and Barometer Data for Floor Accuracy

This is where ghosting dies.

A practical fusion strategy:

Let fari vote for a floor (based on your floor-specific ID grouping).
Let barometer vote for a floor band (based on calibrated floor-to-floor height).
Only switch floors after stable evidence.

Rule of thumb (simple, effective):

Require 3 consecutive reports agreeing on a new floor before you switch.
Add hysteresis around stairwells so a person doesn’t bounce floors mid-step.

Barometric sensori can resolve small altitude changes, but they also drift over time. Bosch’s BMP581 press release highlights both high relative accuracy and long-term drift characteristics, which is exactly why we treat the barometer as relative + periodically re-anchored. (4)

Multi-Floor BLE Configuration Guide

Building condition	Faro Potenza di trasmissione approach	Beacon interval	Barometer role
Concrete floors, closed stair cores	Low to mid (reduce overlap)	500–800 ms target	Tie-breaker
Hollow/metal decking, open shafts	Push very low (example guidance: -26 dBm where supported)	500 ms or less	Primary floor lock
Mixed site (warehouse + offices)	Lower in offices, slightly higher in open bays	500–800 ms	Strong near transitions

Multi-Floor Indoor Tracking Deployment Checklist

Separate fari by floor so IDs never overlap.
Reduce Potenza di trasmissione until cross-floor receptions become weak and rare (Lansitec example: -26 dBm in a multi-floor metal-deck area).
Keep beacon intervals aligned with the 3-second receive window (target 800 ms / 500 ms).
Turn on barometer floor bands on wearables that support it (Helmet Sensor, NBM2 badge).
Add a conservative floor-switch rule (3 confirmations, hysteresis).

Domande frequenti

About Multi-floor Indoor Tracking

Can a barometer really tell which floor I’m on?

Yes, as a relative indicator. Pressure shifts slightly as you move a few meters up or down, which is usually enough to separate floors once you calibrate “floor bands” for that building. Lansitec explicitly recommends using the tracker’s built-in barometer to measure floor height and differentiate floors. For hardware examples, Lansitec lists barometer support and altitude-related specs on Helmet Sensor and NB-IoT/LTE-M Badge Tracker pages.
Won’t weather changes mess up barometer floor detection?

Weather changes pressure slowly, over hours. Floor changes happen quickly, in seconds. In practice, you handle this by anchoring to a reference floor (or a baseline) and using smoothing plus hysteresis so the system reacts to fast changes, not slow drift. Sensor vendors also talk about long-term drift characteristics, which is why we treat the barometer as “relative and filtered,” not absolute altitude.
How do I calibrate floor heights with barometer data?

A pragmatic method we’ve used:

– Record stable pressure readings on each floor (30–60 seconds per floor).

– Store either absolute pressure bands per floor, or pressure differences relative to a chosen reference floor.

– Re-anchor occasionally (daily, weekly, or after big HVAC changes) if your environment is sensitive.

For the underlying pressure-altitude relationship, NCAR’s note is a good reference.
What happens near stairwells or elevators where ghosting is worst?

That’s where a barometer helps most. RSSI gets chaotic near vertical openings, so you use conservative rules:

– Require 2–3 consecutive confirmations before switching floors.

– Add hysteresis so a person climbing stairs doesn’t bounce off the floor on every step.

The “why” is also covered in Lansitec’s own multi-floor guidance and deployment notes.
My fari can’t go as low as -26 dBm. What do I do?

Still reduce power as far as your model supports, then fix the rest with placement and zoning:

– Move fari away from stair cores, elevator shafts, and atriums.

– Tighten zones so overlap stays local on the same floor.

– Use a barometer to break ties when RF leaks anyway.

Lansitec’s -26 dBm note is a site-specific recommendation, not a universal requirement.
What beacon interval should I use for reliable detection while people move?

Match the tracker’s listening behavior. Lansitec notes a 3-second Ricezione Bluetooth window and recommends keeping beacon intervals at 1 second or less, with 800 ms and 500 ms as practical starting points. This gives you enough packets to make stable decisions without waiting ages.
Do I need a barometer if I already separate beacon IDs by floor?

If your building has clean RF separation, maybe not. But in real sites with shafts, metal structures, or open voids, cross-floor bleed shows up sooner or later. The barometer acts as the “second vote” that prevents those occasional teleports. Lansitec recommends both approaches: floor-specific beacon identification plus barometer-based height differentiation where needed.