Juniper Mist
The Juniper Mist connector integrates with the Juniper Mist cloud platform to bring wireless network infrastructure data into the Mapped graph. It discovers wireless access points, switches, and gateways from Mist sites and maps them to buildings and floors, continuously polling device status and occupancy metrics. Each access point is paired with an occupancy zone that tracks the number of connected wireless clients, providing real-time space utilization data. Optionally, the connector supports webhook notifications for occupancy alerts.
Use Cases
Potential use cases include:
- Occupancy estimation via connected clients: Monitor how many wireless clients are connected to each access point as a proxy for occupancy, useful for space utilization analysis and capacity planning.
- Network infrastructure visibility: See all Mist wireless access points, switches, and gateways across your portfolio, organized by building and floor.
- Device health monitoring: Track online/offline status of network devices in real time to identify outages or connectivity issues.
Configuration
Auth Requirements
In order to authenticate, the following is required:
- Juniper Mist API Token: An API token with organization or site-level permissions needs to be created from the Juniper Mist Portal. Juniper Mist: Create API Tokens
- Mist Region: Select the cloud region where your Mist organization is hosted (Global, Europe, APAC, or US Government).
- Organization ID: Your Mist organization UUID, found in the Mist dashboard under Organization > Settings.
- Webhook Secret (optional): A shared secret for validating webhook signatures, only needed if webhooks are enabled. Add a Webhook in the Juniper Mist Portal
Entity Import
The connector lists every access point, switch, and gateway in the Mist sites your API token can access on the Devices tab. Each row is one Mist device. Choose its Location, then select the rows and save to add the devices to Mapped.
| Column | Required | Description |
|---|---|---|
| Name | Yes | Device name in Mapped. Defaults to Access Point, Switch, or Gateway followed by the Mist device name. |
| Location | Yes | The Building, Sub-building, Floor, or Space the device is in. Access points are usually placed on a Floor; switches and gateways in a Building or Sub-building. |
| Context | – | Read-only Mist details you can filter on or use in mapping rules: device type, Mist site name, Mist floor plan (map) name, serial number, MAC address, and model. |
Notes:
- Access points and switches need a serial number in Mist to be added.
- Changing a device's Location and saving moves it (and an access point's occupancy zone) to the new place.
- If the device list can't be read completely from Mist (for example, a site the token can't access, or Mist rate limits), the tab shows the error and keeps the saved devices unchanged.
- A device removed from Mist stops reporting. Its row leaves the tab when you save; its history stays in Mapped.
Connectors set up before the Devices tab use the Location Mapping tab until they are migrated. To migrate, use Entities Migration: every mapped device keeps its Mapped ID, location, and point history.
Advanced Options
- Enable Webhooks: Enable real-time webhook notifications from Mist. When enabled, the connector registers a webhook with Mist for occupancy alert events. The default is disabled.
Mapped Concepts
Mist API to Mapped Entities
| Mist API Model | Mapped Entity | exactType | Description |
|---|---|---|---|
| Access Point | Occupancy Zone | Occupancy Zone | An occupancy zone is created for each access point and attached to the floor. The AP serves this zone. |
| Device (type: ap) | WirelessAccessPoint | WirelessAccessPoint | Mist wireless access points, linked to their assigned floor. |
| Device (type: switch) | Switch | Switch | Mist network switches, linked to their building or sub-building. |
| Device (type: gateway) | NetworkedDevice | NetworkedDevice | Mist gateways, linked to their building or sub-building. |
| Relationships: |
- Each device has an ExternalIdentity using the device serial number scoped to the organization. Read more on Identities at Mapped.
- Access points are located on floors (Floor → isLocationOf → WirelessAccessPoint).
- Each access point has an associated OccupancyZone attached to its floor (Floor → hasPart → OccupancyZone).
- Access points serve their occupancy zone (WirelessAccessPoint → serves → OccupancyZone).
- Switches and gateways are located in buildings or sub-buildings (Building/SubBuilding → isLocationOf → Switch/NetworkedDevice).
Mist API to Mapped Points
| Mist Data | Mapped Point | exactType | ParentEntity | Datatype | Unit | Description |
|---|---|---|---|---|---|---|
| AP device status | OnOffStatus | OnOffStatus | WirelessAccessPoint | ENUM | NUM | Access point online/offline status. Values: 0 = disconnected, 1 = connected. |
| AP connected clients | ConnectedDevicesCountSensor | ConnectedDevicesCountSensor | OccupancyZone | INT | NUM | Count of wireless clients currently connected to the access point. Represents actual occupants (people with devices) in the AP's coverage area. |
| Switch device status | OnOffStatus | OnOffStatus | Switch | JSON | — | Switch status as a JSON object containing the status field. |
| Gateway device status | OnOffStatus | OnOffStatus | NetworkedDevice | JSON | — | Gateway status as a JSON object containing the status field. |
| Notes: |
- Access point status uses a numeric value map: 0 → "disconnected", 1 → "connected".
- The ConnectedDevicesCountSensor is attached to the OccupancyZone (not directly on the Access Point). It reflects the
num_clientsmetric from the Mist API — the number of wireless clients actively associated with the AP. - Switch and gateway status is reported as a JSON payload (e.g.,
{"status": "connected"}). - Data is polled every 5 minutes.
Sample Code
Query latest device status for access points:
Note you'll need the connectorId of your Juniper Mist connector to execute this query. You can find this in the Mapped Console grid view under the Connectors tab.
{
points(
filter: {exactType: {eq: "On_Off_Status"},
and: {connectedDataSourceId: {eq: "your-connector-Id"}}}
) {
id
name
datatype
valueMap
series(latest: true) {
timestamp
value {
int64Value
}
}
}
}
Query connected client counts over a time range:
{
points(filter: { exactType: { eq: "Connected_Devices_Count_Sensor" },
and:{connectedDataSourceId: { eq: "your-connector-Id" } }}
) {
id
name
series(
startTime: "2026-05-01T12:00:00Z"
endTime: "2026-05-02T13:00:00Z"
) {
timestamp
value {
int64Value
}
}
}
}
Graph Diagrams
Access Points with Occupancy Zones (linked to Floors)

Switches & Gateways (linked to Buildings)

Switches & Gateways with Sub-Buildings

Changelog
2026-11-12
- Changed: Devices are now chosen and placed on a new Devices tab instead of the Location Mapping table. Each device has a Location (Building, Sub-building, Floor, or Space); changing it and saving moves the device.
- Fixed: Loading the device list no longer makes about one Mist call per device, which could time out on large organizations and show every mapped device as unavailable. If Mist can't be read completely, the Devices tab shows the error and keeps the saved devices.
- Fixed: Sites with more than 100 devices are now listed in full.
- Fixed: Switches and gateways now report their status. The status poll requested access points only.
- Added: Entities Migration for connectors that use the Location Mapping table. Mapped devices keep their Mapped IDs, locations, and point history.