Juniper Mist Location & vBLE — Watch a BLE Signal Become a 1-3 m Location

Before vBLE — the one idea that flips everyone's mental model

For 15 years, indoor location meant physical beacons: little battery pucks glued to walls every few metres. Someone surveys the building, sticks 200 beacons, swaps 200 batteries a year, and re-surveys whenever a shelf moves. Painful.

Juniper Mist flips that. The vBLE array is built into the access point you already bought for Wi-Fi. The beacons are virtual — you drag them onto a floorplan in the cloud. No survey, no batteries, no ladders. Move a beacon? Drag it in the portal. That single idea — "the location infrastructure is the AP" — is what you must internalise first.

🧒 ELI5: Think of each Mist AP as a lighthouse that can sweep eight beams of invisible Bluetooth light in eight directions. By comparing which beams a phone or tag "sees" brightest, the cloud guesses where it is standing — like spotting which window in a building a torch is shining from.

🏛 Architect: Strategically, vBLE collapses three procurement lines (Wi-Fi APs, beacon hardware, location appliance) into one cloud-managed asset. The location compute lives in the Mist cloud as an ML pipeline; the AP is a pure sensor/emitter. Your design lever is AP density and placement, not beacon count — which means location quality is a by-product of a good Wi-Fi design, not a separate project.

① How vBLE works — beams, fingerprints, and an (x,y)

Here's the mechanism. Each Mist AP sweeps 8 directional BLE beams. A phone or tag hears each beam at a different RSSI. The Mist cloud has already split the floorplan into 1-metre squares and pre-computed an expected RF fingerprint for each square. It compares the live RSSI pattern to the fingerprints and returns the best-matching square as an x,y — in well under a second.

② Asset Visibility — find the wheelchair, count the room

Flip the array into listen mode and it becomes an asset tracker. Stick a small BLE tag on anything — a wheelchair, a forklift, a high-value laptop — and Mist locates it on the floorplan. You then create a Named Asset so "F4:CE:36…" shows up as "Wheelchair 14."

Group the floor into Zones and you get occupancy, dwell time, and "is the crash-cart in the right ward?" answers. This is the bread-and-butter of healthcare and warehouse Mist deployments.

Creating a Named Asset — the exact dashboard path

From the Mist portal, the menu path is Location → Live View for the map, and Organization → Asset Filters / Named Assets to bind tags. The non-negotiable rule: the tag must advertise a static MAC.

Name:            Wheelchair-14
MAC Address:     F4:CE:36:1A:2B:7C   (must be STATIC — no randomization)
Asset Type:      Medical Equipment
BLE Adv interval: 250 ms              (range 100–1000 ms)
BLE Tx power:    0 dBm                (NEVER below 0 dBm)

Asset: Wheelchair-14   STATE: Located
Floor: HQ-Floor-2      Zone: Ward-B
Position: x=14.2m y=8.7m   Accuracy: ~1.8m
Last seen: 3s ago      Heard by: AP-12, AP-14, AP-17, AP-19

③ Wayfinding & Proximity — the blue dot and the push

Now flip to transmit. The array radiates virtual beacons a phone can hear. A retail or campus app embeds the Mist SDK, which reads those beacons and shows the user's own blue dot — turn-by-turn indoor navigation. Cross a virtual beacon near the pharmacy counter and the app can fire a proximity push: "20% off vitamins today."

Wayfinding and proximity ride the User Engagement subscription. Critically, the user must run your app (with the SDK) for engagement to work — unlike asset tags, the phone isn't a tag you can track silently.

④ Deploy & Troubleshoot — get the dot to land where the thing is

Location quality is mostly an AP placement problem. The deployment rules from the Mist Location guide are blunt and worth memorising: APs 25-32 ft apart, every tracked tag with line of sight to ≥4 APs, BLE Tx power ≥0 dBm, and the floorplan in the portal must exactly match the physical AP positions.