Event Types

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

Most of these events can be grouped together based on similar technologies as listed below:

Note

If you use custom events, please login to Cisco DNA Spaces Partners Dashboard to access and download documentation.

  • WiFi events

    • Device Entry: This event is sent when a device enters a location.

    • Device Exit: This event is sent when a device has exited a location.

    • Profile Update: This event is sent when a device profile is updated or changed. For example, this event is sent when an end-user provides information in a captive portal.

    • Device Location Update: This event is sent when a device location is updated.

      Location update events continuously generate an approximate location of the device when connected to the network. The app requires X,Y, and/or the latitude, and longitude level location data and a map of your location. If the Device Location Update event is selected in the Event Types section, then one of the following events is selected. The app requires zone, floor, or site level presence data. These events include Location Updates and Device Entry, Device Exit, and Device Dwell data for the devices connected to your network. These events are generated every time a device enters or exits a building, a floor, or a zone. The information available in Cisco DNA Spaces about these devices and a high level information about their location is also shared. You can choose to receive Geo coordinates data for the Device Location Update event.

      If the Device Location Update event is not selected, then either Device Entry, or Device Entry, or Device Exit, or Device Presence, or the User Presence event is selected in Event Types section.

    • Device Presence: This event is used to track the life cycle of a device at a location. Events are generated at various points such as at device entry, when a device is inactive for 10 minutes, when a device is active after being inactive, or when we determine the device has exited. These events also provide the current count of active and inactive devices at location.

    • User Presence: Based on the available authentication in use and the information available from the network, Cisco DNA Spaces can map group or multiple devices owned by a user. Events are generated at various points such as at device entry, when a device is inactive for 10 minutes, when a device is active after being inactive, or when we determine the device has exited. These events also provide the current count of active and inactive devices at location.

    • Device Count: This event is sent when there is a change in the (count) number of devices at the location.

    • Network Telemetry: This event is sent at a periodical interval with health and performance telemetries of the location.

    • Device RSSI Update: This event is sent when a device RSSI is updated.

  • IoT events

    • IoT Telemetry: This event is sent when there are telemetry updates from BLE, RFID, and Zigbee IoT devices.

    • IoT User Action: This event is sent when user actions are performed on IoT devices.

    • BLE RSSI Update: This event is sent when there is a ping from the BLE device at the location.

  • Camera events

    • Camera Count: This event is sent when there is a change in the aggregated count of people (computed via the Meraki Video Camera) at the location.

    • Raw Camera Count: This event is sent when there is a change in the individual camera count (computed via the Meraki Video Camera) at the location.

  • Location hierarcy events

    • Location Information Change: This event is sent when a location is updated. For example, a location is moved under a group, location is renamed or there is a change to location’s meta data.

    • Location Anchor Update: This event is sent when a new location anchor is added to, updated in, or removed from IoT Services.

    • AP Topology Change: This event is sent when topology of an AP gets changed on the floor.

  • Activation events

    • App Activation: This event is sent when a customer activates the application.

Events that do not belong to the above categories are listed below:

  • Keep Alive: This event is sent when there is no other event sent for a period of 15 seconds. This event is applicable only for HTTP/gRPC channels to prevent your connection from timing out.

  • Tele Presence: This event is sent when the Tele Presence system encounters a people-count update. If you choose the Tele Presence option, then the app requires data generated by the Tele Presence units. This includes the presence event and the people count event. Presence is provided by devices connected to the Telepresence unit via ultrasound. People count is provided by computer vision from the Telepresence video camera. Cisco DNA Spaces does not receive any video or photographs data. Cisco DNA Spaces receives the final count of people recognized and all video stays on the Tele Presence unit.

  • Account Admin Change: This event is sent when an account admin gets added/removed/updated for the partner account.

  • Network Status Update: This event is sent to represent the status of the connector and controller.