20 September 2022 / Last updated: 20 Sep 2022

Enabling deep sleep for your Raspberry Pi project

Single board computers (SBCs) are awesome, small, low-power devices, often with wireless connectivity, which makes them ideal for simple battery operated projects.
However, when calculating your energy budget, you often come to realize they are not quite low power enough to accommodate small batteries running over a long time (multiple days/months). We often don't need full-time availability, so why not put our computer to sleep to improve our project battery life?
In this article, I will show you how I created the balenaBlock ‘Morpheus’ to give you a simple approach to enable deep-sleep capability on your next battery powered Raspberry Pi (or any SBC-powered) project.

The study case

To demonstrate how it works, I have used the BalenaLabs Inkyshot project, which perfectly fits the intermittent operation, battery operable use case.
Here’s a quick overview of what Inkyshot does, the project at startup will connect to the internet, pull a new inspirational quote, or your local weather, and then will update the eInk display, this process is repeated once in a while (generally once every hour), staying idle the rest of the time.
This project is perfect for battery operation because eInk display retains the display without power, which allows us to power down the system entirely to save battery.

Bill of materials

To reproduce this project, the hardware you will need:
  • A Raspberry Pi compatible SBC,
  • A SD card,
  • A Raspberry Pi Pico micro-controller board,
  • A voltage regulator with enable pin (we used Weewooday-5825 found on Amazon, but you can also convert a LM2596S kit),
  • A Inky pHat or Waveshare 2.13" eInk display module,
  • 2 USB-A to Micro-USB cables (or one + one A to C if using a Pi4),
  • A power source in the 6-12V range, with at least 1A capability (depending on the Raspberry you chose),
  • A way to connect to your power source (alligator clips, barrel jack...),
  • A perf board to mount everything together (optional).
You will also need:
  • A soldering iron,
  • Some solder,
  • Some wires to connect everything.
The software you will need:

Our goal

To keep power consumption as low as possible, the best approach is to:
  1. Start our system,
  2. Connect to the internet (optional, depending on the project requirement),
  3. Load our project state from storage (optional, depending on the project requirement),
  4. Do our project processing, updates, communications...,
  5. Program our next wake up conditions,
  6. Go to deep sleep to preserve as much power as possible,
  7. Repeat from [2] on wake-up.
If we apply it to our use-case, we want to:
  1. Start our system at power-up,
  2. Connect to the internet,
  3. Pull our data and update the display,
  4. Program a 1h sleep period,
  5. Go into deep sleep,
  6. Repeat from [1].

The problem

Performing this operation cycle is not natively supported on RaspberryPi’s, they can't go to low power mode. The only way to drastically reduce power consumption is to shut down the SBC and cut down the power supply. Once the system is shut down, you need manual/external intervention to power it back on.

Proposed solution: Morpheus

To reduce the power consumption, a common approach in embedded systems is to cut the power supply on the main energy hungry components. To do so, we will use an ultra low power external circuit able to keep track of the time, communicate with the Raspberry Pi, and control its input power supply.
Here enters Morpheus.
Morpheus (named after the greek god of sleep and dreams), is a Raspberry Pi Pico based project designed to interface between your Raspberry Pi power supply and your Raspberry Pi. I've developed Morpheus as a balenaBlock to help you integrate it in your own projects.


The Raspberry Pi Pico (called Pico here-after) is a $4 Micro-Controller Unit (MCU) development board, powered by an ultra low power 133MHz Dual Cortex-M0+ processor, with 2MB Flash storage for the program and 264kB of internal RAM and USB communication capabilities. This doesn't 0 much compared to the Gigabytes of RAM and storage of the Raspberry Pi 3 (called Pi here-after), and to its multi GHz processors, but this is plenty enough to turn ON and OFF a power supply, keep track of time or read sensors data... and all this for a fraction of the Pi power budget (450mW under full load, down to 6.5mW in sleep mode, compared to the 10+W rating of the Raspberry Pi 4 without sleep capability).
The final wiring will follow this diagram:
As the Pico is capable of USB communication, it will be connected to the Pi via USB cable for communication (Pink wire). However, as the Pi power supply will be cut, it also needs an external power input of its own.
Thanks to the clever design of this tiny board, a VSYS pin is exposed on its headers, and is a 5V power input, diode protected from the VBUS input (the USB bus power input). This means if you power the board using a 5V power supply on VSYS, it will keep running even when the Pi is OFF, and it won't send power to it through the USB port. This is done using the Red wire and the 5V voltage regulator (here a 7805, but a higher efficiency one should be preferred).
Next, we want to connect one of the GPIO (General Purpose Input/Output) pins of the Pico to the control input of the Pi power supply (with Green wire). Note in the diagram we are using a BC547 NPN transistor in-line to invert the signal, as the LM2596S control input is active low.
We chose GPIO 2 for this purpose, as GPIO 0 and 1 are reserved for the default serial communication bus.
We might want to wake-up the Pi using a button press (or any ON/OFF switching mechanism, like a door sensor or a pressure plate). If this is the case, you can connect the switch between GPIO 3 (Cyan wire from the Pico) and GND (Blue wires).
The output of the controlled Pi power supply (Orange wire) is connected to a USB type A connector for convenience, but you also can connect directly to the 5V pin on the Pi header, to a cut Micro-USB wire if preferred.
Note that Yellow wires are the 12V power input for the whole project, and should be connected to a 12V, 1.5A capable power source.


1. Setting up the MCU
First things first: we have to program the Pico with the Morpheus Firmware.
  1. Start by downloading the pre-complied UF2 File.
  2. Then, connect the Pico to your computer with a USB cable, while keeping the BOOTSEL button pressed. A new USB disk drive called RPI-RP2 should appear.
  3. Drag the UF2 file to the disk drive, it should automatically disappear in 3 to 10 seconds.
  4. When the disk has disappeared, disconnect the Pico from your computer, it is ready to go.
2. Prepare the hardware
Second step is to build the project is to create the hardware assembly according to the Architecture diagram.
IMPORTANT NOTE: You should set the correct output voltage (5V) using a multimeter BEFORE connecting the supply to the Raspberry Pi.
3. Adding the block to your project
Then, you can add the morpheus-serial block to your project. Add the following code to your docker-compose.yml file:
image: bh.cr/g_aurelien_valade/morpheus-serial
io.balena.features.supervisor-api: '1'
io.balena.features.balena-api: '1'
io.balena.features.sysfs: '1'
io.balena.features.kernel-modules: '1'
privileged: true
- "SERIAL_PORT=/dev/ttyACM0"
- "/dev/ttyACM0:/dev/ttyACM0"
- "5555"
You can adjust the SERIAL_PORT variable value, and the shared device if needed, but those should work fine with our configuration (not that the SERIAL_PORT variable is pointing to the shared device).
4. Using the API
The morpheus block exposes a REST API on its TCP port 5555. The API documentation exposes available commands. This might be obvious but something here about why you would need to use the API?
5. Using the CLI script
To help with the Morpheus API access, you can add the morpheus.sh helper script to your project.
Ensure the file will be copied to your application container and will be executable. In the inkyshot project, we do it by adding these lines after the COPY block of the inkyshot/Dockerfile file:
COPY morpheus.sh .
RUN chmod +x morpheus.sh
Then, add the MORPHEUS_ADDR environment variable to your application container, pointing to the serial block (in docker-compose.yml):
- "MORPHEUS_ADDR=morpheus-serial"
Finally, call the morpheus.sh script when your application is ready to sleep, ask the supervisor to halt the device and start a wait loop.
For inkyshot we replaced the cron part of the inkyshot/start.sh script by the following code:
Request sleep for 1h
./morpheus.sh -a ${MORPHEUS_ADDR} -w TimeSleep 1800
Clean turn-off
curl -X POST --header "Content-Type:application/json" \
Prevent from quitting
while :
sleep 1h


In order to qualify the consumption improvement on this system, we did some measurements on a standard Inkyshot project, and on an Morpheus modified one.

Measurement method

In order to measure the power consumption, we hooked a 0.47Ohms resistor in series with the 12V power supply, we then measured the drop voltage across that resistor during operation. The tested hardware is:
  • A Raspberry Pi Pico running Morpheus Firmware v0.1.0,
  • A Raspberry Pi 3 B+ running the project,
  • A Waveshare 2.13" EInk display Pi Hat,
  • A controlled and un-controlled (for the Pico) 5V power supply composed of 2 independent Weewooday-5825 modules.

Standard Inkyshot project

After a high-intensity start-up phase, the consumption settles around 150mA on the 12V line with regular short 250mA spiker, which represents an average consumption of a bit less than 2W. This value is not affected much by refresh rate.

Modified Inkyshot project

The main difference with this project is that we have two main consumption profiles.
The total boot-up to shutdown time on the Pi is about 150 seconds, with a main consumption phase of 105 seconds averaging 168mV. This corresponds to about 360mA under 12V which is about 4.3W. For the other 45 seconds, the power is ramping up and down and can be averaged to half that power.
Which makes an activation energy budget of
4.3W 105s + 2.15W 45s = 548J = 15.23Wh
This cycle is repeated every 30 minutes, with a power consumption during the sleep phase of 14mA under 12V, which equals 0.17W, with a total power over 30minutes of 0.085Wh.
The total average consumption of this version is about 0.438W for our 30min sleep cycle.
If we expand the sleep cycles to one hour instead of 30 min however, we get an average consumption of 0.309W, the refresh rate having a huge impact on power consumption.
Initially, the inkyshot project is designed to update only once a day. With this setting, the benefit is even greater: the average power consumption drops to 0.176W.

Equivalent battery life

The battery life will vastly depend on a large number of factors, starting with:
  • The battery type, voltage and capacity,
  • The controlled power supplies efficiency and sleep leakage current,
  • The time your project needs to be active to process its data,
  • The frequency at which you wake up your project,
  • The power consumption of external components/add-on cards you are using...
For our use case, with a 30min sleep period, and with the selected components we have, we can approximate:
Battery: 12V 7.2Ah lead battery
  • Without Morpheus: 43 hours
  • With Morpheus (30 mins): ~197h = ~8days
  • With Morpheus (60 mins): ~279h = ~11.6 days
  • With Morpheus (24h): 490h = ~20.4 days
Battery: 2xCR18650: 7.2V 3Ah
  • Without Morpheus: 10 hours
  • With Morpheus (30 mins): 49 hours
  • With Morpheus (60 mins): ~70 hours
  • With Morpheus (24h): ~122h = ~5 days
Note: These values are broad approximations based on nominal values, not taking into account efficiency variation with voltage, nor voltage variation during the battery life cycle.


We saw that adding a deep sleep capability to your project is a major improvement for battery operation, giving in our use-case scenario a x5 to x7 improvement in battery life. In order to be effective, you still have to finetune your project life-cycle. As we can see, the refresh rate has a major impact on the battery life when sleeping.
One of the main surprises for me during the tests was the amount of power consumed by the start-up process of the Pi. The Pi consumes about twice as much power when starting than in normal idle state (as observed from the original Inkyshot test). This, coupled with the start-up time of about 100 seconds makes the bootup process draw most of the energy of the project when using Morpheus. This alone could make the project irrelevant for short sleep periods. At this point, finding a way to speed-up the startup process could be the best way to improve the project battery life (still considering the Pi sleeps using Morpheus).
To integrate Morpheus into your project, you still have to keep in mind the following considerations:
  • As the system state is lost on every power down, you should load/save the state on disk (or other method),
  • You may want to keep the system running while updates are pending (this is done with the -w flag on the helper script).


Morpheus is still in active development, and we already see some improvement to consider down the road:
  • Putting the Pico in deep sleep to preserve even more power,
  • Shutting down Pico USB while the Pi is not powered, which should also improve power consumption,
  • Adding other sources of wake up (I2C sensor threshold value...),
  • Using other low power MCUs to do the deep sleep with other capabilities (Pico W, ESP32C3...).
    If you come up with other ideas, please raise an issue on the project Morpheus Github Page.


You can find here the links to all relevant used projects:
by Aurélien ValadeHardware and IoT hacker