Troubleshooting

Common issues, diagnostic procedures, and solutions for Thingsee ENVIRONMENT sensors

Quick Diagnostics

Basic Checks

Before detailed troubleshooting:

  • Batteries installed correctly (polarity matched)
  • LED flashed on battery installation
  • Gateway operational (green blinking LED)
  • Sensor within 20m of gateway or another sensor
  • At least one heartbeat interval (1 hour) has passed

LED Indicators

  • Single flash on power-on: Normal operation startup
  • No continuous LED: Normal (battery conservation)

Note: Sensors do not have constant LED indication to maximize battery life.

Installation Issues

LED Not Flashing on Battery Installation

Symptoms:

  • No LED flash when batteries inserted
  • No power indication

Possible Causes:

  • Batteries inserted incorrectly
  • Batteries depleted or defective
  • Battery contacts not making connection
  • Sensor malfunction

Solutions:

  1. Verify battery polarity

    • Check +/- orientation matches compartment markings
    • Both AAA batteries must be correct
    • Ensure fully seated in contacts

  2. Try fresh batteries

    • Use recommended: Varta Industrial Pro 1.5V AAA LR03
    • Test with multimeter: should read >1.4V per battery
    • Avoid mixing old and new batteries

  3. Check battery contacts

    • Inspect for corrosion or damage
    • Clean with isopropyl alcohol if needed
    • Ensure spring contacts not compressed

  4. Remove and reinsert batteries

    • Take both batteries out
    • Wait 10 seconds
    • Reinsert with correct polarity
    • Should see brief LED flash

  5. Verify cover connection

    • Ensure A-cover and B-cover properly aligned
    • Press firmly until click
    • Internal connection may be loose if not fully seated

If still no response: Contact support@haltian.com with sensor ID

Sensor Not Appearing in Cloud

Symptoms:

  • Sensor not listed in Haltian IoT Studio
  • No data received after installation
  • “Last Seen” shows never or very old timestamp

Possible Causes:

  • Gateway not operational
  • Sensor not joined to network
  • Network coverage issue (too far from gateway)
  • Sensor not provisioned correctly
  • First heartbeat interval not yet elapsed

Solutions:

  1. Verify gateway operational

    • Check gateway LED (should be blinking green)
    • Confirm internet connectivity
    • Gateway appears “Online” in IoT Studio
    • Test with another known-working sensor

  2. Confirm network coverage

    • Sensor within 20m of gateway or another sensor
    • Check for physical obstructions (thick walls, metal, fire doors)
    • Add intermediate sensors as routers if needed

  3. Wait for first message

    • Default heartbeat: 1 hour
    • First message may take 60-90 minutes
    • Sensor joins network, then waits for report interval

  4. Trigger a report manually

    • Change environment significantly:
      • Wave hand in front of sensor (light change)
      • Warm sensor with hands (temperature change)
      • Open/close nearby door if magnetic switch in use
    • Should trigger event report within 5-10 minutes

  5. Verify sensor provisioning

    • Check sensor added to correct project in IoT Studio
    • Verify sensor ID matches QR code label
    • Confirm network ID and keys match gateway

  6. Power cycle the sensor

    • Remove both batteries
    • Wait 30 seconds
    • Reinsert batteries (correct polarity)
    • LED should flash
    • Wait 10 minutes for network rejoin

If still not appearing after 2 hours: Contact support with sensor ID, installation location, gateway ID, and installation time

Poor Signal Strength (RSSI)

Symptoms:

  • RSSI values < -85 dBm in IoT Studio
  • Intermittent data reception
  • Long gaps between messages

Possible Causes:

  • Sensor too far from gateway or mesh network
  • Physical obstructions
  • RF interference
  • Suboptimal mesh density

Solutions:

  1. Check distance to gateway

    • Should be < 20m from gateway or another sensor
    • Measure straight-line distance
    • Account for floor height in multi-story buildings

  2. Identify obstructions

    • Metal structures, filing cabinets, equipment
    • Concrete walls with rebar
    • Fire doors (metal core)
    • Solution: Relocate sensor or add mesh routers

  3. Add intermediate sensors

    • Deploy sensors between isolated sensor and gateway
    • Each sensor acts as mesh router
    • Creates redundant paths

  4. Check for RF interference

    • WiFi routers on 2.4 GHz
    • Microwave ovens
    • Bluetooth devices
    • Solution: Relocate away from interference sources

RSSI Guidelines:

  • > -60 dBm: Excellent
  • -60 to -70 dBm: Good
  • -70 to -85 dBm: Fair (monitor)
  • < -85 dBm: Poor (action required)

Data Quality Issues

Temperature Readings Seem Incorrect

Symptoms:

  • Temperature significantly different from thermostat
  • Values don’t match other sensors

Possible Causes:

  • Sensor in microclimate (sun, heat source, airflow)
  • Comparison device inaccurate or poorly placed
  • Sensor not acclimated to environment
  • Normal variation due to location differences

Solutions:

  1. Verify sensor placement

    • Not in direct sunlight?
    • Not near heating/cooling vents?
    • Not above radiators?
    • Not in cold draft from window?
    • Relocate if in microclimate

  2. Allow acclimation time

    • Wait 15-30 minutes after installation or battery change
    • Sensor needs to equilibrate to room temperature

  3. Compare to calibrated reference

    • Thermostat may be in different location (different temperature)
    • Thingsee ENVIRONMENT: ±0.3°C accuracy
    • 2-3°C variation normal in same room

  4. Check for thermal sources

    • Sun exposure (even indirect)
    • Nearby equipment (computers, monitors)
    • Heat from lighting
    • Solution: Relocate to representative location

If readings still seem incorrect: Document exact values, comparison device specs, installation location. Contact support for sensor verification.

Humidity Readings Seem Wrong

Symptoms:

  • Humidity significantly different from other devices
  • Values seem too high or too low

Possible Causes:

  • Consumer comparison device inaccurate (±5-10% typical)
  • Sensor in microclimate (near bathroom, kitchen, humidifier)
  • Recent battery change (sensor needs recalibration time)
  • Sensor exposed to condensing humidity

Solutions:

  1. Verify comparison device accuracy

    • Consumer humidity meters often inaccurate
    • Thingsee ENVIRONMENT: ±5% RH accuracy
    • Use NIST-traceable reference if available

  2. Check sensor location

    • Not near bathroom or kitchen (high humidity)
    • Not near humidifier or dehumidifier
    • Not in direct HVAC airflow
    • Relocate if in microclimate

  3. Wait for stabilization

    • After battery change, wait 1-2 hours
    • After exposure to condensing humidity, wait 4-6 hours for sensor recovery

  4. Verify no condensation exposure

    • Humidity sensor degrades if exposed to condensing conditions
    • IP30 rating: Not suitable for wet environments
    • If condensation occurred, contact support for sensor evaluation

Ambient Light Readings Fluctuate or Seem Incorrect

Symptoms:

  • Light values don’t match expectations
  • Readings fluctuate wildly
  • Doesn’t detect lights on/off

Important: Light sensor is not calibrated - provides indicative values only

Possible Causes:

  • Sensor orientation (not facing light sources)
  • Shadows or obstructions blocking sensor
  • Daylight overwhelming artificial light
  • Normal behavior (sensor designed for on/off detection, not precision)

Solutions:

  1. Understand sensor limitations

    • Light measurement indicative only
    • Suitable for relative changes and on/off detection
    • Not suitable for precision lux measurements

  2. Check sensor orientation

    • Sensor face should point toward room lights
    • Not obstructed by furniture or equipment
    • Not in shadow

  3. Verify light source detection

    • Turn lights fully on → expect 300-1000+ lux
    • Turn lights fully off → expect < 50 lux
    • Large difference confirms working

  4. Consider daylight interference

    • Near windows: daylight may overwhelm room lights
    • Use higher threshold (e.g., 10,000 lux) to detect major changes
    • Or relocate sensor away from window influence

Expected behavior: Large changes (thousands of lux) when lights turn on/off. Absolute values less important than relative changes.

Magnetic Switch Not Detecting Door/Window Opens

Symptoms:

  • State counter not incrementing
  • Door opens but no detection in IoT Studio
  • Inconsistent detection

Possible Causes:

  • Magnet and sensor not aligned
  • Gap too large (> 15mm)
  • Wrong magnet type (too weak)
  • Magnet orientation incorrect

Solutions:

  1. Verify alignment

    • Sensor and magnet must be parallel, facing each other
    • Maximum gap when closed: 15mm (preferably 5-10mm)
    • Use ruler to measure gap

  2. Check magnet strength

    • Use strong permanent magnet (neodymium recommended)
    • Test: Magnet should attract small metal objects
    • Weak magnets may not trigger sensor

  3. Test magnet orientation

    • Magnet has north and south poles
    • Try flipping magnet 180° if detection poor
    • One orientation typically works better

  4. Verify sensor sees magnet

    • With door/window closed, magnet should be directly adjacent to sensor
    • Move magnet closer if gap too large
    • Check that door/window doesn’t sag or shift when opening/closing

  5. Test detection

    • Slowly open door/window while watching IoT Studio
    • Counter should increment within 1-5 minutes
    • Perform several open/close cycles to confirm consistent detection

If still not working: Magnet may be too weak, or gap too large. Contact support for replacement magnet or troubleshooting assistance.

Machine Usage Mode Not Detecting Vibration

Symptoms:

  • Equipment running but no vibration reports
  • Machine Usage Mode enabled but no data
  • Accelerometer shows static values only

Possible Causes:

  • Machine Usage Mode not actually enabled (contact support required)
  • Insufficient vibration (below 128mG threshold)
  • Poor mechanical coupling (tape mounting on vibrating equipment)
  • Equipment not actually running during test

Solutions:

  1. Verify Machine Usage Mode enabled

    • Contact Haltian support to confirm configuration
    • Standard mode does NOT detect vibration (only position/orientation)
    • Support must remotely enable Machine Usage Mode

  2. Check mounting method

    • Must use screw mounting for vibration detection
    • Tape mounting insufficient (dampens vibration)
    • Ensure rigid mechanical coupling to equipment
    • Verify screws tight (no wobbling)

  3. Verify equipment vibration level

    • Some equipment has very low vibration (< 128mG threshold)
    • Test by touching equipment - should feel vibration clearly
    • If barely perceptible, may be below detection threshold
    • Contact support to lower threshold if needed

  4. Confirm equipment actually running

    • Verify equipment in operating mode (not idle)
    • Run full operational cycle during test
    • Check that vibration present at sensor location

  5. Check sensor orientation and location

    • Vibration strongest at certain points on equipment
    • Try different mounting location if possible
    • Ensure sensor not on dampened/isolated part

If still not detecting: Contact support with equipment type, mounting details, and approximate vibration level. Support can verify Machine Usage Mode configuration and adjust sensitivity.

Battery Issues

Battery Life Shorter Than Expected

Symptoms:

  • Battery level dropping faster than 5-year expected life
  • Frequent low battery warnings
  • Battery depleted in < 3 years

Possible Causes:

  • High reporting frequency (custom configuration)
  • Machine Usage Mode (expected 4 years vs. 5 years standard)
  • Poor signal strength (many retransmissions)
  • Sensor acting as mesh router for many others
  • Low-quality or old batteries
  • Cold operating environment

Solutions:

  1. Review configuration

    • Check reporting thresholds and intervals in IoT Studio
    • Very low thresholds = frequent reports = more battery use
    • Machine Usage Mode uses more power (50Hz sampling when active)
    • Default thresholds optimal for battery life

  2. Improve signal strength

    • Poor RSSI (< -85 dBm) causes retransmissions
    • Add intermediate sensors to improve mesh
    • Better signal = less power per transmission

  3. Check mesh network density

    • If sensor routing for many others, power consumption higher
    • Contact support for network topology review

  4. Verify battery quality

    • Use recommended: Varta Industrial Pro 1.5V AAA LR03
    • Avoid bargain or off-brand batteries
    • Check expiration date
    • Old batteries (> 2 years in storage) have reduced capacity

  5. Operating temperature

    • Cold environments reduce battery capacity
    • Alkaline batteries lose capacity below +10°C
    • Shorter battery life expected in cold areas

Battery life estimates:

  • Standard mode (default): 5 years
  • Machine Usage Mode: 4 years
  • High-frequency custom config: 3-4 years

Low Battery Warning but Batteries Recently Replaced

Symptoms:

  • Low battery alert shortly after new batteries
  • Battery level drops rapidly from 100%

Possible Causes:

  • Batteries not fresh (old stock)
  • Poor quality batteries
  • Battery contacts not making good connection
  • Very cold environment affecting measurement

Solutions:

  1. Verify battery freshness

    • Check expiration date on battery packaging
    • Batteries have ~2-3 year shelf life
    • Old stock may have reduced capacity

  2. Test battery voltage

    • Use multimeter: should read 1.5-1.6V per battery when fresh
    • < 1.4V indicates depleted or defective

  3. Try different battery brand

    • Use recommended: Varta Industrial Pro AAA
    • Alkaline batteries required (not lithium, not rechargeable)

  4. Clean battery contacts

    • Remove batteries
    • Clean contacts with isopropyl alcohol
    • Ensure spring contacts not damaged
    • Reinsert fresh batteries

  5. Check environmental temperature

    • Battery level calculation affected by extreme cold
    • Below +10°C, apparent capacity reduces
    • If sensor in cold zone, indication may be pessimistic

  6. Wait 24 hours

    • Battery level calculation may need time to stabilize
    • If drops to < 20% within 24 hours, batteries defective

If issue persists: Try completely different battery batch. Contact support with sensor ID and battery details.

Network and Connectivity Issues

Sensor Reporting Intermittently

Symptoms:

  • Gaps in data (missing hours or days)
  • “Last Seen” timestamp irregular
  • Messages arrive in bursts, then silence

Possible Causes:

  • Borderline signal strength (RSSI near -85 dBm)
  • Gateway intermittent connectivity or reboots
  • Temporary RF interference
  • Mesh network instability

Solutions:

  1. Check signal strength trends

    • Review RSSI history in IoT Studio
    • If hovering around -85 dBm, borderline coverage
    • Add intermediate sensor to improve link

  2. Verify gateway stability

    • Check gateway uptime and connectivity
    • Gateway reboots cause temporary sensor silence
    • Review gateway logs for issues

  3. Monitor for patterns

    • Do gaps occur at specific times? (interference)
    • Random gaps or consistent time of day?
    • Pattern may indicate external cause

  4. Add mesh redundancy

    • Deploy additional sensors in area
    • Creates multiple routing paths
    • Improves network resilience

  5. Review mesh network health

    • Contact support for network analysis
    • Identify routing bottlenecks or weak links

Expected behavior:

  • Continuous reports every 5-60 minutes (depending on activity)
  • Maximum gap: heartbeat interval (default 1 hour)
  • Occasional 2-hour gap acceptable
  • Gaps > 3 hours indicate problem

No Data After Battery Replacement

Symptoms:

  • Sensor was working, stopped after battery change
  • LED flashed on new battery installation
  • But no data in cloud

Possible Causes:

  • Sensor not rejoined to network after reboot
  • Batteries inserted incorrectly despite LED flash
  • Configuration reset (rare)

Solutions:

  1. Wait for network rejoin

    • After battery replacement, sensor reboots
    • Network rejoin: 1-10 minutes
    • First data may arrive after heartbeat (up to 1 hour)
    • Be patient, wait 1-2 hours

  2. Verify batteries correctly installed

    • Double-check polarity markings
    • Both batteries correctly oriented
    • LED flash doesn’t guarantee proper operation if one battery reversed

  3. Power cycle again

    • Remove both batteries
    • Wait 30 seconds
    • Reinsert carefully (correct polarity)
    • Wait 1 hour for first report

  4. Check IoT Studio device list

    • Sensor should still be listed
    • If missing, may need reprovisioning
    • Contact support if device disappeared

  5. Trigger event manually

    • Wave hand in front (light change)
    • Warm sensor (temperature change)
    • Should trigger event report within 5-10 minutes

If still no data after 2 hours: Contact support - sensor may need reprovisioning (rare)

Support and Diagnostics

Collecting Diagnostic Information

When contacting support, provide:

Sensor Information:

  • Sensor ID (from QR code label)
  • Installation date
  • Physical location description
  • Battery installation/replacement dates
  • Operational mode (Standard or Machine Usage)

Symptom Details:

  • What is not working as expected?
  • When did issue start?
  • Recent changes (batteries, moved sensor, configuration)?
  • How frequently does issue occur?

IoT Studio Data:

  • Last seen timestamp
  • Recent RSSI values
  • Battery level
  • Screenshot of sensor dashboard if possible

Environmental Context:

  • Room size and type
  • HVAC system (always on, scheduled, none)
  • For Machine Usage Mode: Equipment type, expected vibration level
  • For magnetic switch: Door/window type, magnet position

Contacting Support

  • Email: support@haltian.com
  • Subject line: “Thingsee ENVIRONMENT - [brief issue description]”
  • Provide: Sensor ID, symptom, troubleshooting attempted
  • Response time: Typically within 1 business day

Warranty and Replacement

  • Standard warranty: 2 years from purchase date
  • Exclusions: Battery depletion, physical damage, environmental damage
  • RMA process: Contact support for return authorization
  • Replacement timeline: Typically 1-2 weeks

Preventive Maintenance

Regular Checks (Monthly)

  • Verify sensor reporting in IoT Studio
  • Check battery level (should decline slowly)
  • Review RSSI signal strength
  • Spot-check measurement values for reasonableness
  • If magnetic switch: Test door/window detection

Periodic Maintenance (Annually)

  • Visual inspection (physical damage?)
  • Verify mounting still secure
  • Clean sensor exterior with dry cloth (dust)
  • Review historical data trends
  • Verify placement still optimal (room layout changes?)

Battery Replacement Planning

  • Schedule replacement at 20% battery level
  • Keep spare AAA batteries in inventory
  • Use recommended: Varta Industrial Pro 1.5V AAA LR03
  • Document replacement dates for lifecycle tracking

Still having issues? Contact support@haltian.com with your sensor ID and problem description.