Home/DIY Builds/Offline Voice Assistant on Raspberry Pi 5
Creator demonstratedLocalClaw source-reviewed

Build a Raspberry Pi 5 Offline Voice Assistant

A battery-powered Raspberry Pi 5 assistant with a screen, microphone and speaker that can hear, think and answer locally after the required models are downloaded.

IntermediateComplete build · price variesOffline voice AI
Original demonstration by Jdaie Lin PiSugar built and documented the reference implementation.Qwen3 1.7B for Ollama by Qwen.
Portable Raspberry Pi 5 voice assistant with a small display, microphone, speaker, active cooler and stacked battery board on a dark maker workbench
Original LocalClaw editorial artwork · not a creator thumbnail
Model1.7B class parameters1.4 GB Ollama Q4_K_M package
HardwareRaspberry Pi 5 8 GBWhisplay HAT · PiSugar 3 Plus · active cooling
PurposeOffline voice conversationLocal after models are cached; no cloud API required
Source statusReviewed 2026-09-01Creator demonstrated · not yet LocalClaw tested

Original demonstration

Watch Jdaie Lin build the complete assistant

The tutorial covers the physical stack, Raspberry Pi OS, SSH, Whisplay drivers, the chatbot, Ollama, Whisper, Piper, PiSugar power management, an offline conversation test and automatic startup.

Video: Offline AI on Raspberry Pi 5 — It Talks, Thinks locally without Wi-Fi! (Complete Tutorial) by Jdaie Lin. LocalClaw does not rehost or modify the video.

Hardware gate

Use the Pi 5 8 GB and plan the stack before assembly

The creator recommends 8 GB or more because the combined AI stack uses roughly 4 GB in the demonstrated configuration. Active cooling is essential. The battery, cooler, stackable GPIO header and Whisplay HAT occupy the same compact area, so confirm clearances before tightening anything.

Compute
Raspberry Pi 5 with 8 GB RAM; the creator recommends 8 GB or more
Display and audio
PiSugar Whisplay HAT with LCD, onboard microphones, speaker and button
Battery
PiSugar 3 Plus 5000 mAh for the Raspberry Pi 5 build
Cooling
Active cooler with confirmed clearance around the battery and HAT stack
GPIO spacing
2×20 stackable header/riser long enough to clear the cooler and expose all 40 pins
Storage
64 GB A2 microSD recommended; 32 GB is the practical minimum
Operating system
Current 64-bit Raspberry Pi OS; SSH and network enabled during setup
Offline boundary
Internet required for installation and model downloads, then removable for normal use

Verification boundary: LocalClaw checked the parts and demonstrated flow against the original tutorial, PiSugar hardware documentation and the current Whisplay chatbot, driver and power-manager sources. The commands below use the current maintainer path at the reviewed commits rather than copying an older command transcript from the video. Reviewed runtime commit: ee7301b2f769. LocalClaw has source-reviewed this guide but has not physically reproduced this build.

Parts list

Buy every part for the portable build

These buttons open regional Amazon searches through LocalClaw. Confirm the exact specifications on the seller page before ordering.

01
Required

Raspberry Pi 5 8 GB

Use the 8 GB model shown in the tutorial. The complete Whisper, Ollama and Piper stack uses several gigabytes and should not be presented as a comfortable 4 GB build.

Find on Amazon
02
Required

PiSugar Whisplay HAT

This combines the small LCD, microphones, speaker, RGB LEDs and interaction button used by the assistant. Confirm it includes the speaker and mounting hardware.

Find on Amazon
03
Required for portable use

PiSugar 3 Plus 5000 mAh battery

Choose the Plus 5000 mAh version documented for Raspberry Pi 5, not the smaller 1200 mAh PiSugar 3 intended for lighter boards.

Find on Amazon
04
Required

Raspberry Pi 5 active cooler

Local speech and LLM inference sustain CPU load. Confirm the cooler and its fasteners clear the PiSugar underside and the raised Whisplay HAT.

Find on Amazon
05
Required

2×20 stackable GPIO header

The riser lifts the Whisplay HAT above the cooler while passing all 40 GPIO pins through. Match the pin length and board clearance shown in the video.

Find on Amazon
06
Recommended

64 GB A2 microSD card

Use a reputable card with room for Raspberry Pi OS, build dependencies, the 1.4 GB Qwen package, Whisper weights, a Piper voice and logs.

Find on Amazon
07
Required for setup and charging

Official Raspberry Pi 27 W USB-C supply

Use stable wall power while installing and downloading models. The PiSugar battery makes the finished device portable but still needs a suitable charger.

Find on Amazon

Affiliate disclosure: As an Amazon Associate, LocalClaw earns from qualifying purchases. The original creators do not endorse these purchasing links, and prices or availability may change.

Step-by-step

Assemble, install and prove the assistant offline

The video remains the visual assembly reference. This written path independently organizes the current official commands, pins the reviewed chatbot revision and adds checks before each long download.

01

Flash Raspberry Pi OS with SSH enabled

Use Raspberry Pi Imager to write current 64-bit Raspberry Pi OS to the microSD card. Set a hostname, username, password, Wi-Fi and SSH in Imager before first boot.

  • Use 64-bit Raspberry Pi OS.
  • Keep networking enabled until every package, model and voice file is cached.
  • Record the hostname and login before ejecting the card.
02

Dry-fit the cooler, battery, riser and Whisplay HAT

Install active cooling on the Pi 5, align the PiSugar 3 Plus underneath, add the 2×20 stackable header and seat the Whisplay HAT above the cooler. Check every pin before applying pressure.

  • Disconnect all power before assembly.
  • Never offset the 40-pin connector by one row.
  • Do not bend a cooler fastener unless you understand the mechanical risk shown in the creator video.
  • Confirm the HAT sits level and no metal part contacts the battery board.
03

Install and test the current Whisplay driver

SSH into the Pi, clone the official driver, pin the revision reviewed by LocalClaw, install it and reboot. Run the hardware demo before adding any AI software.

Terminal
git clone https://github.com/PiSugar/Whisplay.git --depth 1
cd Whisplay
git checkout a695240f866257033414697d47c3aa4c5f9b749c
sudo bash install_driver.sh
sudo reboot

Note: After reboot, return to ~/Whisplay/example, install its requirements and run bash run_test.sh. Do not continue until the display, button, LEDs, microphone and speaker pass the hardware test.

04

Install the PiSugar power manager

Install the official release-channel power manager, select the PiSugar 3 model when prompted and confirm that the battery service sees the board.

Terminal
cd ~
wget -O pisugar-power-manager.sh https://cdn.pisugar.com/release/pisugar-power-manager.sh
bash pisugar-power-manager.sh -c release
systemctl status pisugar-server --no-pager

Note: The official manager exposes its local web interface on port 8421. Change its default credentials before exposing that port beyond your trusted LAN.

05

Clone and build the reviewed Whisplay chatbot

Clone the application, pin the current reviewed revision, install its system and Python dependencies, then load the Node environment added to your shell.

Terminal
cd ~
git clone https://github.com/PiSugar/whisplay-ai-chatbot.git
cd whisplay-ai-chatbot
git checkout ee7301b2f7693111ee016f81c48a75d3387a7326
bash install_dependencies.sh
source ~/.bashrc
bash build.sh

Note: The current repository has evolved since the 2025 video. Pinning the reviewed commit keeps the commands and configuration fields on this page reproducible.

06

Install and cache the three offline engines

Install Ollama and pull Qwen3 1.7B, install Whisper and cache its tiny English model, then install Piper HTTP and download one English voice.

Terminal
cd ~/whisplay-ai-chatbot
bash scripts/install_ollama.sh
ollama pull qwen3:1.7b
python3 -m pip install -U openai-whisper --break-system-packages
python3 -c "import whisper; whisper.load_model('tiny')"
python3 -m pip install 'piper-tts[http]' --break-system-packages
mkdir -p /home/pi/piper
cd /home/pi/piper
python3 -m piper.download_voices en_US-amy-medium

Note: The /home/pi paths match the official defaults and the creator setup. If your Raspberry Pi username is not pi, use your actual home directory consistently in .env.

07

Configure the local voice pipeline

Run the official configuration wizard, choose Whisper for ASR, Ollama for the LLM and Piper HTTP for TTS, then verify the critical values in .env.

  • ASR_SERVER=whisper
  • LLM_SERVER=ollama
  • TTS_SERVER=piper-http
  • OLLAMA_MODEL=qwen3:1.7b
  • SERVE_OLLAMA=true
  • WHISPER_MODEL_SIZE_OR_PATH=/home/pi/.cache/whisper/tiny.pt
  • PIPER_HTTP_MODEL=/home/pi/piper/en_US-amy-medium
  • ENABLE_THINKING=false for the first full test
Terminal
cd ~/whisplay-ai-chatbot
whisplay configure
grep -E '^(ASR_SERVER|LLM_SERVER|TTS_SERVER|OLLAMA_MODEL|SERVE_OLLAMA|WHISPER_MODEL_SIZE_OR_PATH|PIPER_HTTP_MODEL|ENABLE_THINKING)=' .env

Note: If the wizard does not expose one of these advanced fields, edit .env directly. Never add a cloud API key for this fully local configuration.

08

Run the chatbot and test the complete audio loop

Start the application in the foreground, press the Whisplay button, speak a short request and wait for the display and speaker response. Keep this foreground test visible until every stage works.

Terminal
cd ~/whisplay-ai-chatbot
bash run_chatbot.sh
Test promptsTell me a short joke.Give me three ingredients for a pizza.What can I do without an internet connection?

Note: The first Whisper and Ollama request is slower because processes and model data are warming up. Thinking mode should remain disabled during this baseline test.

09

Disconnect networking and enable startup only after proof

Stop the foreground process, disconnect Wi-Fi or Ethernet, repeat the same voice request, then install the startup service once the offline test succeeds.

  • Qwen3, Whisper and the Piper voice must already be present locally.
  • A successful disconnected request proves the demonstrated pipeline, not every optional plugin.
  • startup.sh switches the Pi to multi-user mode and disables the graphical desktop.
  • If whisplay-daemon is installed, follow the current repository warning instead of creating a competing legacy chatbot service.
Terminal
cd ~/whisplay-ai-chatbot
bash startup.sh
systemctl status chatbot --no-pager
journalctl -u chatbot -n 100 --no-pager

Expected performance

A real offline assistant with deliberate pauses

Private local voice conversation with sequential speech recognition, text generation and speech synthesis. This is a three-stage CPU pipeline on a small computer: Whisper transcribes, Qwen3 generates and Piper synthesizes. It is private and portable, but it will not respond like a cloud smart speaker.

Combined working memory
roughly 4 GB in the creator's demonstrated configuration
Qwen3 Ollama package
1.4 GB Q4_K_M download for qwen3:1.7b
Response path
Whisper → Ollama/Qwen3 → Piper; each stage adds latency
Practical verdict
Private and portable with visible pauses; not an instant smart-speaker replacement

Troubleshooting

The failures that look mysterious

Most failures are not model failures. Test the Whisplay hardware, each local engine and the final chatbot as separate layers before enabling automatic startup.

The Whisplay screen or audio does not work

Return to the official Whisplay example test. Recheck the 40-pin alignment, SPI/I2C/I2S driver installation and audio device before debugging Ollama or the chatbot.

Ollama answers in the terminal but the chatbot does not

Confirm LLM_SERVER=ollama, OLLAMA_MODEL=qwen3:1.7b and OLLAMA_ENDPOINT=http://localhost:11434 in .env. Run ollama list and curl the local Ollama endpoint before restarting the chatbot.

Whisper downloads again or fails after disconnecting Wi-Fi

Confirm /home/pi/.cache/whisper/tiny.pt exists and WHISPER_MODEL_SIZE_OR_PATH points to that exact file. Cache the model while online before repeating the offline test.

Piper starts but produces no audible response

Confirm both en_US-amy-medium.onnx and its JSON file exist under /home/pi/piper, verify PIPER_HTTP_MODEL uses the matching basename path, then test the Whisplay speaker independently.

The Pi becomes hot, throttles or restarts

Stop the chatbot and inspect cooling, power and GPIO-stack clearance. Use active cooling, a stable supply during setup and do not compress the cooler or battery against another board.

Responses take much longer with thinking mode

Set ENABLE_THINKING=false and restart the chatbot. Thinking produces more tokens and is an optional demonstration mode, not a requirement for a useful offline voice assistant.

startup.sh refuses because whisplay-daemon is present

Do not run two managers for the same hardware. The current project recommends registering the chatbot with whisplay-daemon; use the repository's current daemon path or explicitly stop and disable the daemon before choosing legacy chatbot.service mode.

Sources and credit

Follow the work back to its creators

Jdaie Lin published the complete Raspberry Pi 5 offline build on the PiSugar Studio channel. PiSugar maintains the Whisplay hardware driver, chatbot application and battery manager used by the project. LocalClaw's page is independent and does not imply endorsement by any cited creator, model author or tool maintainer.

License note: The Whisplay chatbot and PiSugar power manager are GPL-3.0; the Whisplay hardware driver and Qwen3 model identify Apache-2.0 licensing. Piper uses GPL-3.0 and OpenAI Whisper uses MIT. LocalClaw links to the original projects and does not redistribute their code, model packages, voice files or video.

Questions

Offline Raspberry Pi voice assistant FAQ

Is this Raspberry Pi voice assistant really offline?

Yes after setup, if Qwen3, the Whisper checkpoint and the Piper voice are already stored locally. Internet is still required to install packages and download those assets. Optional cloud providers or plugins are outside this offline claim.

Why does the guide require a Raspberry Pi 5 with 8 GB?

Jdaie Lin recommends 8 GB or more and reports that the combined AI software uses roughly 4 GB. LocalClaw keeps that demonstrated hardware gate rather than promising a comfortable 4 GB build.

What does the Whisplay HAT add?

It provides the small LCD, microphones, speaker, RGB LEDs and button used for the assistant interaction, avoiding a collection of separate audio and display peripherals.

Can I use a different Ollama model?

Yes, but qwen3:1.7b is the model demonstrated in the tutorial and the only model covered by this guide. Larger models increase memory use and latency; other models may handle thinking or tools differently.

Do I need the PiSugar battery?

No for a desk-only assistant, but yes for the portable build shown in the video. The PiSugar 3 Plus 5000 mAh is the documented Raspberry Pi 5 option.

Has LocalClaw physically reproduced this build?

No. Jdaie Lin demonstrated the finished device. LocalClaw verified the hardware list, current repositories, model package, licenses and installation path, but has not physically assembled this appliance.

← Browse Community DIY Builds