Get started
Deploying to the robot·
How the code reaches the CM4 (rsync, not git), which venv it lands in, how to restart only what you touched, and how to know it came back.
In 10 seconds
~/tiny-the-reachy/on the CM4 is an rsync target, not a clone.- Python goes into Pollen's
/venvs/apps_venv;/venvs/mini_daemonis hands-off. rsync, then restart only what you touched.
Where things live·
| on the CM4 (Debian 13, 4 GB, 14 GB SD) | what |
|---|---|
~/tiny-the-reachy/ |
this repo, rsync'd — not a git repo |
~/tiny-the-reachy/.env |
keys — never in git |
~/.reachy-dashboard.env |
REACHY_TOKEN, REACHY_REG_TOKEN, REACHY_RP_ID |
~/.tiny-mcp.env (600) |
the fleet token |
/venvs/apps_venv |
Pollen's Python 3.12 — install into it |
/venvs/mini_daemon |
the daemon's — hands off |
~/tts-venv + ~/tiny-tts/ |
Piper TTS |
~/.local/node + ~/.local/lib/tiny-mcp |
node 22 + the MCP server |
~/.config/systemd/user/ |
the eight units |
~/.cloudflared/ |
tunnel credentials |
Ship a change·
rsync -az --delete --exclude .git --exclude .env --exclude node_modules \
--exclude 'dashboard/frontend/src' --exclude '__pycache__' \
./ pollen@reachy-mini.local:tiny-the-reachy/
ssh reachy 'systemctl --user restart tiny-voice tiny-telegram tiny-thinker'
A voice restart drops the current conversation.
Verify it came back·
ssh reachy 'systemctl --user is-active tiny-voice tiny-telegram tiny-thinker reachy-dashboard reachy-tunnel'
curl -s localhost:8097/api/health | jq '{daemon: .daemon.state, camera: .camera.fps, fds: .pressure.fds}'
Network and constraints·
- Wi-Fi: home first, hotspot
neon_netfallback;reachy-mini.localon either. :8000is unauthenticated — never exposed; the tunnel publishes:8097.- Disk 89 % full:
df -h /before anypip install. - Load ~3 of 4 cores; tracking +1.5 —
Fturns it off when the temperature pill goes amber. - Camera is imx708 behind libcamera:
cv2.VideoCapturesees nothing — use the daemon's IPC socket. journalctl --userfinds nothing:journalctl _SYSTEMD_USER_UNIT=tiny-voice.service.
First-time setup on a fresh CM4·
- Flash Pollen's image, join Wi-Fi,
curl localhost:8000/api/daemon/status. ssh-copy-id pollen@reachy-mini.local; change the factory password.- Raise the daemon's fd limit first:
- rsync;
/venvs/apps_venv/bin/pip install -r requirements-robot.txt. cp scripts/systemd/robot/*.service ~/.config/systemd/user/;loginctl enable-linger pollen; enable the units.- Dashboard:
~/.reachy-dashboard.env,dashboard/deploy/sync.sh, enrol your passkey — the gate is open until the first one (TOFU). - Tunnel:
cloudflared tunnel create reachy+ user unit — after step 6. - Optional: Piper, tiny-mcp token, watchdog.