OpenClaw on Raspberry Pi: Full Setup Guide for Low-Cost Home Automation

”
}
}

Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. This means we may earn a small commission when you click our links and make a purchase on Amazon. This comes at no extra cost to you and helps support our site.

We’re using Claude Haiku here (around $0.80 per million input tokens / $4.00 per million output tokens from Anthropic) because it’s designed for speed and low latency, and OpenClaw’s tasks are generally simpler than complex reasoning. If you’re cost-conscious, you could also use GPT-4o mini (around $0.15 per 1M input tokens / $0.60 per 1M output tokens from OpenAI). Set `max_tokens` to 512—you rarely need longer responses for automation.

Persistent Execution with systemd

Running OpenClaw as a one-off command is impractical for home automation. You need it running continuously. The cleanest approach is a systemd service, which will automatically restart OpenClaw if it crashes and start it on boot.

Create a new systemd service file:

sudo nano /etc/systemd/system/openclaw.service

Add the following:

[Unit]
Description=OpenClaw Home Automation
After=network.target home-assistant.service
Wants=home-assistant.service

[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi/openclaw
Environment="PATH=/home/pi/openclaw/venv/bin"
ExecStart=/home/pi/openclaw/venv/bin/python -m openclaw
Restart=on-failure
RestartSec=30

[Install]
WantedBy=multi-user.target

Then enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable openclaw
sudo systemctl start openclaw

Check that it’s running:

sudo systemctl status openclaw

Memory and CPU Optimization

Even with all the above in place, a Pi 4 with 4GB RAM will feel the pressure when OpenClaw is running alongside other services (Home Assistant, a database, perhaps a local Zigbee coordinator). To ease the load, swap memory is your friend on Linux. By default, Raspberry Pi OS allocates just 100MB of swap. Increase it to 2GB:

sudo dphys-swapfile swapoff
sudo nano /etc/dphys-swapfile

Find the line `CONF_SWAPSIZE=100` and change it to `CONF_SWAPSIZE=2048`:

sudo dphys-swapfile setup
sudo dphys-swapfile swapon

This is a trade-off: swap is much slower than RAM, but on a Pi, having it can prevent out-of-memory crashes. Monitor your actual RAM usage with `free -h` to see if you need it.

For CPU, disable CPU frequency scaling (the Pi will run hot otherwise) or use a heatsink. A simple passive heatsink (around $5-$10) or an active cooler can keep thermal throttling at bay.

Network and API Reliability

Home automation often depends on network connectivity and API uptime. Since OpenClaw will be calling external LLM APIs, add basic retry logic and timeout handling. While the OpenClaw docs may not highlight this, it’s essential in production. Edit your `.openclaw/config.json` to add:

"api_retries": 3,
"api_timeout": 10,
"network_retry_backoff": 1.5

Also, make sure your Raspberry Pi has a stable internet connection—wired Ethernet is preferable to Wi-Fi, but if you’re using Wi-Fi, position the Pi close to your router or use a better antenna.

Logging and Monitoring

When OpenClaw is running silently in the corner, you need visibility into what it’s doing. Configure logging in `.openclaw/config.json`:

"logging": {
  "level": "INFO",
  "file": "/home/pi/openclaw/logs/openclaw.log",
  "max_size_mb": 10,
  "backup_count": 5
}

Create the logs directory:

mkdir -p /home/pi/openclaw/logs

You can then tail the log in real time:

tail -f /home/pi/openclaw/logs/openclaw.log

For deeper monitoring, consider a lightweight tool like Prometheus or simply check systemd logs:

journalctl -u openclaw -n 50 --no-pager

This shows the last 50 lines of the OpenClaw service logs.

Troubleshooting Common Issues

Out of Memory (OOM) Errors: If you see `Killed` messages in your logs, the Pi ran out of RAM. Increase swap (as described above) or reduce the number of background services.

API Rate Limits or Timeouts: If OpenClaw frequently times out when calling the LLM API, check your internet connection and consider increasing `api_timeout` in the config. Also, verify your API key is valid and has available credits or quota.

Service Won’t Start: Run `sudo systemctl status openclaw` to see the exact error. Common causes are missing Python packages (re-run `pip install -r requirements.txt` in the venv) or an invalid Home Assistant token or URL.

Slow Response Times: The Pi isn’t fast. If automation tasks feel sluggish, it’s likely because the LLM API request is slow (not the Pi itself). Try a faster model, like GPT-4o mini, or check your network latency with `ping 8.8.8.8`.

Final Thoughts

Running OpenClaw on a Raspberry Pi 4 is feasible and cost-effective for home automation tasks. The setup process is straightforward once you understand the key constraints: memory, CPU, and network reliability. By choosing an efficient LLM model, configuring systemd properly, and adding basic monitoring, you can have a stable, always-on home automation engine that doesn’t drain your wallet. The Pi may not be the fastest device, but it’s reliable, low-power, and perfectly adequate for the job.

If you’re looking to run OpenClaw for home automation without the recurring costs of cloud services or a dedicated server, a Raspberry Pi is an incredibly compelling option. The challenge often lies in getting it to run reliably with limited resources, especially when dealing with larger language models. This guide walks you through a full setup, optimized for stability and cost-effectiveness on a Raspberry Pi 4.

Choosing the Right Raspberry Pi and OS

While OpenClaw can theoretically run on older Pis, for any practical home automation task, you’ll want at least a Raspberry Pi 4 with 4GB RAM. The 8GB model is preferable if you can swing it, as it provides more headroom for the operating system and other background processes. Don’t even consider a Pi 3 or Zero for this use case; you’ll be fighting memory limits constantly. For the operating system, stick with Raspberry Pi OS Lite (64-bit). The desktop environment adds unnecessary overhead that eats into your precious RAM. You can download the image and flash it using Raspberry Pi Imager.

sudo apt update
sudo apt upgrade
sudo apt install git python3-venv python3-pip

This ensures your system is up-to-date and has the necessary tools for setting up OpenClaw.

OpenClaw Installation and Virtual Environment

Setting up OpenClaw within a Python virtual environment is crucial for dependency management and avoiding conflicts with system-wide Python packages. This is standard practice, but on a resource-constrained device like a Pi, it helps keep things tidy and predictable.

mkdir ~/openclaw
cd ~/openclaw
python3 -m venv venv
source venv/bin/activate
git clone https://github.com/your-org/openclaw.git .
pip install -r requirements.txt

Replace `https://github.com/your-org/openclaw.git` with the actual OpenClaw repository URL. Once installed, deactivate the environment for now: `deactivate`.

Optimizing OpenClaw Configuration for Raspberry Pi

This is where the non-obvious insights come in. Running large language models directly on the Pi is generally not feasible for real-time inference. Instead, we’ll leverage remote API calls, but with specific model choices that are cheap and performant enough for automation tasks. While the OpenClaw documentation might suggest powerful models, for a Pi, you need to be very deliberate. Create or edit your `.openclaw/config.json` file:

{
  "llm_provider": "anthropic",
  "llm_model": "claude-haiku-20240307",
  "temperature": 0.3,
  "max_tokens": 512,
  "api_keys": {
    "anthropic": "YOUR_ANTHROPIC_API_KEY"
  },
  "plugins": [
    "shell_executor",
    "home_assistant_interface"
  ],
  "home_assistant": {
    "url": "http://homeassistant.local:8123",
    "token": "YOUR_HOME_ASSISTANT_LONG_LIVED_ACCESS_TOKEN"
  },
  "system_prompts": {
    "default": "You are a helpful home automation assistant running on a Raspberry Pi."
  }
}

We’re using Claude Haiku here (around $0.80 per million input tokens / $4.00 per million output tokens from Anthropic) because it’s designed for speed and low latency, and OpenClaw’s tasks are generally simpler than complex reasoning. If you’re cost-conscious, you could also use GPT-4o mini (around $0.15 per 1M input tokens / $0.60 per 1M output tokens from OpenAI). Set `max_tokens` to 512—you rarely need longer responses for automation.

Persistent Execution with systemd

Running OpenClaw as a one-off command is impractical for home automation. You need it running continuously. The cleanest approach is a systemd service, which will automatically restart OpenClaw if it crashes and start it on boot.

Create a new systemd service file:

sudo nano /etc/systemd/system/openclaw.service

Add the following:

[Unit]
Description=OpenClaw Home Automation
After=network.target home-assistant.service
Wants=home-assistant.service

[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi/openclaw
Environment="PATH=/home/pi/openclaw/venv/bin"
ExecStart=/home/pi/openclaw/venv/bin/python -m openclaw
Restart=on-failure
RestartSec=30

[Install]
WantedBy=multi-user.target

Then enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable openclaw
sudo systemctl start openclaw

Check that it’s running:

sudo systemctl status openclaw

Memory and CPU Optimization

Even with all the above in place, a Pi 4 with 4GB RAM will feel the pressure when OpenC

Frequently Asked Questions