Activity Monitor Firmware

Presence Detection Test

Objective: Verify the radar detects human presence

Steps:

1. Position yourself 1-3 meters in front of the sensor
2. Remain still (mmWave radar detects stationary humans)
3. Monitor serial output

Expected Output:

I (5234) HLK_LD2420: Target detected at 2.3m
I (5456) HLK_LD2420: Presence: YES, Distance: 2.3m

Troubleshooting:

• No detection: Check UART wiring (TX/RX may be swapped)
• Random detections: Adjust sensitivity in sensor configuration
• No serial output: Verify UART port configuration in menuconfig

Distance Accuracy Test

Objective: Test distance accuracy

Steps:

1. Stand at known distances (1m, 2m, 3m) from sensor
2. Record reported distance values
3. Compare with actual measured distance

Expected Accuracy: ±0.3m at distances up to 5m

Serial Output Example:

I (7823) HLK_LD2420: Distance: 1.2m (actual: 1.0m)
I (8234) HLK_LD2420: Distance: 2.1m (actual: 2.0m)
I (8645) HLK_LD2420: Distance: 3.3m (actual: 3.0m)

Absence Detection Test

Objective: Verify sensor detects when no one is present

Steps:

1. Leave the sensor’s detection area (move >5m away or behind obstacles)
2. Wait 5-10 seconds for timeout
3. Check serial output

Expected Output:

I (12456) HLK_LD2420: No target detected
I (12789) HLK_LD2420: Presence: NO

Manual Relay Control via MQTT

Via MQTT Command (requires MQTT broker setup):

Publish command to turn relay ON:

mosquitto_pub -h localhost -t "room/scanner/relay/set" -m "ON"

Turn relay OFF:

mosquitto_pub -h localhost -t "room/scanner/relay/set" -m "OFF"

Expected Behavior:

• Relay clicks audibly
• LED indicator changes state
• Serial output confirms state change

Serial Output:

I (45678) RELAY: Command received: ON
I (45680) RELAY: Relay state changed to ON

Automatic Presence-Based Control

Presence-Based Automation (if enabled in firmware):

Test Scenario:

1. Configure relay to activate when presence detected
2. Enter sensor detection range
3. Verify relay turns ON automatically
4. Leave detection range
5. Verify relay turns OFF after timeout

Configuration (in code or menuconfig):

#define AUTO_RELAY_ENABLED 1
#define RELAY_TIMEOUT_SEC 30  // Turn off after 30s absence

Serial Output:

I (56789) AUTO: Presence detected - Relay ON
I (87654) AUTO: Absence timeout - Relay OFF

Relay Safety & Stress Testing

Test Safety Interlocks:

Rapid Toggle Test:

# Send rapid ON/OFF commands
for i in {1..10}; do
mosquitto_pub -h localhost -t "room/scanner/relay/set" -m "ON"
sleep 0.1
mosquitto_pub -h localhost -t "room/scanner/relay/set" -m "OFF"
sleep 0.1
done

Expected Behavior:

• Relay should handle commands without lock-up
• No unexpected resets or crashes
• Commands processed in order

Baseline Measurement

Objective: Capture clean air baseline

Steps:

1. Ensure sensor is in fresh air (open window)
2. Let sensor warm up for 2-3 minutes
3. Monitor ADC readings

Serial Output:

I (12000) MQ2: ADC Raw: 1245
I (13000) MQ2: ADC Raw: 1238
I (14000) MQ2: ADC Raw: 1251
I (15000) MQ2: Baseline established: 1244

Note: Initial readings may fluctuate. Baseline stabilizes after warm-up period.

Gas Response Test

Objective: Verify sensor response to gas

Steps:

1. Introduce test gas source (e.g., alcohol, lighter gas - be careful!)
2. Hold near sensor (not directly touching)
3. Monitor ADC value changes
4. Remove gas source
5. Verify values return to baseline

Expected Behavior:

I (20000) MQ2: ADC Raw: 1244 (baseline)
I (25000) MQ2: ADC Raw: 2156 (gas detected - increase)
I (26000) MQ2: ADC Raw: 2489 (peak response)
I (30000) MQ2: ADC Raw: 1567 (recovery)
I (35000) MQ2: ADC Raw: 1252 (back to baseline)

Safety Warning:

• Test in well-ventilated area
• Use small amounts of test gas
• Never use open flame near sensor during operation

Calibration Verification

Objective: Verify calibration algorithm

Current Implementation: Baseline drift compensation

Test Procedure:

1. Record initial baseline
2. Run for 24 hours
3. Check if baseline auto-adjusts for environmental drift

Expected: Baseline should slowly adjust to compensate for temperature/humidity changes

Serial Output:

I (00:00) MQ2: Initial baseline: 1244
I (01:00) MQ2: Baseline adjusted: 1247
I (02:00) MQ2: Baseline adjusted: 1243

Mosquitto MQTT Broker Setup

Install Mosquitto (if not already installed):

sudo apt update
sudo apt install mosquitto mosquitto-clients
sudo systemctl start mosquitto
sudo systemctl enable mosquitto

Verify Broker Running:

sudo systemctl status mosquitto

Test Broker:

# Terminal 1: Subscribe
mosquitto_sub -h localhost -t "test" -v

# Terminal 2: Publish
mosquitto_pub -h localhost -t "test" -m "Hello MQTT"

Monitor Sensor Data

Subscribe to All Topics:

mosquitto_sub -h localhost -t "room/scanner/#" -v

Expected Output (example):

room/scanner/presence {"detected":true,"distance":2.3,"timestamp":1678901234}
room/scanner/air_quality {"gas_level":1244,"status":"normal","timestamp":1678901234}
room/scanner/relay {"state":"on","auto_mode":true,"timestamp":1678901234}
room/scanner/status {"uptime":3600,"wifi_rssi":-45,"free_heap":123456}

Check Publishing Rate:

• Presence updates: Every 1-2 seconds (configurable)
• Air quality: Every 5-10 seconds (configurable)
• Status: Every 30 seconds (configurable)

Test MQTT Commands

Send Relay Commands:

# Turn relay ON
mosquitto_pub -h localhost -t "room/scanner/relay/set" -m '{"state":"on"}'

# Turn relay OFF
mosquitto_pub -h localhost -t "room/scanner/relay/set" -m '{"state":"off"}'

# Toggle relay
mosquitto_pub -h localhost -t "room/scanner/relay/set" -m '{"action":"toggle"}'

Monitor ESP32 Response:

I (45678) MQTT: Message received on topic: room/scanner/relay/set
I (45680) MQTT: Payload: {"state":"on"}
I (45682) RELAY: Command processed: ON

Test Configuration Updates (if implemented):

# Update sampling interval
mosquitto_pub -h localhost -t "room/scanner/config/set" -m '{"sample_interval":2000}'

Test Connection Reliability

Test Reconnection:

1. Flash firmware and verify MQTT connected
2. Stop Mosquitto broker:

sudo systemctl stop mosquitto

3. Monitor ESP32 serial output - should show reconnection attempts
4. Restart broker:

sudo systemctl start mosquitto

5. Verify ESP32 automatically reconnects

Expected Serial Output:

I (12000) MQTT: Connection lost - attempting reconnect
I (13000) MQTT: Reconnection attempt 1/5
I (14000) MQTT: Reconnection attempt 2/5
I (20000) MQTT: Reconnected successfully
I (20100) MQTT: Resuming data publishing

Flashing Issues

Problem: A fatal error occurred: Failed to connect to ESP32-S3

Solutions:

1. Hold BOOT button while connecting USB
2. Check USB cable - some cables are power-only
3. Verify port: ls /dev/ttyUSB* or ls /dev/ttyACM*
4. User permissions: sudo usermod -a -G dialout $USER (logout/login required)
5. Try different USB port - some ports have power issues

Problem: Flash size mismatch

Solution: Set flash size to 16MB in menuconfig → Serial flasher config

WiFi Connection Problems

Problem: WiFi not connecting

Solutions:

1. Verify credentials in menuconfig
2. Check 2.4GHz network - ESP32 doesn’t support 5GHz
3. SSID visibility - hidden networks may need special configuration
4. Signal strength - try moving closer to router
5. Router compatibility - some enterprise networks require special auth

Check logs:

E (5000) wifi:Failed to connect to SSID:YourNetwork

Debug command:

idf.py menuconfig
# Enable: Component config → ESP32-specific → WiFi debug log

MQTT Connection Problems

Problem: MQTT not connecting

Solutions:

1. Verify broker running: sudo systemctl status mosquitto
2. Check broker URI in menuconfig (use IP instead of localhost if needed)
3. Test broker locally: mosquitto_sub -h localhost -t "test"
4. Firewall: Ensure port 1883 is open
5. Authentication: Verify username/password if broker requires auth

Problem: Data not publishing

Solutions:

1. Check topic subscription: mosquitto_sub -h localhost -t "#" -v
2. Verify WiFi connected before MQTT attempts
3. Increase log verbosity in menuconfig
4. Check QoS settings - start with QoS 0 for testing

Sensor Troubleshooting

HLK-LD2420 Not Detecting:

• Swap TX/RX connections (common wiring error)
• Verify 5V power supply (insufficient power causes erratic behavior)
• Check UART configuration (baud rate, pins)
• Sensor needs clear line of sight

MQ-2 Incorrect Readings:

• Allow 2-3 minute warm-up time
• Check VCC connection (needs stable 5V)
• Verify ADC channel configuration
• Calibrate in fresh air environment

Relay Not Responding:

• Verify GPIO pin number in configuration
• Check relay module VCC (3.3V or 5V requirement)
• Test GPIO directly: gpio_set_level(GPIO_NUM_21, 1);
• Check relay LED indicator for control signal

Full-Stack Web Application

Technology Stack:

• Frontend: React.js with real-time WebSocket updates
• Backend: FastAPI (Python) RESTful API
• Database: MongoDB for time-series data storage
• Visualization: Chart.js or D3.js for graphs

Features:

• Real-time sensor visualization
• Historical data analysis and trends
• Device configuration management
• Alert rule configuration
• Multi-device monitoring
• User authentication and access control

Current Status: 🔲 Planned

Intelligent Pattern Recognition

Capabilities:

• Anomaly Detection: Identify unusual activity patterns
• Predictive Alerts: Forecast potential issues based on trends
• Sleep Quality Analysis: Analyze motion and sound for sleep assessment
• Energy Optimization: Learn usage patterns for efficient automation

Implementation Approach:

• Edge ML: TensorFlow Lite on ESP32-S3 for real-time inference
• Cloud Training: Collect data and train models in cloud
• Model Deployment: OTA updates for improved models

Use Cases:

• Elderly fall detection
• Unusual absence alerts
• Sleep disorder screening
• Optimized HVAC scheduling

Current Status: 🔲 Research phase

iOS and Android Native Apps

Features:

• Real-time device monitoring
• Push notifications for alerts
• Remote relay control
• Device configuration
• Historical data viewing
• Geofencing for location-based automation

Technology:

• iOS: Swift/SwiftUI
• Android: Kotlin/Jetpack Compose
• Communication: MQTT over WebSocket or REST API

Current Status: 🔲 Planned

Advanced System Capabilities

Over-The-Air (OTA) Updates

• Secure firmware updates without physical access
• Rollback capability for failed updates
• Staged deployment for testing
• Status: 🔲 Planned

Bluetooth Low Energy (BLE)

• Offline configuration and data retrieval
• Mobile app connectivity without WiFi
• Backup communication channel
• Status: 🔲 Planned

Multi-Room System

• Centralized monitoring of multiple rooms
• Inter-device communication
• Coordinated automation
• Aggregate analytics
• Status: 🔲 Future vision

Power Optimization

• Deep sleep modes
• Battery operation support
• Solar charging integration
• Status: 🔲 Research