Aruba Central Source

Aruba Central Source connects to HPE Aruba Networking Central to sync floor-level WiFi occupancy counts and network device online/offline status into Mapped. The connector provisions floor occupancy zones, creates optional device inventory for selected access points, switches, and gateways, and refreshes both data streams every 5 minutes. Note this connector uses GreenLake / HPE SSO unlike the legacy version.
Use Cases
- Monitor floor occupancy trends using WiFi client counts
- Detect offline network devices that may impact building operations
- Combine occupancy and device health data in one graph for dashboards and workflows
Configuration
Auth Requirements
| Field | Required | Description | Where to Find |
|---|---|---|---|
| Base URL | Yes | Aruba Central cluster URL used for API calls | Aruba Central cluster/region for your tenant |
| Client ID | Yes | OAuth client credential ID | Aruba Central or HPE GreenLake API credential setup |
| Client Secret | Yes | OAuth client credential secret | Generated with the client ID |
The connector authenticates with OAuth2 client credentials against Aruba Central and stores the current access token automatically.
Place Mappings
The Place Mapping step loads sites, buildings, and floors from Aruba Central. Users confirm the hierarchy and add any missing business context before provisioning.
| Field | Required | Editable | Description |
|---|---|---|---|
| Building Name | Yes | No | Building name returned by Aruba Central |
| Building Address | Yes | Yes | Customer-supplied street address for the building |
| Building Ref ID | Yes | No | Aruba building ID used for device location matching |
| Aruba Site ID | Yes | No | Stored as building context and used for occupancy/device API filtering |
| Sub-building Name | No | Yes | Optional subdivision for wings or towers |
| Sub-building Code | No | Yes | Optional short code for the sub-building |
| Floor Name | Yes | Yes | Display name for the floor |
| Floor Level | Yes | Yes | Numeric floor level |
| Floor Ref ID | Yes | No | Aruba floor ID used by provisioning and polling |
Enumerations
After saving place mappings, the Device Status tab devices at the mapped Aruba sites. Users choose which rows to monitor for online/offline status. Each saved selection records the device serial number, device type, site, and any available building/floor location IDs.
Supported device categories are:
IAP— provisioned as a wireless access pointSWITCH— provisioned as an ethernet switchGATEWAY— provisioned as a generic networked device
Advanced Options
| Option | Default | Description |
|---|---|---|
| Poll Occupancy | TRUE | Enables or disables floor occupancy polling |
| Poll Device Status | TRUE | Enables or disables device status polling |
| Use Streaming API | FALSE | Takes floor occupancy from the Aruba Central Streaming API instead of polling, so the Streaming Occupancy Filters apply. Requires an Advance-tier Central subscription |
| Streaming Window Minutes | 5 | With streaming on, how long a client stays counted on a floor after Central last located it |
Streaming Occupancy Filters
Aruba Central locates every Wi-Fi device, including sensors, printers, signage and UPS cards, so a raw client count runs higher than the number of people on a floor. With Use Streaming API on, this step chooses which clients count. Each list offers the values Central reports at your mapped sites, with how many clients have each.
| Field | Default | Description |
|---|---|---|
| Clients to count | Connected to an AP | Counting every located client also counts phones probing with randomized addresses |
| Count only these device functions / operating systems / categories | Any | When set, a client counts only if Central's profile of it matches. Clients Central has not profiled are not counted |
| Never count these device functions / operating systems / categories | None | Clients matching any of these are never counted, e.g. Network Monitoring (UXI sensors) or Printer |
Streaming occupancy needs the API client to have access to Central's location and client monitoring data. If Central refuses the stream, the connector logs an error and writes no occupancy until it is fixed or streaming is turned off.
Mapped Concepts
API to Mapped Entities
This connector creates a place hierarchy from Aruba Sites/Buildings/Floors, adds one Occupancy Zone per mapped floor, and optionally provisions selected Aruba devices with a status point.
| Aruba concept | Mapped entity | exactType | Relationships |
|---|---|---|---|
| Building from site map | Building | Building | Parent place in the hierarchy |
| Optional sub-building | Building | Building | hasPart from building, isPartOf to building |
| Floor from site map | Floor | Floor | hasPart from building or sub-building |
| Virtual floor occupancy area | Zone | OccupancyZone | hasPart from floor |
| Selected access point | Thing | WirelessAccessPoint | hasLocation to floor or building |
| Selected switch | Thing | EthernetSwitch | hasLocation to floor or building |
| Selected gateway | Thing | NetworkedDevice | hasLocation to floor or building |
API to Mapped Points
| Aruba data | Point location | exactType | Datatype | Unit | Description |
|---|---|---|---|---|---|
| /network-services/v1/wifi-clients-locations total count | Floor occupancy zone | OccupancyCountSensor | INT | — | Current WiFi client count for the mapped floor |
| /network-monitoring/v1/clients failed-device result | Selected device | Point | INT | — | 1 when the device is not in the failed list, 0 when it is |
Occupancy and device status polls both run every 5 minutes when enabled. With Use Streaming API on, occupancy is instead the number of distinct clients passing the Streaming Occupancy Filters that Central located on the floor within the streaming window, written every minute.
Sample Code
Query Aruba Central devices
{
things(filter: { connectedDataSourceId: { eq: "your-connector-Id" } }) {
id
name
exactType
mappingKey
hasLocation {
... on Building {
id
name
exactType
}
... on Floor {
id
name
exactType
}
}
hasPoint {
id
name
exactType
mappingKey
}
}
}
Query Aruba Central Occupancy Zones
{
zones(filter: { connectedDataSourceId: { eq: "your-connector-Id" } }) {
id
name
exactType
mappingKey
hasPoint {
id
name
exactType
mappingKey
}
}
}
Query Time Series for On Off Status and Occupancy Count Sensors
{
points(filter:{connectedDataSourceId:{eq:"your-connector-Id"}}) {
id
name
exactType
mappingKey
isPointOf {
...on Zone {
id
name
exactType
mappingKey
}
...on Thing {
id
name
exactType
mappingKey
}
}
series(latest:true) {
timestamp
value {
int64Value
}
}
}
}
Graph Diagrams

Changelog
2026-11-17
- Added: Floor occupancy can come from the Aruba Central Streaming API (Advance-tier subscription), updated every minute.
- Added: With streaming on, Streaming Occupancy Filters choose which devices count toward occupancy by device function, operating system or category, so sensors, printers and other non-person devices can be left out.