Troubleshooting Guide

Solutions to common problems with Wala Works automation devices.

Quick Diagnostic Checklist

Before diving into specific issues, run through this checklist:

  • [ ] Device powered on (LED visible)
  • [ ] Power supply correct voltage (12-24V for MotorWala, 12V for RelayWala)
  • [ ] Device connected to WiFi (check router)
  • [ ] Device reachable (ping IP address)
  • [ ] Recent firmware updates applied
  • [ ] Configuration backed up

Power & Hardware Issues

Device Won't Power On

Symptoms:

  • No LED light
  • Device not responding
  • No network presence

Solutions:

1. Check power supply:

# Measure voltage with multimeter
Expected: 12-24V DC (MotorWala), 12V DC (RelayWala)

2. Verify connections:

  • Check +/- polarity
  • Tighten terminal screws
  • Inspect wires for damage
  • Try different power outlet

3. Test with known-good power supply:

  • Borrow from another device
  • Try bench power supply
  • Check current capacity (minimum 2A)

4. Hardware reset:

  • Disconnect power for 30 seconds
  • Reconnect and observe LED
  • Check for smoke/burning smell

If still not working:

  • Contact support with purchase details
  • Device may need warranty service

LED Patterns

Understanding LED behavior:

| Pattern | Meaning | Action | |---------|---------|--------| | Rapid blink | Setup mode | Connect to WiFi AP | | Slow blink | Connecting to WiFi | Wait 30 seconds | | Solid on | Normal operation | Good | | Off | No power or fault | Check power | | Fast flash then off | Boot loop | Factory reset needed |

Overheating

Symptoms:

  • Device hot to touch
  • Random reboots
  • Performance degradation

Solutions:

1. Improve ventilation:

  • Remove from enclosed space
  • Add cooling fins
  • Install small fan
  • Keep away from heat sources

2. Check load:

# For RelayWala - check current draw
# Ensure relays not overloaded
Maximum per channel: 10A

3. Reduce duty cycle:

  • Limit continuous operation time
  • Add rest periods
  • Use larger relay for heavy loads

Network & Connectivity

Can't Connect to Setup WiFi

Symptoms:

  • Device AP not visible
  • Can't join device network
  • Setup page won't load

Solutions:

1. Ensure setup mode:

  • Hold reset button 10 seconds
  • LED should blink rapidly
  • Release and try again

2. Check phone/computer WiFi:

  • Disable mobile data (on phone)
  • Forget other networks temporarily
  • Use 2.4GHz capable device

3. Try different device:

  • Use laptop instead of phone
  • Try different phone
  • Check WiFi adapter supports 2.4GHz

4. Manual IP: If auto-redirect fails:

Manually navigate to: http://192.168.4.1

Device Won't Connect to Home WiFi

Symptoms:

  • Setup completes but device offline
  • Can't find device on network
  • LED keeps slow blinking

Solutions:

1. Verify WiFi settings:

  • Check password carefully (case-sensitive)
  • Ensure 2.4GHz network (5GHz not supported)
  • Try network without special characters in name

2. Router compatibility:

  • Disable MAC filtering temporarily
  • Check DHCP pool not full
  • Ensure WPA2 encryption (WPA3 may have issues)
  • Set channel to 1, 6, or 11

3. Signal strength:

  • Move router closer
  • Use WiFi extender
  • Check for interference
  • Reduce obstacles between device and router

4. Check router logs:

# Look for connection attempts
# Check for DHCP lease denials
# Verify device MAC address

Device Keeps Disconnecting

Symptoms:

  • Intermittent connection
  • Device goes offline randomly
  • Poor reliability

Solutions:

1. Check signal strength:

# Via API
curl http://192.168.1.100/api/system/wifi

# Look for RSSI value
-30 to -50 dBm = Excellent
-50 to -60 dBm = Good
-60 to -70 dBm = Fair
-70 to -80 dBm = Poor (action needed)
Below -80 dBm = Unusable

2. Improve WiFi:

  • Move router closer
  • Add WiFi extender/mesh
  • Change WiFi channel
  • Reduce interference (microwaves, cordless phones)

3. Check power supply:

  • Insufficient power can cause WiFi drops
  • Try different power adapter
  • Check voltage under load

4. Update firmware:

  • May contain WiFi stability fixes
  • Backup config first
  • Follow update procedure

5. Configure WiFi power save:

# Settings → Network → WiFi
WiFi Power Save: Disabled

Can't Find Device IP

Symptoms:

  • Device connected but IP unknown
  • Can't access web interface
  • Need to find device on network

Solutions:

Method 1: Check router:

  • Log into router admin
  • Look at DHCP leases
  • Find device by name or MAC

Method 2: Network scan:

# Using nmap
nmap -sn 192.168.1.0/24

# Using arp-scan
sudo arp-scan --localnet | grep -i wala

# Using fing (mobile app)
# Scan network and look for ESP32 devices

Method 3: mDNS:

# Try hostname
ping motorwala-01.local
ping relaywala-01.local

# Or use avahi-browse
avahi-browse -rt _http._tcp

Method 4: Serial monitor:

# Connect via USB
screen /dev/ttyUSB0 115200

# IP printed during boot
# Press reset button to reboot

MQTT Issues

MQTT Not Connecting

Symptoms:

  • Device shows "MQTT: Disconnected"
  • No state updates
  • Commands work via HTTP but not MQTT

Solutions:

1. Verify broker running:

# Check Mosquitto service
sudo systemctl status mosquitto

# Test with client
mosquitto_sub -h 192.168.1.50 -t test

2. Check credentials:

# Device settings
MQTT Username: wala-devices
MQTT Password: [verify correct]

3. Test connection:

# From another machine
mosquitto_sub -h 192.168.1.50 -p 1883 \
  -u wala-devices -P your-password \
  -t motorwala/#

4. Check broker logs:

sudo tail -f /var/log/mosquitto/mosquitto.log

Common errors:

  • "Connection refused" → Broker not running
  • "Auth failed" → Wrong username/password
  • "Connection lost" → Network issue

5. Firewall rules:

# Ensure port 1883 open
sudo ufw allow 1883/tcp

# Or check iptables
sudo iptables -L | grep 1883

MQTT Messages Not Arriving

Symptoms:

  • Device connected but no updates
  • Commands not working
  • State not syncing

Solutions:

1. Verify topics:

# Subscribe to all device topics
mosquitto_sub -h 192.168.1.50 -t motorwala/# -v

# Send test command
mosquitto_pub -h 192.168.1.50 \
  -t motorwala/living-room/set \
  -m "OPEN"

2. Check device topic configuration:

# Settings → MQTT → Topics
Command Topic: motorwala/living-room/set
State Topic: motorwala/living-room/state

3. QoS settings:

# Try QoS 1 for reliability
MQTT QoS: 1

4. Test retained messages:

# Check for retained state
mosquitto_sub -h 192.168.1.50 -t motorwala/# -v --retained-only

MotorWala Specific Issues

Motor Not Moving

Symptoms:

  • Commands accepted but motor doesn't move
  • API returns success
  • No motor sound

Solutions:

1. Test motor directly:

  • Disconnect from MotorWala
  • Connect directly to power supply
  • Verify motor works

2. Check current capacity:

  • Motor may need more current than supply provides
  • Minimum 2A recommended
  • Try higher amperage power supply

3. Verify connections:

  • M+ and M- terminals tight
  • No loose wires
  • Correct polarity

4. Test via API:

# Test open command
curl -X POST http://192.168.1.100/api/motor/open

# Check status
curl http://192.168.1.100/api/status

5. Check logs:

curl http://192.168.1.100/api/system/logs?limit=20

Look for:

  • Stall detection
  • Over-current errors
  • Motor driver faults

Motor Runs Wrong Direction

Symptom:

  • Open command closes
  • Close command opens

Solution:

Method 1: Software reversal:

# Settings → Motor → Direction
Direction: Reversed

Method 2: Swap wires:

  • Swap M+ and M- connections
  • Simpler for permanent fix

Position Inaccurate

Symptoms:

  • Position drifts over time
  • Doesn't reach full open/close
  • Positions inconsistent

Solutions:

1. Recalibrate:

curl -X POST http://192.168.1.100/api/motor/calibrate

2. Check for slippage:

  • Verify motor coupling tight
  • Check belt/gear not slipping
  • Inspect mechanical connections

3. Set position limits:

# Settings → Motor → Limits
Upper Limit: 95
Lower Limit: 5

4. Verify full travel time:

curl http://192.168.1.100/api/motor/calibration

Should show consistent travel time.

Motor Stalls

Symptoms:

  • Motor starts but stops mid-movement
  • Stall errors in logs
  • Inconsistent operation

Solutions:

1. Check for obstructions:

  • Remove any blockages
  • Verify free movement
  • Check mechanical binding

2. Adjust stall detection:

# Settings → Motor → Safety
Stall Threshold: 3000ms  # Increase if false positives

3. Check power under load:

  • Measure voltage while motor running
  • Should not drop significantly
  • Upgrade power supply if needed

4. Reduce speed:

# Settings → Motor → Speed
Speed: 30  # Slower = less current

RelayWala Specific Issues

Relay Not Clicking

Symptoms:

  • Command sent but no click
  • Load not switching
  • No relay board activity

Solutions:

1. Verify power:

  • Check 12V supply
  • Measure voltage at relay board
  • Try different power source

2. Test individual relay:

# Test relay 1
curl -X POST http://192.168.1.101/api/relay/1/on

# Listen for click sound

3. Check relay board:

  • Visual inspection for damage
  • Test continuity with multimeter
  • Replace relay board if faulty

4. Check API response:

curl http://192.168.1.101/api/relay/1

Should show state change.

Relay Clicks But Load Not Switching

Symptoms:

  • Relay audibly clicks
  • LED on relay board lights up
  • But connected load doesn't switch

Solutions:

1. Check load wiring:

  • Verify COM, NO, NC connections
  • Ensure wires in correct terminals
  • Check terminal screw tightness

2. Test load independently:

  • Connect load directly to power
  • Verify load works
  • Check voltage at load

3. Measure relay contacts:

# Use multimeter
# Check continuity between COM and NO when relay ON
# Should show < 1 ohm resistance

4. Check load current:

  • Ensure load < 10A
  • Heavy loads may need contactor
  • Inductive loads need snubber circuit

Relay Stuck On/Off

Symptoms:

  • Relay won't change state
  • Stays on even when commanded off
  • Or vice versa

Solutions:

1. Power cycle:

  • Turn off device
  • Wait 30 seconds
  • Power back on

2. Check for welded contacts:

  • Relay may have failed
  • Replace relay board
  • Reduce inrush current on load

3. Factory reset:

curl -X POST http://192.168.1.101/api/system/reset

4. Check interlock settings:

# Settings → Relays → Channel X
Interlock: None  # Or verify correct setting

API & Integration Issues

API Commands Not Working

Symptoms:

  • Commands fail
  • 401/403 errors
  • Timeouts

Solutions:

1. Check authentication:

# If auth enabled, include token
curl -H "Authorization: Bearer YOUR_TOKEN" \
  http://192.168.1.100/api/status

2. Verify URL:

# Correct format
http://192.168.1.100/api/motor/open

# Not:
http://192.168.1.100:80/motor/open  # Missing /api

3. Check HTTP method:

# Control commands need POST
curl -X POST http://192.168.1.100/api/motor/open

# Not GET:
curl http://192.168.1.100/api/motor/open

4. Test with verbose output:

curl -v -X POST http://192.168.1.100/api/motor/open

Home Assistant Integration Issues

Symptoms:

  • Device not discovered
  • States not updating
  • Commands not working

Solutions:

1. Check MQTT integration:

# Configuration → Integrations → MQTT
# Should show connected

2. Verify discovery:

# Device settings
MQTT Discovery: Enabled
Discovery Prefix: homeassistant  # Default

3. Manual configuration:

# If discovery fails, use manual config
# See [Integration with Home Assistant](/installation/software-setup#integration-with-home-assistant)

4. Check HA logs:

# In Home Assistant
# Settings → System → Logs
# Filter for MQTT or device name

5. Restart HA:

# After configuration changes
Developer Tools → Restart

Performance Issues

Slow Response Times

Symptoms:

  • Commands take long to execute
  • Web interface laggy
  • Timeouts

Solutions:

1. Check network:

# Ping device
ping -c 10 192.168.1.100

# Should see < 50ms

2. Check device load:

curl http://192.168.1.100/api/system/metrics

# Check CPU usage and free memory

3. Reduce polling frequency:

  • If using REST sensors in HA
  • Increase scan_interval
  • Use MQTT for real-time updates

4. Update firmware:

  • Performance improvements in newer versions

Memory Issues

Symptoms:

  • Device crashes
  • Reboots randomly
  • "Out of memory" errors

Solutions:

1. Check free memory:

curl http://192.168.1.100/api/system/metrics

Should have >20KB free.

2. Reduce features:

# Disable unused features
WebSocket: Disabled  # If not needed
Logging Level: Warning  # Less verbose

3. Factory reset:

  • May clear corrupted data
  • Backup config first

Getting Help

Collect Diagnostic Information

Before contacting support:

1. Device info:

curl http://192.168.1.100/api/status > device-status.json

2. Logs:

curl http://192.168.1.100/api/system/logs?limit=100 > device-logs.txt

3. Configuration:

curl http://192.168.1.100/api/config/export > device-config.json

4. Network info:

ping -c 10 192.168.1.100 > network-test.txt

Support Channels

Warranty & RMA

Hardware issues may be covered under warranty:

  1. Check purchase date (1-year warranty)
  2. Gather diagnostic info
  3. Contact support with:
    • Order number
    • Problem description
    • Troubleshooting attempts
    • Diagnostic files

Next Steps

Still stuck? Our support team is here to help: support@walaworks.com

Previous

—

Next

—