Location-based Services · Topic 1 of 2
vBLE Asset Visibility
Learn Juniper Mist vBLE asset visibility: enabling it per site, BLE tag types, asset filters, Live View, zones and the SUB-AST subscription for assets.
- 5 min
- Asset visibility: BLE tags transmit, Mist APs listen, the cloud calculates location.
- Enable it under Organization > Site Configuration > Bluetooth based Location Services, or in a device profile.
- Assets appear on Location > Live View; the APs must be on a floor plan.
What it is
Asset visibility lets Juniper Mist APs find things that carry a BLE tag: wheelchairs, infusion pumps, machinery, carts, laptops and tablets. The tag broadcasts Bluetooth Low Energy signals, the APs listen, and the Mist cloud calculates where the tag is and shows it on the floor plan.
Juniper says asset visibility works with standards based third party BLE tags, including iBeacon and Eddystone tags. You do not need tags from one vendor, and you do not need to install separate BLE receivers, because the APs do the listening.
How it works
Turning it on
Asset visibility is enabled per site:
- Select Organization > Site Configuration and choose the site.
- Scroll to Bluetooth based Location Services.
- Enable Asset Visibility.
The same options can be set in device profiles instead of at site level. Once it is on, the APs listen for BLE tags and show the locations of BLE clients and assets on Live View. The APs must already be placed on a floor plan, because the location is worked out against that map.
Reporting rates and performance
An AP that both transmits for engagement and listens for assets has more work to do. The documentation lists how often location data is sent to the cloud:
| Location service enabled | Data sent to the Mist cloud |
|---|---|
| vBLE Engagement and Asset Visibility | Every 2 seconds |
| Only vBLE Engagement | Every second |
| Only Asset Visibility | Every 2 seconds |
Juniper advises enabling only the features you need. If a site only tracks equipment, leave vBLE Engagement off so the APs spend their time listening for tags.
Seeing assets
| Where | What you see |
|---|---|
| Location > Live View | Assets and BLE clients placed on the floor plan of a site |
| BLE Clients page | The BLE devices heard by the APs, and the Add Asset button |
| Asset Insights | A Premium Analytics dashboard for asset data; needs SUB-AST |
Asset Insights classifies tags as active, inactive or non activated based on whether and when they were detected.
Asset filters
Many BLE devices already broadcast identifying data, such as a manufacturer value or an iBeacon UUID. An asset filter groups assets by that existing data, so you do not have to name each tag by hand. On the BLE Clients page, click Add Asset and select Asset Filter.
| Filter type | Matches |
|---|---|
| iBeacon | Proximity UUID, Major and Minor values |
| Eddystone UID | The Eddystone UID values a tag sends |
| Eddystone URL | The URL an Eddystone tag broadcasts |
| Eddystone TLM | Eddystone telemetry frames |
| Service UUID | The BLE service UUID the device advertises |
| MFG Data | Manufacturer specific data in the advertisement |
One asset filter can combine up to six filter types and values. For example, a hospital could match the iBeacon Proximity UUID used by all its tags plus a Major value that marks the radiology department.
Individual signals can also be named as assets. The asset visibility datasheet lists MAC address, Service UUID, iBeacon and Eddystone as the ways to identify an asset of significance.
An asset filter matches what the tag already broadcasts. If a question says the tags "come preconfigured with a manufacturer UUID", an asset filter on that value is the quickest way to group them.
Zones
Location zones are named areas drawn on the floor plan: Location > Live View, choose the site and floor plan, click Beacons and Zones, then Add Location Zone. Each zone needs a unique name.
Zones let you capture zone entry and exit events for client devices, assets and SDK clients through the API, and they feed occupancy and engagement analytics. A typical use is an alert when a tracked pump leaves the ward zone.
Getting the data out
| Method | Asset related option |
|---|---|
| WebSocket API | Discovery of BLE Assets by Map channel, BLE Asset RF Glass Info channel |
| Webhooks (site level) | asset-raw-rssi, location-asset, zone |
| REST API | Read asset and zone data, like every portal feature |
Subscription
Asset visibility needs the Asset Visibility (SUB-AST) subscription. SUB-AST is a site level subscription, and the number of subscriptions must match the number of APs in the site.
| Asset Visibility | |
|---|---|
| Subscription | SUB-AST |
| Signal direction | Tag transmits, AP listens |
| Enabled in | Site Configuration or device profile, Bluetooth based Location Services |
| Shown in | Location > Live View |
Asset visibility tracks tags, not people with the Mist app. If the scenario says visitors use a phone app for directions, that is vBLE engagement with SUB-ENG, not asset visibility.
Common mistakes
Installing extra BLE receivers. The APs listen for the tags themselves. No separate BLE scanner hardware is needed.
Buying vendor specific tags. Asset visibility works with standards based third party BLE tags such as iBeacon and Eddystone.
Forgetting the floor plan. Assets can only be shown on Live View when the APs are placed on a floor plan.
Enabling everything by habit. With both services on, data is reported every 2 seconds. Enable only what the site needs.
What to remember for the exam
- Asset visibility: BLE tags transmit, Mist APs listen, the cloud calculates location.
- Enable it under Organization > Site Configuration > Bluetooth based Location Services, or in a device profile.
- Assets appear on Location > Live View; the APs must be on a floor plan.
- Asset filters: iBeacon, Eddystone UID, URL and TLM, Service UUID, MFG Data; up to six per filter.
- Reporting: every 2 seconds with Asset Visibility on; every second with engagement only.
- Subscription: Asset Visibility (SUB-AST), site level, one per AP.
- Zones give entry and exit events for assets and clients.
Check yourself
A hospital wants to see where its wheelchairs are on the floor plan using third party BLE tags. Which feature and subscription does it need?
Asset visibility with the Asset Visibility (SUB-AST) subscription, enabled in the site's Bluetooth based Location Services settings.
How often is location data sent to the cloud when only Asset Visibility is enabled?
Every 2 seconds.
All of a customer's tags share one iBeacon Proximity UUID. How can the administrator group them as assets quickly?
Create an asset filter on the BLE Clients page that matches that iBeacon Proximity UUID.
Topic 1 of 2 in Location-based Services
Test yourself on Location-based Services
The full Juniper JNCIA-MistAI JN0-253 question bank has 668 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.