Event Types

Cisco Spaces transmits data corresponding to various real-time events. On the Firehose API, data related to multiple technologies is sent on a single stream. It is recommended to choose only the desired events so that you can limit the amount of data streamed for your application.

Note: If you use custom events, log in to the Cisco Spaces Partner Dashboard to access and download documentation.

Quick Reference

Event Type Category Description
DEVICE_LOCATION_UPDATE Wi-Fi Device position update with coordinates
DEVICE_PRESENCE Wi-Fi Device lifecycle event (entry, active, inactive, exit)
USER_PRESENCE Wi-Fi User lifecycle event (aggregated across devices)
PROFILE_UPDATE Wi-Fi Device profile data changed
DEVICE_COUNT Wi-Fi Aggregated device count at a location (1-minute intervals)
DEVICE_ASSOCIATION Wi-Fi Device associated/disassociated with network
DEVICE_RSSI_UPDATE Wi-Fi Device RSSI measurement update
NETWORK_TELEMETRY Wi-Fi Network health and performance telemetry
NETWORK_STATUS_UPDATE Wi-Fi Connector/controller status change
WIFI_DEVICE_UPDATE Wi-Fi WiFi device update
IOT_TELEMETRY IoT IoT device telemetry (temperature, accelerometer, etc.)
IOT_USER_ACTION IoT IoT user action (button press, etc.)
BLE_RSSI_UPDATE IoT BLE device RSSI measurement
ASSET_LOCATION_UPDATE IoT Asset location update from asset locator devices (BLE/RFID/UWB/Wi-Fi)
CAMERA_COUNT Camera Aggregated people count via Meraki camera
RAW_CAMERA_COUNT Camera Individual camera count telemetry
LOCATION_CHANGE Location Location hierarchy changed
LOCATION_ANCHOR_UPDATE Location Location anchor added, updated, or removed
AP_TOPOLOGY_CHANGE Location Access point topology changed on floor
WEBEX_TELEMETRY Webex Webex device telemetry
SPACE_OCCUPANCY Occupancy Space occupancy state
SPACE_OCCUPANCY_CHANGE Occupancy Space occupancy changed
BUILDING_FEATURE Occupancy Space (feature) added, updated, or removed on a digital floor map
APP_ACTIVATION Activation Customer activated the application
KEEP_ALIVE System Heartbeat (every 15 seconds when idle)

Wi-Fi Events

Profile Update (PROFILE_UPDATE)

Sent when a device profile is updated or changed. For example, when an end-user provides information in a captive portal.

Device Location Update (DEVICE_LOCATION_UPDATE)

Sent when a device location is updated. Location update events continuously generate an approximate location of the device when connected to the network. The event includes X/Y coordinates, latitude/longitude, map ID, and confidence factor.

If your application requires zone, floor, or site-level presence data rather than precise coordinates, consider using DEVICE_PRESENCE or USER_PRESENCE instead.

You can choose to receive geo-coordinate data for Device Location Update events in the Cisco Spaces Partner Dashboard.

Device Presence (DEVICE_PRESENCE)

Tracks the lifecycle of a device at a location (site). Events are generated at various points:

  • Entry — Device first detected at the location
  • Active — Device becomes active after being inactive
  • Inactive — Device inactive for 10 minutes
  • Exit — Device determined to have exited

These events also provide the current count of active and inactive devices at the location.

User Presence (USER_PRESENCE)

Similar to Device Presence, but aggregated at the user level. Based on authentication and network information, Cisco Spaces can group multiple devices owned by a single user. Events are generated at the same lifecycle points as Device Presence.

Device Count (DEVICE_COUNT)

Sent when there is a change in the number of devices at a location. Includes associated count, probing count, and delta values. Generated at 1-minute intervals.

Device Association (DEVICE_ASSOCIATION)

Sent when a device associates with or disassociates from the network.

Device RSSI Update (DEVICE_RSSI_UPDATE)

Sent when a device RSSI measurement is updated.

Network Telemetry (NETWORK_TELEMETRY)

Sent at periodic intervals with health and performance telemetry for the location.

Network Status Update (NETWORK_STATUS_UPDATE)

Sent when a connector or controller status changes.

WiFi Device Update (WIFI_DEVICE_UPDATE)

Sent when WiFi device information is updated.

IoT Events

IoT Telemetry (IOT_TELEMETRY)

Sent when there are telemetry updates from BLE, RFID, and Zigbee IoT devices. Includes sensor data such as temperature, accelerometer readings, and battery status.

IoT User Action (IOT_USER_ACTION)

Sent when user actions are performed on IoT devices (e.g., button press).

BLE RSSI Update (BLE_RSSI_UPDATE)

Sent when there is a ping from a BLE device at the location.

Asset Location Update (ASSET_LOCATION_UPDATE)

Sent when an asset's location is updated by an asset locator device. Includes the asset metadata (assetInfo), the locator device that detected it (assetLocatorDeviceInfo — BLE, RFID, UWB, or Wi-Fi client), the detected position on the floor, the hierarchy location, and allComputedPositions.

Camera Events

Camera Count (CAMERA_COUNT)

Sent when there is a change in the aggregated count of people (computed via Meraki video cameras) at a location.

Raw Camera Count (RAW_CAMERA_COUNT)

Sent when there is a change in the individual camera count (per-camera telemetry from Meraki video cameras).

Location Hierarchy Events

Location Change (LOCATION_CHANGE)

Sent when a location is updated — for example, a location is moved under a group, renamed, or its metadata changes.

Location Anchor Update (LOCATION_ANCHOR_UPDATE)

Sent when a new location anchor is added to, updated in, or removed from IoT Services.

AP Topology Change (AP_TOPOLOGY_CHANGE)

Sent when the topology of an access point changes on a floor.

Webex Events

Webex Telemetry (WEBEX_TELEMETRY)

Sent with telemetry data from Webex devices.

Occupancy Events

Space Occupancy (SPACE_OCCUPANCY)

Sent with the current occupancy state of a space.

Space Occupancy Change (SPACE_OCCUPANCY_CHANGE)

Sent when the occupancy of a space changes.

Building Feature (BUILDING_FEATURE)

Sent when a space (feature) is added, updated, or removed on a digital floor map. Includes the space polygon, area, type, and associated floor location.

Activation Events

App Activation (APP_ACTIVATION)

Sent when a customer activates the application.

System Events

Keep-Alive (KEEP_ALIVE)

Sent every 15 seconds when no other events are available. Used to confirm the connection is healthy. See Connection Management for details.

Common Nested Objects

Events share these common nested structures:

Object Key Fields Description
device deviceId, macAddress, manufacturer, os, osVersion, type Device identification and metadata
location locationId, name, inferredLocationTypes, parent Location in the hierarchy
position xPos, yPos, latitude, longitude, confidenceFactor, mapId Coordinates on a floor map

Schema Discovery

The canonical schema for all event types is defined in the Protocol Buffer spec:

  1. Download the full spec: spaces_firehose_spec_v2.0.proto — defines every event type, field, and nested message
  2. Sample events: Review Sample Events — contains one example of every event type with all fields populated
  3. Live events: Connect to the streaming endpoint and observe real events for your activation
  4. Health endpoint: Use GET /api/partners/v1/firehose/health to inspect subscribed event types

JSON field names are the camelCase equivalent of proto snake_case names (e.g., record_uid → recordUid).