Configuration
Overview
Thingsee AIR sensors come preconfigured from the factory with optimal default settings for most applications. However, specific parameters can be adjusted remotely via Haltian IoT Studio to fine-tune sensor behavior for your environment.
Default Configuration
Factory Settings
Out-of-the-box, Thingsee AIR is configured with:
| Parameter | Default Value | Purpose |
|---|---|---|
| Measurement interval | Continuous | Constant monitoring |
| Event reporting threshold (CO₂) | 10 ppm | Sensitive change detection |
| Event reporting threshold (TVOC) | 30 ppb | Moderate sensitivity |
| Event reporting threshold (Temperature) | 0.5°C | Typical room changes |
| Event reporting threshold (Humidity) | 2% RH | Standard comfort monitoring |
| Event reporting threshold (Pressure) | 20 hPa | Weather/HVAC changes |
| Minimum report interval | 5 minutes | Event-based |
| Maximum report interval | 1 hour | Heartbeat |
| Battery report interval | 6 hours | Status monitoring |
Standard Operating Mode
The default configuration suits most applications:
- Office environments - Standard sensitivity for comfort monitoring
- Educational facilities - Balanced between responsiveness and data volume
- Healthcare - Suitable for general patient areas
- Retail spaces - Adequate for customer comfort tracking
Configurable Parameters
Reporting Thresholds
CO₂ Event Threshold
Default: 10 ppm
Range: 5-100 ppm
Recommended adjustments:
| Environment | Suggested Threshold | Rationale |
|---|---|---|
| High-precision monitoring | 5 ppm | Maximum sensitivity for research/critical areas |
| Standard office | 10 ppm (default) | Balance between data and responsiveness |
| Low-traffic areas | 25-50 ppm | Reduce data volume in stable environments |
| Storage/utility spaces | 50-100 ppm | Minimal reporting for non-occupied areas |
Impact:
- Lower threshold → More frequent reports, higher data volume, shorter battery life
- Higher threshold → Fewer reports, lower data volume, longer battery life
TVOC Event Threshold
Default: 30 ppb
Range: 10-500 ppb
Recommended adjustments:
| Application | Suggested Threshold | Rationale |
|---|---|---|
| Clean rooms | 10-20 ppb | Detect minute contamination |
| Standard office | 30 ppb (default) | Normal air quality monitoring |
| Industrial areas | 100-200 ppb | Focus on significant events |
| Low-priority spaces | 200-500 ppb | Minimal monitoring |
Considerations:
- TVOC sources can cause rapid spikes
- Lower thresholds may generate excessive alerts
- Higher thresholds may miss gradual accumulation
Temperature Event Threshold
Default: 0.5°C
Range: 0.1-5.0°C
Recommended adjustments:
| Use Case | Suggested Threshold | Purpose |
|---|---|---|
| Precision control | 0.1-0.2°C | Laboratory/medical applications |
| Comfort monitoring | 0.5°C (default) | Standard HVAC verification |
| Energy optimization | 1.0-2.0°C | Focus on significant changes |
| Storage areas | 2.0-5.0°C | Alert only on major deviations |
Humidity Event Threshold
Default: 2% RH
Range: 1-10% RH
Recommended adjustments:
| Environment | Suggested Threshold | Rationale |
|---|---|---|
| Critical humidity control | 1% RH | Museums, archives, clean rooms |
| Standard comfort | 2% RH (default) | Normal office/retail |
| General monitoring | 5% RH | Reduced reporting frequency |
| Non-critical areas | 10% RH | Alert only on major changes |
Mold prevention:
- Monitor for sustained levels > 60% RH
- Consider lower threshold (1-2% RH) in areas at risk
Barometric Pressure Event Threshold
Default: 20 hPa
Range: 1-100 hPa
Typical use:
- 1-5 hPa: Weather pattern tracking
- 10-20 hPa (default): HVAC pressure monitoring
- 50-100 hPa: Significant system events only
Reporting Intervals
Minimum Event Report Interval
Default: 5 minutes
Range: 1-60 minutes
Purpose: Prevents data flooding from rapid fluctuations
Adjustments:
- 1-2 minutes: High-frequency critical monitoring
- 5 minutes (default): Standard responsiveness
- 10-15 minutes: Reduce data volume
- 30-60 minutes: Minimal data needs
Trade-offs:
- Shorter intervals → Real-time responsiveness, higher battery drain
- Longer intervals → Delayed detection, extended battery life
Maximum Report Interval (Heartbeat)
Default: 1 hour
Range: 15 minutes - 24 hours
Purpose: Ensures regular data flow even in stable conditions
Recommendations:
- 15-30 minutes: Critical monitoring requiring frequent status
- 1 hour (default): Standard operational visibility
- 2-4 hours: Low-priority monitoring
- 6-24 hours: Battery optimization for stable environments
Note: Longer heartbeat intervals extend battery life significantly in stable environments.
Battery Status Report Interval
Default: 6 hours
Range: 1-24 hours
Purpose: Monitor battery health without excessive reporting
Typical settings:
- 1-2 hours: Critical installations requiring constant status
- 6 hours (default): Standard monitoring
- 12-24 hours: Battery life optimization
Configuration Methods
Via Haltian IoT Studio
Standard configuration interface for Haltian-managed deployments:
- Access IoT Studio: Log in at https://iot.haltian.com
- Navigate to device: Select your Thingsee AIR sensor
- Configuration tab: Access device settings
- Modify parameters: Adjust values as needed
- Apply changes: Send configuration to device
Delivery time:
- Configuration sent as downlink message
- Delivered on next sensor uplink (typically < 5 minutes)
- Confirmation message upon successful application
Via Haltian Operations Cloud API
For programmatic or bulk configuration:
- API endpoint: Contact Haltian support for API access
- Authentication: API keys provided per customer
- Bulk operations: Configure multiple devices simultaneously
- Automation: Integrate with your management systems
Via Haltian Support
For complex or custom configurations:
Contact: support@haltian.com
Request information:
- Device IDs to configure
- Parameters to modify
- Target values
- Deployment timeline
Support can configure:
- Custom threshold combinations
- Advanced reporting logic
- Special operational modes
- Bulk fleet updates
Configuration Best Practices
Planning Configuration Changes
Assess Current Performance
Before modifying settings:
- Review 1-2 weeks of historical data
- Identify actual data patterns
- Determine if changes are needed
- Document rationale for modifications
Start Conservative
- Make small adjustments initially
- Monitor impact for several days
- Fine-tune based on observed behavior
- Avoid extreme values without specific requirements
Testing Configuration Changes
Pilot Deployment
For large installations:
- Select test sensors: 2-5 representative locations
- Apply new configuration: Limited scope initially
- Monitor for 1 week: Assess data quality and volume
- Evaluate results: Battery impact, alert frequency, data usefulness
- Roll out: Apply to full fleet if successful
Monitor After Changes
Track these metrics post-configuration:
- Data volume: Messages per day per sensor
- Battery consumption: Estimated life based on new settings
- Alert frequency: Are alerts meaningful or excessive?
- Data gaps: Any missing data due to long intervals?
Environment-Specific Recommendations
High-Occupancy Offices
- CO₂ threshold: 10 ppm (default) or 5 ppm for precision
- TVOC threshold: 30 ppb (default)
- Temperature threshold: 0.5°C (default)
- Minimum interval: 5 minutes (default)
- Heartbeat: 1 hour (default)
Educational Facilities
- CO₂ threshold: 10 ppm (classroom air quality critical)
- TVOC threshold: 20-30 ppb (sensitive to cleaning products)
- Temperature threshold: 0.5°C
- Minimum interval: 5 minutes
- Heartbeat: 30 minutes (more frequent during school hours)
Healthcare Environments
- CO₂ threshold: 10 ppm
- TVOC threshold: 20 ppb (detect contamination early)
- Temperature threshold: 0.2-0.5°C (patient comfort critical)
- Humidity threshold: 1-2% RH (infection control)
- Minimum interval: 5 minutes
- Heartbeat: 30 minutes
Retail Spaces
- CO₂ threshold: 15-25 ppm (customer comfort focus)
- TVOC threshold: 30-50 ppb
- Temperature threshold: 0.5-1.0°C
- Minimum interval: 10 minutes
- Heartbeat: 1 hour
Storage/Utility Areas
- CO₂ threshold: 50-100 ppm (minimal monitoring)
- TVOC threshold: 100-200 ppb
- Temperature threshold: 2-5°C (detect failures only)
- Humidity threshold: 5-10% RH
- Minimum interval: 15-30 minutes
- Heartbeat: 4-6 hours (battery optimization)
Battery Life Optimization Through Configuration
Impact of Configuration on Battery Life
Reporting frequency is the primary factor affecting battery life:
| Configuration Profile | Messages/Day | Expected Battery Life |
|---|---|---|
| High-frequency monitoring | 200-300 | 2-3 years |
| Standard (default) | 50-100 | 4 years |
| Optimized intervals | 20-40 | 5-6 years |
| Minimal monitoring | 10-20 | 6+ years |
Battery Optimization Strategies
For Stable Environments
If data shows minimal variation:
- Increase event thresholds
- Extend minimum report interval to 10-15 minutes
- Increase heartbeat to 2-4 hours
- Result: 5-6 year battery life
For Variable Environments
If frequent changes are expected:
- Keep default thresholds
- Maintain 5-minute minimum interval
- Standard 1-hour heartbeat
- Result: Standard 4-year battery life
For Critical Monitoring
When maximum responsiveness needed:
- Reduce thresholds (high sensitivity)
- 1-2 minute minimum interval
- 15-30 minute heartbeat
- Result: 2-3 year battery life (plan more frequent replacements)
Advanced Configuration Options
Custom Operational Modes
Contact Haltian support for:
- Scheduled reporting: Different thresholds for occupied vs. unoccupied hours
- Conditional logic: Combined parameter triggers (e.g., report when CO₂ > 1000 AND temperature > 25°C)
- Adaptive thresholds: Auto-adjust based on learned patterns
- Multi-zone coordination: Configure groups with synchronized settings
Integration-Specific Configuration
For specific third-party integrations:
- Data format adjustments: Custom payload formatting
- Report filtering: Send only specific parameters to certain endpoints
- Aggregation: Send averaged values instead of raw measurements
Configuration Change Log
Tracking Configuration History
Maintain a log of configuration changes:
- Date/time of change
- Parameters modified and values
- Reason for change
- Applied to which sensors
- Result of change (successful/issues)
Benefits:
- Troubleshooting performance issues
- Documenting optimization efforts
- Training new team members
- Regulatory compliance (if required)
Support
For configuration assistance:
- Email: support@haltian.com
- Documentation: Operation Guide for monitoring
- Technical Support: Custom configuration requirements
- API Access: Contact support for programmatic configuration
Related Documentation
- Operation Guide - Understanding sensor data and monitoring
- Specifications - Technical parameter ranges
- Troubleshooting - Configuration-related issues
- Installation Guide - Initial setup and deployment