Troubleshooting

Common issues and solutions for Haltian RADAR sensor

Troubleshooting Overview

This guide addresses common issues with Haltian RADAR sensors and provides step-by-step solutions.

Quick troubleshooting approach:

  1. Identify the problem (symptoms)
  2. Check common causes (this guide)
  3. Verify configuration (IoT Studio)
  4. Contact support if unresolved

Detection Issues

Sensor Reports “Occupied” When Space is Empty (False Positive)

Symptoms:

  • Parking space or loading dock is empty
  • Sensor reports “occupied” in IoT Studio
  • Persistent or intermittent false positive

Common causes:

1. Sensing Distance Too Long

Problem: Sensor detecting objects beyond intended monitoring zone (e.g., vehicles in adjacent parking space, pedestrians, walls)

Solution:

  1. Review current sensing distance in IoT Studio (or contact support to check)
  2. Measure actual distance from sensor to monitored area boundary
  3. Request reduced sensing distance via Haltian support
    • Example: If adjacent space 6m away, reduce from 5m → 4m
  4. Test after configuration change

Expected outcome: False positives eliminated by limiting detection range to intended zone

2. Obstructions Causing Reflections

Problem: Radar beam reflecting off nearby objects (walls, poles, equipment) creating false detections

Solution:

  1. Inspect area within 17° detection cone from sensor
  2. Identify reflective surfaces (metal walls, poles, signage)
  3. Option A: Relocate sensor to avoid reflections
  4. Option B: Reduce sensing distance to exclude reflective object
  5. Option C: Remove/relocate reflective object (if possible)

Expected outcome: Clear line of sight eliminates false reflections

3. Sensor Angle Too Steep

Problem: Sensor angled beyond 45° from perpendicular, causing beam to spread or reflect unexpectedly

Solution:

  1. Check sensor mounting angle
  2. Verify sensor face as close to perpendicular (90°) to monitored area as possible
  3. If angle > 45°, physically reposition sensor
  4. Ideal: 0-30° from perpendicular

Expected outcome: Proper angle focuses beam on intended area

4. Environmental Interference (Rare)

Problem: Other 60GHz devices or extreme RF noise (very rare)

Solution:

  1. Check for other 60GHz radar devices nearby (unlikely in most environments)
  2. Temporarily power off nearby electronics to test
  3. Contact Haltian support if interference suspected

Expected outcome: Interference is rare; if confirmed, sensor relocation may be needed

Sensor Reports “Unoccupied” When Vehicle Present (Missed Detection)

Symptoms:

  • Vehicle parked in space or trailer at loading dock
  • Sensor reports “unoccupied” in IoT Studio
  • Detection failure (vehicle not detected)

Common causes:

1. Sensing Distance Too Short

Problem: Sensor range doesn’t reach vehicle detection point

Solution:

  1. Measure actual distance from sensor to vehicle (when parked/docked)
  2. Compare to configured sensing distance
  3. Request increased sensing distance via Haltian support
    • Example: If vehicle 3m away but distance set to 2m, increase to 3.5m
  4. Test with vehicle in position

Expected outcome: Extended range detects vehicle reliably

2. Obstruction in Beam Path

Problem: Object blocking 17° radar cone (post, sign, equipment, etc.)

Solution:

  1. Inspect clear line of sight from sensor to monitored area
  2. Identify any obstructions within 17° cone
  3. Option A: Remove obstruction (if possible)
  4. Option B: Relocate sensor to clear position
  5. Verify clear path after adjustment

Expected outcome: Clear line of sight enables reliable detection

3. Radar-Absorptive Vehicle Materials (Rare)

Problem: Vehicle materials absorb 60GHz radar (very rare - most vehicles are metal and highly reflective)

Solution:

  1. Test with different vehicles (cars, SUVs, trucks)
  2. If specific vehicle not detected but others are, may be material issue
  3. Contact Haltian support with vehicle type/model details
  4. Possible solutions: Reduce sensing distance (requires stronger reflection at closer range)

Expected outcome: Most vehicles are radar-reflective; material absorption is extremely rare

4. Sensor Mounting Height or Angle Wrong

Problem: Sensor aimed above or below vehicle, missing target

Solution:

  1. Parking spaces: Verify mounting height 40-60 cm (knee height)
  2. Loading docks: Verify sensor aimed at trailer position (1-3m height typical)
  3. Check sensor angle - beam should point at vehicle detection zone
  4. Adjust mounting height or angle if needed
  5. Test with vehicle present

Expected outcome: Proper height and angle ensure beam intersects vehicle

Intermittent Detection (Sometimes Works, Sometimes Doesn’t)

Symptoms:

  • Detection unreliable (works for some vehicles, not others)
  • Sporadic false positives or missed detections
  • Inconsistent behavior over time

Common causes:

1. Vehicle Size Variation

Problem: Small cars detected, large SUVs missed (or vice versa) due to fixed sensing distance

Solution:

  1. Identify range of vehicle sizes using space (compact cars → SUVs)
  2. Set sensing distance to cover full vehicle range
    • Example: If cars 1.5m - 3m from sensor, set distance to 3m
  3. Test with smallest and largest vehicles
  4. Adjust if needed

Expected outcome: Single sensing distance covers all vehicle types

2. Environmental Conditions (Temperature, Humidity)

Problem: While RADAR is generally stable, extreme conditions may affect performance

Solution:

  1. Check environmental conditions during failures (temperature, heavy rain, etc.)
  2. RADAR should work -35°C to +85°C and in rain/snow (IP68)
  3. If performance degrades in specific conditions, document and report to Haltian support
  4. Possible solutions: Sensor relocation, configuration adjustment

Expected outcome: RADAR designed for extreme environments; issues rare but reportable

3. Measurement Interval Too Long

Problem: Vehicle parks briefly and leaves before next measurement (missed)

Solution:

  1. Review measurement interval (30s parking default, 60s loading dock default)
  2. For high-turnover areas, shorter interval may help (trade-off: battery life)
  3. Request measurement interval reduction via Haltian support (e.g., 60s → 30s)

Expected outcome: More frequent measurements catch brief occupancies (but reduce battery life)

Connectivity Issues

Sensor Not Appearing in IoT Studio

Symptoms:

  • Sensor installed and powered
  • Does not appear in IoT Studio device list
  • “Last Seen” timestamp never updates

Common causes:

1. Sensor Not Yet Joined Wirepas Network

Problem: Network join process can take 1-10 minutes (or longer in outdoor/sparse mesh environments)

Solution:

  1. Wait 10-15 minutes after installation
  2. Refresh IoT Studio device list
  3. If still not appearing after 30 minutes, proceed to next troubleshooting step

Expected outcome: Sensor appears in device list within 30 minutes

2. Out of Range from Gateway or Mesh Network

Problem: Sensor > 20m from gateway with no intermediate routers

Solution:

  1. Measure distance from sensor to nearest gateway or router sensor
  2. If > 20m, mesh network cannot reach sensor
  3. Option A: Add intermediate sensor(s) as routers (< 20m spacing)
  4. Option B: Relocate gateway closer to sensor
  5. Option C: Relocate sensor closer to network

Expected outcome: Sensor within 20m of mesh network, joins successfully

3. Gateway Offline or Not Configured

Problem: Thingsee Gateway not operational

Solution:

  1. Verify gateway powered and connected to internet
  2. Check gateway status in IoT Studio (should show “online”)
  3. If gateway offline, troubleshoot gateway (refer to gateway documentation)
  4. Restart gateway if needed
  5. After gateway online, sensor should join within 10 minutes

Expected outcome: Gateway online, sensor joins mesh network

4. Sensor Hardware Failure (Rare)

Problem: Sensor defective (rare - quality control high)

Solution:

  1. If all other troubleshooting steps fail, hardware failure possible
  2. Contact Haltian support with sensor ID
  3. Report troubleshooting steps already attempted
  4. Haltian may send replacement sensor under warranty

Expected outcome: Replacement sensor (if within warranty and confirmed defective)

Sensor Shows “Last Seen” Timestamp Outdated

Symptoms:

  • Sensor appeared in IoT Studio previously
  • “Last Seen” timestamp hours or days old
  • No recent data updates

Common causes:

1. Sensor Moved Out of Network Range

Problem: Sensor or gateway relocated, now out of range

Solution:

  1. Verify sensor and gateway physical locations unchanged
  2. Check for environmental changes (new metal structures blocking RF)
  3. Verify intermediate routers still operational (check “Last Seen” on all sensors in path)
  4. If network topology changed, add routers or relocate gateway

Expected outcome: Network connectivity restored, “Last Seen” updates

2. Battery Depleted

Problem: Battery drained (should last 10 years, but early depletion possible)

Solution:

  1. Check battery level in IoT Studio (if available from last report)
  2. If battery < 10%, sensor may have shut down
  3. Battery non-replaceable → sensor end-of-life
  4. Deploy replacement sensor

Expected outcome: If battery depleted, replace sensor

3. Gateway Offline

Problem: Gateway lost internet connection or powered off

Solution:

  1. Check gateway status in IoT Studio
  2. Verify gateway internet connection (ethernet or cellular)
  3. Restart gateway if needed
  4. Verify power supply

Expected outcome: Gateway online, sensor data resumes transmission

4. Wirepas Mesh Network Issue

Problem: Mesh network disruption (interference, router failures)

Solution:

  1. Check signal strength (RSSI) in IoT Studio (if available from last report)
  2. If RSSI < -85 dBm, signal quality poor
  3. Add intermediate routers between sensor and gateway
  4. Contact Haltian support for mesh network diagnostics

Expected outcome: Improved mesh connectivity, data transmission resumes

Battery Issues

Battery Draining Faster Than Expected

Symptoms:

  • Battery level decreasing faster than ~10% per year
  • Expected 10-year life, but draining in 5-7 years or less

Common causes:

1. Sensor Acting as Heavy Router

Problem: Sensor relaying many packets for other sensors (router role)

Solution:

  1. Contact Haltian support to check sensor’s mesh network role
  2. If sensor is routing many packets, this is normal (trade-off for mesh connectivity)
  3. Option A: Accept shorter battery life (7-10 years still typical for routers)
  4. Option B: Add more routers to distribute load (Haltian can advise)

Expected outcome: Heavy routers have shorter battery life (7-10 years vs. 10+ years for end devices)

2. Measurement or Reporting Interval Too Short

Problem: Sensor measuring or transmitting too frequently (custom configuration)

Solution:

  1. Review measurement interval (should be 30s or 60s typically)
  2. Review reporting interval (state change + hourly typical)
  3. If intervals very short (e.g., 10s measurements), battery drains faster
  4. Contact Haltian support to adjust intervals (trade-off: slower updates vs. longer battery life)

Expected outcome: Optimized intervals extend battery life

3. Extreme Cold Environment

Problem: Battery capacity reduced in very cold temperatures (< -20°C)

Solution:

  1. Check environmental temperature range (sensor operates -35°C to +85°C)
  2. Battery chemistry (thionyl chloride lithium) capacity reduced in extreme cold
  3. If sensor in very cold environment (< -20°C), shorter battery life expected
  4. Option A: Relocate sensor to warmer location (if possible)
  5. Option B: Accept shorter battery life, plan for earlier replacement

Expected outcome: Cold environments inherently reduce battery life

4. Defective Battery (Rare)

Problem: Manufacturing defect (rare - quality control high)

Solution:

  1. If battery draining extremely fast (e.g., < 2 years), may be defect
  2. Contact Haltian support with sensor ID and battery level history
  3. If within warranty and defect confirmed, replacement sensor provided

Expected outcome: Replacement if defective and under warranty

How to Check Battery Level

In Haltian IoT Studio:

  1. Log into IoT Studio portal
  2. Navigate to Devices → Device List
  3. Find Haltian RADAR sensor (search by sensor ID)
  4. View Battery field (percentage or voltage)
  5. Review historical battery level trend (if available)

Battery level interpretation:

  • 100-80%: Excellent (sensor new or lightly used)
  • 80-50%: Good (midlife, years remaining)
  • 50-20%: Fair (monitor quarterly, plan for replacement)
  • < 20%: Low (plan for imminent replacement)
  • < 10%: Critical (sensor may stop functioning soon)

Configuration Issues

Unable to Change Sensing Distance or Measurement Interval

Symptoms:

  • Want to adjust configuration (sensing distance, intervals)
  • No self-service option in IoT Studio
  • Unclear how to change settings

Solution:

Configuration via Haltian Support:

  1. Configuration changes currently managed by Haltian remotely
  2. Email support@haltian.com with:
    • Sensor ID(s)
    • Desired configuration (sensing distance, measurement interval, etc.)
    • Use case description (parking, loading dock, custom)
  3. Haltian applies configuration remotely (typically within 1-24 hours)
  4. Verify new configuration via testing (vehicle present/absent)

Expected outcome: Haltian pushes configuration update to sensor

Configuration Change Not Taking Effect

Symptoms:

  • Requested configuration change from Haltian support
  • Sensor behavior unchanged after stated update time

Common causes:

1. Configuration Not Yet Applied

Problem: Update in progress (can take up to 24 hours)

Solution:

  1. Confirm when Haltian confirmed configuration push (check email)
  2. Wait up to 24 hours for sensor to receive and apply update
  3. Sensor must wake up and check for configuration updates
  4. If > 24 hours since Haltian confirmed, contact support

Expected outcome: Configuration applied within 24 hours

2. Sensor Out of Network Range During Update

Problem: Sensor offline when configuration pushed

Solution:

  1. Verify sensor “Last Seen” timestamp recent (< 1 hour)
  2. If sensor offline, configuration cannot be received
  3. Restore sensor connectivity (see “Connectivity Issues” section)
  4. Once online, configuration should apply automatically

Expected outcome: Configuration applies once sensor back online

3. Configuration Applied to Wrong Sensor

Problem: Multiple sensors, configuration applied to different sensor ID

Solution:

  1. Verify sensor ID in request to Haltian support
  2. Check sensor ID in IoT Studio (ensure correct sensor)
  3. Contact Haltian support to confirm configuration applied to correct sensor ID
  4. Re-request configuration for correct sensor if needed

Expected outcome: Configuration applied to correct sensor

Data Quality Issues

Distance Values Fluctuating Wildly

Symptoms:

  • Reported distance values inconsistent (e.g., 1.5m → 8.2m → 1.8m in consecutive measurements)
  • Erratic distance readings even when space stable (empty or occupied)

Common causes:

1. Sensor Vibration or Movement

Problem: Sensor mounting loose, vibrating, or shifting

Solution:

  1. Inspect sensor mounting hardware
  2. Tighten screws/bolts if loose
  3. Verify mounting surface stable (not vibrating wall or pole)
  4. Re-secure sensor, ensure level and aimed correctly
  5. Test distance measurements after re-securing

Expected outcome: Stable mounting yields consistent distance readings

2. Multi-Path Reflections

Problem: Radar reflecting off multiple surfaces (walls, ceiling, floor) causing interference

Solution:

  1. Inspect environment for reflective surfaces near sensor
  2. Option A: Relocate sensor to reduce reflections
  3. Option B: Reduce sensing distance to limit range of reflections
  4. Option C: Contact Haltian support for advanced troubleshooting

Expected outcome: Minimizing reflections stabilizes distance readings

3. Obstruction Moving in/out of Beam

Problem: Object (e.g., person, equipment) occasionally passing through 17° cone

Solution:

  1. Observe monitored area during measurement intervals
  2. Check for transient objects (pedestrians, shopping carts, forklifts, etc.)
  3. Option A: Accept transient fluctuations (normal in active environments)
  4. Option B: Adjust sensing distance to exclude transient objects
  5. Option C: Increase measurement interval to filter brief obstructions (e.g., 30s → 60s)

Expected outcome: Transient objects cause brief fluctuations (normal); longer intervals smooth data

Occupancy State Flapping (Rapid Occupied ↔ Unoccupied)

Symptoms:

  • Occupancy state toggling rapidly (occupied → unoccupied → occupied within minutes)
  • No actual vehicle coming and going that quickly
  • “Flapping” behavior

Common causes:

1. Sensing Distance at Edge of Vehicle Detection

Problem: Distance threshold exactly at vehicle edge (small movements cause state change)

Solution:

  1. If vehicle 2.0m away and sensing distance 2.0m, tiny movements cause flapping
  2. Increase sensing distance by 0.3-0.5m margin (e.g., 2.0m → 2.5m)
  3. Provides buffer zone, reduces edge-case flapping
  4. Request adjustment via Haltian support

Expected outcome: Margin eliminates flapping for stable vehicles

2. Transient Obstructions

Problem: People, shopping carts, etc. briefly triggering occupancy

Solution:

  1. Same as “Obstruction Moving in/out of Beam” above
  2. Reduce sensing distance to exclude transient objects
  3. Or accept transient triggers as normal in high-traffic areas

Expected outcome: Reduced sensing distance limits transient triggers

Performance Optimization

How to Maximize Battery Life

Best practices:

  1. Use default intervals: 30s (parking) or 60s (loading dock) optimized
  2. Avoid excessive reporting: State change + hourly is optimal
  3. Plan mesh topology: Minimize sensor router role (direct path to gateway)
  4. Monitor battery trend: Review quarterly, plan replacement proactively

Trade-offs:

  • Longer intervals = longer battery, but slower detection
  • Fewer transmissions = longer battery, but less frequent data
  • Router role = shorter battery, but essential for mesh connectivity

How to Improve Detection Accuracy

Best practices:

  1. Proper sensing distance: Measure space, add 0.3-0.5m margin
  2. Perpendicular mounting: 0-30° angle ideal, < 45° maximum
  3. Clear line of sight: No obstructions in 17° cone
  4. Appropriate height: 40-60 cm for parking, 1-3m for loading docks
  5. Test with multiple vehicles: Verify detection across vehicle sizes

Expected outcome: > 95% detection accuracy with proper configuration

How to Reduce False Positives

Best practices:

  1. Set sensing distance precisely: Don’t over-extend beyond monitored zone
  2. Avoid reflective surfaces: Clear reflections from metal walls, poles
  3. Perpendicular mounting: Minimize multi-path reflections

Expected outcome: < 1% false positive rate with proper configuration

Common Error Messages

“Sensor Offline” in IoT Studio

Meaning: Sensor hasn’t communicated with gateway recently (threshold varies, typically 1-24 hours)

Solution: See “Sensor Shows ‘Last Seen’ Timestamp Outdated” section above

“Low Battery” Alert

Meaning: Battery level below threshold (e.g., < 20%)

Solution:

  1. Note battery level percentage
  2. If < 20%, plan for sensor replacement within months
  3. If < 10%, replace sensor soon (may stop functioning)
  4. Battery non-replaceable → deploy new sensor

“Configuration Error” (if shown)

Meaning: Sensor received invalid configuration or failed to apply

Solution:

  1. Contact Haltian support immediately
  2. Provide sensor ID and error details
  3. Haltian will push corrected configuration

Advanced Troubleshooting

Using Signal Strength (RSSI) to Diagnose Issues

RSSI interpretation:

  • > -70 dBm: Excellent signal (strong mesh connectivity)
  • -70 to -85 dBm: Good signal (acceptable)
  • < -85 dBm: Poor signal (connectivity issues likely)

If RSSI poor (<-85 dBm):

  1. Add intermediate router sensors (< 20m spacing)
  2. Relocate gateway closer
  3. Check for RF obstructions (metal structures, underground)

Verifying Mesh Network Path

With Haltian support:

  1. Contact support@haltian.com with sensor ID
  2. Request mesh network path diagnostics
  3. Haltian can trace packet route from sensor → routers → gateway
  4. Identify weak links or missing routers
  5. Haltian recommends topology improvements

Factory Reset (if available)

Not typically user-accessible:

  • Sensors generally cannot be factory reset in field
  • If suspected configuration corruption, contact Haltian support
  • Haltian can remotely reset sensor to factory defaults

When to Contact Support

Contact Haltian support if:

  • ❌ Issue not resolved using this troubleshooting guide
  • ❌ Sensor hardware suspected defective
  • ❌ Battery draining much faster than expected (< 5 years)
  • ❌ Configuration changes needed (sensing distance, intervals)
  • ❌ Mesh network topology assistance required
  • ❌ “Last Seen” > 24 hours and connectivity troubleshooting failed
  • ❌ Warranty or replacement questions

Support contact:

  • Email: support@haltian.com
  • Include: Sensor ID, problem description, troubleshooting steps attempted
  • Response time: Typically 1 business day

Preventive Maintenance

To avoid issues:

  • ✅ Check battery level quarterly
  • ✅ Verify “Last Seen” weekly (or set up alerts)
  • ✅ Inspect mounting security annually
  • ✅ Review detection accuracy periodically (test with vehicle)
  • ✅ Monitor for environmental changes (new structures, obstructions)
  • ✅ Plan sensor replacement proactively (when battery < 20%)

Proactive monitoring prevents downtime and ensures reliable long-term operation.