Configuration

Configuration options for Haltian ENTRYWAY including entry direction, measurement intervals, and operational parameters

Configuration Overview

Haltian ENTRYWAY sensors are remotely configurable via Haltian IoT. This allows adjusting key parameters without physical access to the sensor.

Key configurable parameters:

  • Entry direction: Which side is “entry” vs. “exit”
  • Measurement interval: How often sensor reports during active period
  • Reporting interval (idle): How often sensor reports when no movement detected

Message Reference

For customers who operate their own gateways and cloud infrastructure, complete CBOR/JSON message documentation is available:

  • Uplink Messages — Messages the sensor transmits: people counting reports, battery level, diagnostics, system info
  • Downlink Messages — Configuration commands sent to the sensor: counting parameters, system settings, network roles

Entry Direction Configuration

What is Entry Direction?

Entry direction defines which side of the passageway represents “entry” vs. “exit”:

  • Entry: Person walking from one side → “entries” counter increments
  • Exit: Person walking from other side → “exits” counter increments

Direction determined by:

  • Order of PIR beam triggering (Beam 1 → 2 → 3 vs. 3 → 2 → 1)
  • Sensor orientation during installation

Default Direction

Standard installation (Haltian logo on left):

  • Entry direction: Towards sensor (person walks towards device face)
  • Exit direction: Away from sensor (person walks away from device face)

Example:

  • Sensor mounted on doorframe, logo on left
  • Person walks through doorway towards sensor face → Entry
  • Person walks through doorway away from sensor face → Exit

Custom Direction Configuration

When to configure custom direction:

  • Vertical wall installation (different orientation)
  • Traffic flow opposite to default
  • Specific business logic (e.g., “entry” from lobby to office, not vice versa)

How to configure:

  1. Install sensor in desired location
  2. Note sensor orientation (which direction should be “entry”)
  3. Contact Haltian support:
    • Email: support@haltian.com
    • Provide sensor ID and desired entry direction
    • Describe installation orientation (e.g., “logo on right”, “vertical on wall”)
  4. Haltian configures remotely via Haltian IoT
  5. Configuration typically applied within 1-24 hours
  6. Test with walkthrough to verify correct direction

Verifying Direction Configuration

After installation or configuration change:

  1. Entry test:

    • Walk through passageway in expected “entry” direction
    • Wait 30 seconds (default measurement interval)
    • Check IoT Studio: “entries” should increment, “exits” should not

  2. Exit test:

    • Walk through passageway in expected “exit” direction
    • Wait 30 seconds
    • Check IoT Studio: “exits” should increment, “entries” should not

  3. If incorrect:

    • Contact Haltian support to reverse direction
    • Provide sensor ID and describe issue (e.g., “entries and exits swapped”)
    • Haltian pushes corrected configuration remotely

Measurement Interval Configuration

What is Measurement Interval?

Measurement interval defines how often the sensor reports entry/exit counts during active period (after first detection):

  • 30 seconds (default): Sensor reports accumulated counts every 30 seconds
  • 10 seconds: Faster updates (low-latency mode, reduces battery life)
  • 60 seconds: Slower updates (battery optimization)

Default Setting

Standard configuration:

  • Measurement interval: 30 seconds
  • Rationale: Balance between timely data and battery life (4-year lifespan)

Reporting behavior:

  • First detection: Immediate report (within 1-5 minutes via mesh)
  • Subsequent detections: Every 30 seconds while activity continues
  • Idle period: Switches to idle reporting interval (default 1 hour)

Impact on Battery Life

Shorter measurement intervals increase battery consumption. At default 30s, expect ~4-year battery life. For detailed estimates by configuration, see Specifications — Battery Life Estimates.

When to Adjust Measurement Interval

Decrease interval (e.g., 30s → 10s):

  • Real-time occupancy monitoring (critical applications)
  • High-traffic areas (need frequent updates)
  • Integration with real-time dashboards (parking guidance, meeting room displays)
  • Trade-off: Reduced battery life (2-3 years vs. 4 years)

Increase interval (e.g., 30s → 60s):

  • Low-traffic areas (rarely used rooms, infrequent visitors)
  • Battery optimization priority (extend battery life to 5+ years)
  • Historical analytics only (no real-time need)
  • Trade-off: Delayed data (some brief activity may be aggregated)

How to Change Measurement Interval

Contact Haltian support:

  1. Email: support@haltian.com
  2. Provide:
    • Sensor ID(s)
    • Desired measurement interval (e.g., 10s, 60s)
    • Reason for change (helps Haltian optimize configuration)
  3. Haltian applies configuration remotely
  4. Configuration typically effective within 1-24 hours
  5. Verify new interval by observing report timestamps in IoT Studio

Reporting Interval (Idle) Configuration

What is Idle Reporting Interval?

Idle reporting interval defines how often the sensor transmits when no movement detected (idle period):

  • 1 hour (default): Sensor reports every hour even if no entries/exits
  • Configurable: 10 seconds to 24 hours

Purpose:

  • Confirms sensor operational (even when no traffic)
  • Provides battery level updates
  • Maintains network connectivity

Default Setting

Standard configuration:

  • Idle reporting interval: 1 hour
  • Report content: entries=0, exits=0, battery level, timestamp

Reporting behavior:

  • If no activity for 1 hour → Send “no activity” report
  • Ensures Haltian IoT Studio shows sensor online
  • Battery level monitored even in low-traffic areas

Impact on Battery Life

More frequent idle reports increase battery consumption. At default 1-hour, expect ~4-year battery life. For detailed estimates by configuration, see Specifications — Battery Life Estimates.

When to Adjust Idle Reporting Interval

Decrease interval (e.g., 1 hour → 10 minutes):

  • Critical monitoring (need to know sensor online frequently)
  • Network diagnostics (troubleshooting mesh connectivity)
  • Trade-off: Reduced battery life

Increase interval (e.g., 1 hour → 24 hours):

  • Low-traffic areas (sensor rarely active, idle reports not critical)
  • Battery optimization (extend battery life)
  • Trade-off: Less frequent confirmation of sensor health

How to Change Idle Reporting Interval

Contact Haltian support:

  1. Email: support@haltian.com
  2. Provide:
    • Sensor ID(s)
    • Desired idle reporting interval (e.g., 10 minutes, 24 hours)
    • Reason for change
  3. Haltian applies configuration remotely
  4. Verify by observing “Last Seen” timestamps in IoT Studio during idle periods

Operational Mode Presets

Standard Mode (Default)

Pre-configured settings:

  • Measurement interval: 30 seconds
  • Idle reporting interval: 1 hour
  • Entry direction: Default (towards sensor, logo on left)

Use cases:

  • Office entrances
  • Meeting room doorways
  • Retail spaces (moderate traffic)
  • Typical visitor counting applications

Optimized for:

  • 4-year battery life
  • Timely data (30-second updates during activity)

Low-Latency Mode (Custom)

Faster reporting settings:

  • Measurement interval: 10-20 seconds (faster updates)
  • Idle reporting interval: 10-30 minutes (more frequent health checks)

Use cases:

  • Real-time occupancy dashboards
  • Critical access point monitoring
  • Integration with real-time systems (parking guidance, room booking displays)

Trade-off:

  • Battery life: 2-3 years (vs. 4 years default)

Contact Haltian support to configure low-latency mode.

Low-Power Mode (Custom)

Extended battery life settings:

  • Measurement interval: 60 seconds (slower updates)
  • Idle reporting interval: 24 hours (minimal idle transmissions)

Use cases:

  • Low-traffic areas (rarely used rooms)
  • Historical analytics only (no real-time need)
  • Battery optimization priority (target 5+ year life)

Trade-off:

  • Data latency: Slower updates, some brief activity may be aggregated

Contact Haltian support to configure low-power mode.

Activation and Provisioning

Initial Sensor Activation

Before first use:

  1. Physical installation:

    • Mount sensor in desired location (see Installation guide)
    • Verify batteries installed (2× AA alkaline, pre-installed)

  2. Network join:

    • Sensor automatically joins Wirepas mesh network
    • Join time: 1-10 minutes (typical)
    • No manual activation required

  3. Verify in Haltian IoT Studio:

    • Log into IoT Studio portal
    • Navigate to device list
    • Confirm sensor appears with correct ID
    • Check “Last Seen” timestamp (should be recent)

  4. Configuration assignment:

    • Sensor ships with default configuration (standard mode)
    • If custom configuration needed, contact Haltian support
    • Configuration pushed remotely after network join

Sensor ID and Identification

Unique sensor ID:

  • Each ENTRYWAY has unique device ID (UUID, printed on label)
  • Use ID to identify sensor in IoT Studio
  • Reference ID when contacting support for configuration

Labeling best practice:

  • Note sensor ID during installation
  • Map ID to physical location (e.g., “Meeting Room A - Entrance”, “Lobby Main Door”)
  • Maintain installation records for future reference

Advanced Configuration Options

Mesh Network Role

Sensor can operate as:

  • End device: Only transmits own data (lowest power consumption)
  • Router: Relays packets for other sensors (higher power consumption, shorter battery life)

Automatic role assignment:

  • Wirepas mesh automatically assigns roles based on network topology
  • Sensors closer to gateway more likely to be routers
  • Optimal network topology managed automatically

Manual role configuration:

  • Typically not needed (auto-assignment optimal)
  • Contact Haltian support if specific topology required

Transmission Power

Radio transmission power:

  • Default: Optimized for balance of range and battery life
  • Adjustable: Can increase for challenging RF environments (reduces battery life)
  • Contact Haltian support for transmission power adjustments

When to increase transmission power:

  • Poor signal strength (RSSI < -85 dBm)
  • Long distance to gateway (> 20m, no intermediate routers)
  • RF-challenging environment (metal structures, underground)

Trade-off: Higher power = better connectivity but shorter battery life (3-4 years vs. 4+ years)

Configuration Change Process

Step-by-Step Configuration Update

How to request configuration change:

  1. Identify sensor:

    • Note sensor ID (from label or IoT Studio)
    • Confirm physical location
    • Determine current configuration (if known)

  2. Determine desired configuration:

    • Entry direction: Default or custom (describe orientation)
    • Measurement interval: 10s, 30s, 60s, or other
    • Idle reporting interval: 10 min, 1 hour, 24 hours, or other

  3. Contact Haltian support:

    • Email: support@haltian.com
    • Include:
      • Sensor ID(s)
      • Desired configuration parameters
      • Use case description (helps Haltian optimize)
      • Reason for change (if not obvious)

  4. Haltian applies configuration:

    • Configuration created in Haltian IoT
    • Pushed to sensor via Wirepas mesh network
    • Update typically applied within 1-24 hours

  5. Verify configuration:

    • Test sensor with walkthroughs (verify entry/exit direction)
    • Observe report timestamps (verify measurement/idle intervals)
    • Monitor for 24-48 hours to ensure stable operation
    • Report any issues to Haltian support

Configuration Rollback

If new configuration causes issues:

  • Contact Haltian support immediately
  • Describe problem (wrong direction, missed counts, etc.)
  • Haltian can revert to previous configuration remotely
  • Or adjust to alternative settings

Multi-Sensor Configuration Management

Configuring Multiple Sensors

For deployments with many sensors:

  1. Group by configuration type:

    • Group A: Office entrances → Standard mode (30s, 1hr)
    • Group B: Meeting rooms → Standard mode (30s, 1hr)
    • Group C: Main lobby → Low-latency mode (10s, 10min)

  2. Provide sensor IDs per group:

    • List all sensor IDs for Group A
    • List all sensor IDs for Group B
    • Etc.

  3. Submit single request to Haltian:

    • Configuration pushed to all sensors in each group
    • Reduces coordination overhead

Configuration Templates

Reusable configuration templates:

  • Define standard configurations for your organization
  • Apply same template to new sensors as deployed
  • Simplifies future installations

Example templates:

  • Standard Office: 30s measurement, 1hr idle
  • Real-Time: 10s measurement, 10min idle
  • Low-Power: 60s measurement, 24hr idle

Contact Haltian to establish configuration templates for your deployment.

Monitoring Configuration Effectiveness

Verification After Configuration

Key metrics to check in IoT Studio:

  1. Entry/exit accuracy:

    • Do “entries” align with people entering (in expected direction)?
    • Do “exits” align with people exiting?
    • Any direction confusion (entries/exits swapped)?

  2. Reporting frequency:

    • Check timestamps between reports during active period (should match measurement interval)
    • Check timestamps during idle period (should match idle interval)

  3. Signal strength (RSSI):

    • Maintained after configuration change?
    • If degraded, may need transmission power adjustment

  4. Battery consumption:

    • Monitor battery level trend over weeks
    • Excessive drain may indicate too-frequent measurements/transmissions

  5. Last seen timestamp:

    • Confirm sensor reporting as expected
    • Gap > 24 hours may indicate issue

Troubleshooting Configuration Issues

For detailed diagnosis and solutions for configuration-related problems (swapped direction, missed counts, battery drain, connectivity), see Troubleshooting.

Default Configuration Reference

Standard Mode Settings

ParameterValueRationale
Entry directionTowards sensor (logo on left)Default orientation
Measurement interval30 secondsBalance of timeliness and battery life
Idle reporting interval1 hourRegular health check, battery optimized
Expected battery life~4 yearsOptimized for typical usage

Configuration Best Practices

✅ Do:

  • Verify entry direction after installation (walkthrough test)
  • Document configuration per sensor (map ID to settings)
  • Monitor battery and counting accuracy after configuration changes
  • Use default settings unless specific need for customization

❌ Avoid:

  • Excessive measurement frequency (battery trade-off)
  • Configuring all sensors identically without considering individual locations
  • Frequent configuration changes (let sensor stabilize for 24-48 hours)

Support Resources

For configuration assistance:

  • Email: support@haltian.com
  • Configuration requests: Include sensor ID, desired settings, use case
  • Troubleshooting: Describe issue, provide sensor ID, current behavior vs expected

Response time:

  • Configuration requests: Typically applied within 1-24 hours
  • Support inquiries: Response within 1 business day