Skip to main content

Devices & Criticality Tiers

Every IoT device connected to SpaceOS is classified by a criticality tier that determines how failures affect booking access.

Criticality Tiers​

TierExamplesFailure Impact
CRITICALDoor locks, access controllersBooking access may fail. System retries with configurable grace period. Alerts triggered immediately.
STANDARDWi-Fi hotspots, network switchesBooking proceeds. User notified of degraded service. Background retry.
OPTIONALAmbient lighting, fans, displaysSilently degraded. No user notification. Logged for operator review.

Device Types​

SpaceOS supports these device types through the adapter protocol:

  • lock — Door locks and access controllers
  • wifi — Wi-Fi access points and hotspot management
  • fan — Climate control devices
  • light — Lighting systems
  • display — Meeting room status displays
  • camera — Security cameras
  • sensor — Occupancy and environmental sensors

Device Health Monitoring​

ZenEdge continuously monitors device health through:

  1. Periodic polling — /ping endpoint called at configured intervals
  2. Health status tracking — Last ping time, failure count, response latency
  3. Alert escalation — Based on criticality tier and failure count
  4. Admin dashboard — Real-time device health view with status badges

Booking Access Retry Policy​

When a CRITICAL device fails during booking access:

  1. First attempt at T-15 minutes before booking start
  2. Retry at T-0 (booking start time)
  3. Configurable per-space retry policy (org default with per-space override)
  4. Organizer notified of access issues

Next Steps​