🔧 Reachy Mini Troubleshooting

Symptoms:

• Connection refused
• Site cannot be reached
• ERR_CONNECTION_REFUSED

Solutions:

1. Verify Reachy is powered on (check power LED)
2. Wait full 60-90 seconds after power on
3. Check both devices are on EXACT same WiFi network
4. Verify not on different bands (2.4GHz vs 5GHz)
5. Disable VPN if active
6. Try direct IP instead of .local (e.g., http://192.168.1.110:8000)
7. Check firewall settings

Symptoms:

• Backend not running error
• Movement commands return errors
• APIs return 422

Solutions:

1. 🔴 CRITICAL: Click the red switch in dashboard to activate backend!
2. Wait 5 seconds after clicking switch for backend to initialize
3. Check ./aurion status shows "Backend: Active"
4. Refresh dashboard and try clicking switch again
5. Power cycle if switch doesn't respond

Symptoms:

• ping reachy-mini.local fails
• Can't resolve hostname
• Name or service not known

Solutions:

1. Use IP address directly instead of .local
2. Add to /etc/hosts: 192.168.1.110 reachy-mini.local
3. Ensure Bonjour/Avahi service is running
4. Check if on corporate network (often blocks mDNS)
5. Try from different device to isolate issue

Symptoms:

• Empty movement lists
• Movements fail to load
• HuggingFace errors

Solutions:

1. Ensure Reachy has internet access for first-time download
2. Movements cache after first use
3. Check if another app is running (only one at a time)
4. Try a simple movement first: simple_nod
5. Restart backend via dashboard switch

Symptoms:

• Intermittent connection
• Works then stops
• Random timeouts

Solutions:

1. Check WiFi signal strength
2. Disable WiFi power saving on Reachy
3. Lock devices to same access point (mesh networks)
4. Check for IP conflicts
5. Use static IP assignment