Third-party access points
Use the wireless access points you already run as hotspots. If your building has Juniper Mist or Cisco access points with Bluetooth scanning, an integration brings their tag detections into Blecon. You install no extra hardware.
Supported platforms
| Platform | Who calculates the tag position | What you set up in Blecon |
|---|---|---|
| Juniper Mist | The Blecon positioning engine, from the access point positions on your Mist floor plans | A Mist API token. Blecon configures the webhooks and imports the access point positions. |
| Cisco Spaces | Cisco Spaces, from the access point placements on your Cisco floor plans | Permission to read the Cisco Spaces locations that you select. There is no access point setup in Blecon. |
How they differ from hubs
A third-party access point relays tag detections like any other hotspot. Three things are different:
- You manage the access points in their own platform. Placement, firmware and Bluetooth scan settings stay in Juniper Mist or Cisco Spaces.
- Location comes from your floor plans. You do not register or place the access points in Blecon. Keep the floor plans accurate and geo-referenced, because tag positions depend on them.
- Only registered tags are processed. The integration ignores detections of tags that are not registered on your network.
When to use them
- Your buildings already have enterprise Wi-Fi from one of these vendors.
- You want fixed indoor coverage without installing hubs.
- You want to add coverage to the Blecon Agent on the devices your team carries.