#anyone using openclaw on a raspberry pi
uncut estuary
I usually try to stabilize things during a scenario like this, see below:
openclaw config set agents.defaults.heartbeat.every "0m"
openclaw config set cron.enabled false
openclaw config set gateway.channelHealthCheckMinutes 0
openclaw gateway restart
If the cpu usage drops, then turn them on 1 at a time to find the culprit.
dusky kiln
With new releases, they are heavy, so don't expect arm cores to keep up with it
uncut estuary
If it doesn't the issue could be something else, we'd need to run some commands or do more discovery.
torn pier
I am running it on raspberry pi 4. It had died in the last week or so with new releases. I finally downgraded it to OpenClaw version 2026.4.21. Now it's back!
Previously, I had set up a cron which would check for updates and update it. This cron was set twice a day. It worked great initially, but with 2026.4.22 and later, it was struggling.
I finally investigated and figured out a solution.
uncut estuary
Previously, I had set up a cron which would check for updates and update it. Thi...
Thanks for the issue and your investigation!
shell iris
@marble heron I am running on Raspberry Pi 5 8GB (Arm64/Raspberry Pi OS trixie). Works mostly fine if you adjust timeout values and make sure the vtest/linting/TTDs are running serially, put a heap cap of 4GB and have Openclaw run on NVME PCIE SSD instead of SD Card. If you let it process in parallel it will not have enough headspace and restart 😉
As to Openclaw version, I have not upgraded to 2026.5.2 yet for testing. The latest stable version I tested successfully was 2026.4.26