This document provides core debugging methods, storage management, and network download strategies for Reachy Mini robot.
- Core Debugging Methodology
- Storage Crisis Management
- Download and Network Strategy
- Configuration Persistence
When the background service (Systemd) cannot work normally due to network or configuration issues, do not reboot blindly. Follow these "three steps" to take control.
Stop the background daemon service to free up ports (such as 8000) and resources.
sudo systemctl stop reachy-mini-daemon.serviceEnsure no residual processes are occupying ports (this is the main cause of Address already in use).
# Check ports
sudo lsof -i :8000
# Kill process
sudo kill -9 <PID>
# Quit residual screen
screen -X -S <SessionID> quitRun manually in the foreground, using tools (Proxychains) and environment variables (Export) to inject network capabilities and view error logs directly.
# Activate environment
source /venvs/mini_daemon/bin/activate
# Complete dependencies (fix camera streaming)
export GST_PLUGIN_PATH=$GST_PLUGIN_PATH:/opt/gst-plugins-rs/lib/aarch64-linux-gnu/
# Start with proxy (bypass network)
proxychains4 python -m reachy_mini.daemon.app.main --wireless-version --no-autostartThe Raspberry Pi 16GB card is easily filled, causing installation failures (No space left on device).
# Macro view
df -h
# Find large folders
du -sh /home/pollen/.cache/* | sort -hrAfter installation fails, you must clean these caches before retrying:
# Clean pip installation cache
rm -rf /home/pollen/.cache/pip
# Clean uv download cache
rm -rf /home/pollen/.cache/uv
# Clean HuggingFace model cache
rm -rf /home/pollen/.cache/huggingfaceFor downloading Python libraries and HuggingFace models in domestic network environments, we summarize three strategies that need to be flexibly switched.
| Strategy | Use Case | Pros | Cons | Key Configuration Commands |
|---|---|---|---|---|
| A. Self-built/Private Mirror | First choice. Download via w0x7ce.eu |
Fastest, no proxy needed | May lack packages (e.g., red_light file not found) |
export PIP_INDEX_URL=https://pypi.w0x7ce.eu/simpleexport HF_ENDPOINT=https://hf.w0x7ce.eu |
| B. Public Mirror | Alternative. Tsinghua/HF-Mirror | Fast, relatively complete | Occasional sync delay | export PIP_INDEX_URL=https://pypi.tuna.tsinghua.edu.cn/simpleexport HF_ENDPOINT=https://hf-mirror.com |
| C. Official Source + Proxy | Fallback. When mirror lacks packages | Most stable, guaranteed packages | Speed limited by proxy bandwidth, slow | 1. Clear variables: unset HF_ENDPOINT2. Start with proxy: proxychains4 python ... |
When manual debugging is normal (network works, packages downloaded), and you want the robot to work normally on boot in the future, you need to modify the Systemd service file.
1. Edit service file:
sudo systemctl edit reachy-mini-daemon.service2. Fill in content (example):
[Service]
# Network proxy (allow daemon to access internet)
Environment="http_proxy=http://192.168.137.1:7890"
Environment="https_proxy=http://192.168.137.1:7890"
Environment="no_proxy=localhost,127.0.0.1,reachy-mini.local"
# Required runtime libraries
Environment="GST_PLUGIN_PATH=/opt/gst-plugins-rs/lib/aarch64-linux-gnu/"3. Apply and restart:
sudo systemctl daemon-reload
sudo systemctl restart reachy-mini-daemon.serviceNow you have reverted to "Strategy C (Official Source + Proxy)" and are re-downloading red_light_green_light.
If this download succeeds and you want to play with this robot long-term, it is strongly recommended to:
- Buy a 64GB SD card (clone the system over)
- Or plug in a USB drive and migrate
/venvsto the USB drive to completely solve space anxiety