Managing Devices
Connect, configure, monitor, and report on TelemetryOS device fleets
Device Management
Device management encompasses onboarding, configuration, monitoring, and reporting capabilities for TelemetryOS device fleets. The device lifecycle flows through:
| Lifecycle Stage | Function | Documentation |
|---|---|---|
| Provisioning/Pairing | Account association | Connecting a Device |
| Content Assignment | Playlist/application deployment | Setting Content |
| Runtime Configuration | Settings and policies | Configuring a Device |
| Health Monitoring | Screenshots, logs, geographic visualization | Device Administration |
| Reporting | Data export for analysis | Device Reports |
For multi-device deployments, prefer provisioning over ad‑hoc pairing. Provisioning delivers a more resilient, repeatable onboarding flow for production fleets.
Key Workflows
Device management workflows address distinct operational requirements:
Connecting a Device - Device onboarding and account association
Configuring a Device - Defaults and operational controls
Device Administration - Fleet-scale management operations
Map - Geographic fleet visualization
Active Screenshots - Content playback verification
Device Reports - CSV and JSON data export for reporting and analysis
Deployment Pathways
Entry points vary by deployment context:
Testing and Small-Scale Scenarios
Pairing supports rapid device onboarding for pilot and proof-of-concept deployments requiring minimal configuration:
Characteristics: Pairing supports quick device-to-account association with pairing codes, minimal pre-configuration, and is best suited for small deployments (typically under 10 devices), though it requires manual configuration per device.
Production Deployments
Provisioning supports robust, repeatable onboarding for fleet-scale deployments:
Characteristics: Provisioning uses USB token-based zero-touch setup, applies organization/group defaults during initial activation, and scales to large fleets in the hundreds or thousands.
Production workflows benefit from establishing organization/group defaults before device enrollment, ensuring consistent configuration across fleet deployments.
Common Use Cases
Retail chains: Multi-location device deployment with location-based content and centralized management
Corporate offices: Campus-wide displays with department-specific content and scheduling
Transportation hubs: Real-time information displays with high-availability monitoring
Healthcare facilities: Patient information and wayfinding with compliance logging
Education campuses: Event displays and classroom signage with academic calendar integration
Hospitality venues: Menu boards and promotional displays with brand-consistent content
Device Management Specifications
Device management operations occur through TelemetryOS dashboard (Devices menu) and device-level interfaces (Interactive Menu, setup screens).
Core Operations
Core operations include device onboarding (pairing or provisioning), content assignment (playlists and applications), configuration management (display, network, schedule), health monitoring (online status, screenshots, logs), geographic visualization, and reporting.
Fleet Management Features
Fleet management adds grouping, bulk configuration updates, tag-based targeting, location-based filtering, status monitoring with alerts, and version management.
Limitations
Pairing does not scale well for large fleets because it requires manual code entry per device, config changes sync within roughly 30–60 seconds, and geographic visualization depends on complete location data entry. Screenshot capture is interval-based, reports export in CSV/JSON, and some operations still require devices to be online; account capacity also tracks subscription tier.
Updated about 1 month ago