Choosing the Right Raspberry Pi Power Supply for Always-On OpenClaw Agents

A Raspberry Pi 5 running full CPU load with an NVMe SSD and active cooler pulls roughly 12 watts sustained. Add a Hailo-8L AI accelerator and that rises to 14 to 16 watts, according to 2026 measured benchmarks. That is five times the board's 3-watt idle draw, and it exposes a gap most power supply guides skip over: the difference between a charger that works for hobby projects and one that keeps an always-on OpenClaw agent running for months without interruption.

The problem is not raw wattage. A 65W laptop charger has plenty of total power. The problem is that USB-C Power Delivery negotiation typically offers high wattage at 9V, 12V, or 20V, not at the 5V the Raspberry Pi actually needs. A charger advertising 65 watts at 20V might only deliver 15 watts on its 5V rail. When the Pi draws 5A from a supply rated for 3A at 5V, voltage sags below the board's under-voltage threshold, the firmware throttles the CPU, and the board reboots.

For a Pi running as a media center, that shows up as a brief stutter. For an OpenClaw agent that has been processing tasks for six hours, it means lost work, corrupted state files, and an agent that restarts with no memory of what it was doing when power dropped.

The Raspberry Pi Foundation built the official 27W USB-C power supply for exactly this scenario. It outputs 5.1V at 5A with a thick 17AWG cable, leaving headroom above the under-voltage threshold even under peak load. At roughly $12 from authorized resellers, it is the cheapest reliability upgrade for any Pi deployment that needs to stay up.

The rest of this article covers measured power consumption under different workload profiles, how the official PSU compares to generic chargers, how to detect and monitor under-voltage events, UPS options for surviving outages, and how to keep your agent's output safe in cloud storage when power does fail.

Understanding exact power draw helps you choose a supply with real margin, not just one that looks adequate on paper. These numbers come from measured benchmarks, not manufacturer estimates.

The base Raspberry Pi 5 board draws about 3.0 watts at idle with Wi-Fi active and no display connected. Under full CPU load across all four Cortex-A76 cores, consumption rises to approximately 8.8 watts. With an NVMe SSD connected through the M.2 HAT+, add another 1 to 2 watts. An active cooler fan adds roughly 0.5 watts. The Hailo-8L AI HAT+ adds 2 to 3 watts during active inference.

Here is what that looks like across common agent workload profiles:

• Idle agent waiting for tasks: 3.0 to 3.5W
• Light processing (API calls, file I/O, network polling): 5 to 7W
• Full inference with peripherals: 12 to 16W
• Peak burst (CPU + GPU + NVMe + AI HAT + cooler): up to 16W

For comparison, the Raspberry Pi 4 draws about 2.9W at idle and 6.4W under full CPU load. The Pi 5 consumes roughly twice as much under load, which means a power supply that handled a Pi 4 agent reliably may not be adequate for a Pi 5 running the same workload.

The USB port power budget also shifts with the supply. When the Pi 5 detects a USB-C PD supply (like the official 27W unit), it raises the combined USB port power limit from 600mA to 1.6A across all four ports. If you are running a USB SSD, USB camera, or other peripheral alongside your agent, you need that higher allocation. A non-PD supply keeps you at 600mA, which may not power an external drive at all.

One detail that trips people up: sustained load and burst load draw different amounts, but only sustained load matters for supply selection. A Pi 5 might briefly spike to 16W during a CPU-intensive parsing step, then drop to 5W while waiting for an API response. Your supply needs headroom for the spike, not just the average. If your agent alternates between inference and idle, the average draw might be 6W, but a supply that maxes out at 10W will still trigger under-voltage during every inference burst.

Thermal behavior also interacts with power. The Pi 5's CPU throttles at 85°C to prevent damage, which actually reduces power draw. But if your supply is borderline, the sequence is worse: under-voltage throttles the CPU, which reduces cooling fan speed (since the fan controller is tied to CPU temperature), which raises temperature, which throttles harder. A proper supply breaks this cycle before it starts.

One number worth remembering: a Pi 5 drawing 3W continuously costs roughly $7 to $8 per year in electricity at $0.30/kWh. Even at full load, the annual power cost stays under $50. The electricity bill is never the reason an always-on Pi agent fails. The power supply is.

The Raspberry Pi Foundation sells a 27W USB-C power supply designed specifically for the Pi 5. Here is what separates it from the USB-C charger already in your desk drawer.

Official 27W PSU specifications:

• Output: 5.1V at 5.0A (25.5W on the 5V rail)
• USB PD profiles: 9V/3A, 12V/2.25A, 15V/1.8A
• Cable: 1.2m, 17AWG conductor
• Average efficiency: 89%
• Production guaranteed through January 2035

The important number is 5.1V, not 5.0V. That extra 0.1V provides headroom above the Raspberry Pi's 4.63V under-voltage detection threshold, even when cable resistance and load transients pull voltage down from the nominal output. Most phone chargers output exactly 5.0V, which leaves almost no margin when the Pi draws 5A continuously.

Cable gauge matters more than most people expect. The official supply uses 17AWG wire, which is noticeably thicker than the 24 to 28AWG cables bundled with most phones and tablet chargers. A thin cable carrying 5A can drop 0.3V or more before current reaches the Pi's USB-C port. That single cable loss can push voltage below the 4.63V threshold on an otherwise capable charger.

Common scenarios where generic chargers cause problems:

• Phone chargers supporting USB PD often deliver high wattage at 9V or 12V but only 3A at 5V. The Pi 5 negotiates for 5V first and may not get enough current at that voltage.
• Laptop chargers (65W, 100W) typically work at 5V/3A but not 5V/5A, because they prioritize higher voltage profiles for the laptop they were designed to charge.
• Multi-port chargers split total wattage across active ports. A "65W" charger may only deliver 15W per port when two devices are connected.
• Cables with resistance above 200 milliohms cause measurable voltage sag regardless of the charger's rated output.

For an always-on OpenClaw deployment, the official 27W PSU is the recommended choice. At roughly $12 from authorized resellers, it costs a fraction of the time you will spend debugging intermittent crashes with a generic alternative.

If you already have a third-party USB-C PD supply that outputs 5V at 5A or higher, it can work. Verify two things before deploying: that the supply actually negotiates 5V/5A with the Pi (not just 5V/3A with higher voltage profiles available), and that the cable is 18AWG or thicker. A USB power meter, available for about $15, shows exactly what the Pi is receiving at the connector under load. Plug it inline, run your agent workload for an hour, and confirm voltage stays above 4.8V throughout. If it dips below 4.7V at any point, switch supplies.

Store your OpenClaw agent output where power failures cannot reach it

Free 50GB workspace with MCP server access. Push agent output to versioned cloud storage, no credit card required.

Sign Up Free

Even with the right power supply, voltage can sag. Ambient temperature spikes increase cable resistance slightly. A new USB peripheral plugged in mid-session raises current draw. Mains voltage dips during storms or in buildings with aging wiring. You need to know when it happens, not discover it after your agent has been throttled for hours.

The Pi 5's PMIC monitors input voltage continuously against a fixed threshold at 4.63V. When voltage drops below that level, the firmware responds in three ways: a lightning-bolt icon appears on the desktop (useless for headless deployments), the kernel logs an under-voltage event, and CPU and GPU frequencies are throttled to reduce current draw.

You can check the throttling state at any time:

vcgencmd get_throttled

A return value of 0x0 means no issues since boot. 0x50000 means under-voltage occurred at some point since boot but is not active right now. 0x50005 means under-voltage is happening at this moment and the CPU is actively throttled.

For a headless agent, the lightning-bolt icon is invisible. Build a voltage health check into your agent's startup or periodic monitoring routine. Poll get_throttled every few minutes and log any non-zero value. If your agent's inference tasks are taking longer than expected or network calls are timing out, under-voltage throttling is the first thing to rule out.

Adding UPS protection for 24/7 operation:

A quality power supply solves voltage stability. A UPS solves power continuity. For an OpenClaw agent that runs around the clock, you need both.

UPS HATs for the Raspberry Pi typically use one or two 18650 lithium cells and connect through the GPIO header. When mains power is present, they charge the batteries and pass power to the Pi. When mains fails, they switch to battery without resetting the board.

When choosing a UPS HAT, look for these features:

• Runtime: A single 3200mAh 18650 cell provides roughly 5 to 8 minutes under a typical Pi workload. That is enough for a graceful shutdown but not enough to ride out a real outage. Two cells in parallel roughly double the window.
• I2C telemetry: Better HATs expose battery voltage, current, and charge percentage over I2C. This lets your agent read its own power state and initiate a safe shutdown before the battery dies, rather than crashing unexpectedly.
• Pi 5 compatibility: The Pi 5 changed its PMIC and power delivery behavior. Confirm the vendor explicitly lists Pi 5 support before buying, since boards designed for the Pi 4 often cannot deliver adequate current to the newer model.
• Safe shutdown GPIO: A dedicated GPIO pin that signals "power is about to cut" gives your agent a hardware-level fallback when software monitoring is unresponsive.

Several vendors make Pi-compatible UPS boards worth evaluating. The Sixfab Power Management UPS HAT provides true uninterruptible switching with I2C telemetry and explicit Pi 5 support. The Waveshare UPS HAT is a budget option with basic switchover. The Geekworm X1200 uses dual 18650 cells for longer runtime and includes automatic power-off when the Pi shuts down, preventing unnecessary battery drain.

For extended outages beyond what a HAT battery can handle, consider an external 12V UPS with a buck converter to 5.1V. This separates battery capacity from the Pi's form factor and can provide hours of runtime instead of minutes. A small 12V/7Ah lead-acid UPS (the kind used for alarm systems) with a 5.1V/5A buck converter can keep a Pi running for 8 to 12 hours, which is enough to survive most residential power outages.

The right power supply and UPS protect the hardware. Protecting the agent's work requires a different approach: getting output off the device before power fails.

An OpenClaw agent on a Pi might be generating reports, collecting sensor readings, processing images, or coordinating tasks across a network. All of that work lives on the Pi's SD card or NVMe drive until it's synced elsewhere. An unclean shutdown risks corrupting that storage. Even a clean shutdown means the data is only as available as the Pi itself.

The practical answer is cloud-backed persistence. Store agent output in a workspace that survives regardless of what happens to the Pi's power rail.

Local-first storage options:

• Local NAS (Synology, TrueNAS): Keeps data on your network with RAID redundancy, but does not help if the power outage takes down the NAS too.
• S3 or Google Cloud Storage: Reliable and globally available, but requires manual configuration for each agent and does not include indexing or search.
• Dropbox or Google Drive: Familiar, but not designed for programmatic agent access at scale.

Cloud workspace storage:

Fast.io provides free persistent storage built for agent workflows. The free plan includes 50GB of storage, 5,000 monthly credits, and 5 workspaces, with no credit card or trial expiration. Agents interact through the Fast.io MCP server or the REST API, so your OpenClaw agent can push files to a cloud workspace as part of its normal output flow rather than batching everything to local disk.

This setup helps in two specific scenarios.

Continuous sync: Instead of writing output to the SD card and hoping it survives, configure your agent to write to Fast.io storage as its primary output target. Each file is versioned automatically. When Intelligence Mode is enabled on the workspace, uploaded files are indexed for semantic search and AI-powered Q&A, so you can query past agent output from any device.

Pre-shutdown flush: When the agent detects a power event through UPS telemetry or a GPIO signal, it pushes its most recent state to Fast.io before initiating shutdown. The Fast.io API supports chunked uploads, so even partially uploaded files can be resumed on the next boot.

For teams running multiple Pi-based OpenClaw agents, Fast.io workspaces serve as a shared coordination layer. Each agent pushes to its own workspace. Humans review output through the web interface or Ripley AI chat, which can answer questions about uploaded documents with citations. When a project is complete, the workspace can be transferred to a human owner while the agent keeps admin access for future runs.

The electricity cost of running a Pi 5 always-on is under $50 a year. The storage cost can be zero. The real cost of an always-on deployment is the time you spend recovering from preventable failures, and the right power supply eliminates the most common one.