IoT Configuration Overview
Understand the IoT Configuration workspace, its systems of record, and its recommended workflow.
On this page
Purpose #
The IoT Configuration workspace manages the desired beacon and gateway state for a building-equivalent Cisco Spaces location. It combines AP and battery-beacon intent, local revision control, comparison with live Spaces data, and optional remediation through Cisco Spaces and Pointr.
Sources of state #
| System | Role |
|---|---|
| WaSense local intent | The desired, reviewable configuration managed by this portal. |
| Cisco Spaces | Observed IoT, AP, floor, and beacon state used for import, comparison, and remediation. |
| Pointr | Indoor-navigation floor mapping and draft beacon state used for comparison and synchronization. |
Publishing is local
Publishing a WaSense revision changes the local source of intent. External systems change only when a remediation or synchronization action is explicitly run.
Recommended workflow #
From observed state to verified intent
- Select a supported building-equivalent scope.
- Create intent by loading from Spaces, generating a managed set, or importing CSV.
- Review tenant defaults, AP rows, battery beacons, and floor assignments.
- Compare the working revision against current Cisco Spaces state.
- Publish the local draft when it represents the approved desired state.
- Preview and run only the required Cisco Spaces or Pointr remediation actions.