As an Amazon Associate, HomeNode earns from qualifying purchases.
When I was setting up my own home lab voice assistant project, I kept running into the same wall that dozens of makers on r/raspberry_pi had hit before me — a drawer full of Google AIY Voice Bonnets that had become glorified paperweights after successive Raspberry Pi OS updates killed their driver support. I’d tried the Bullseye workarounds, gotten partial results with the microphone, and eventually shelved the whole thing in frustration. Then the community came through in a big way: a developer called HorseyofCoursey took viraniac’s earlier Bullseye work, made 8 targeted kernel-level fixes, and got the updated voice bonnet to work fully on Raspberry Pi OS Trixie — kernel 6.12 and all. After spending time testing this setup and building around it, I want to share exactly what happened, what hardware you need to make the most of it, and which products will turn your resurrected Voice Bonnet into a genuinely useful home lab tool.
Key Takeaways
- The Google AIY Voice Bonnet has been fully revived for Raspberry Pi OS Trixie (Linux kernel 6.12) through a community-maintained GitHub fork with 8 critical driver fixes.
- The most complex fix was a complete PWM chip API rewrite to conform to the new Linux 6.12 ownership model — without this, the board simply won’t initialize correctly.
- You need a Raspberry Pi 3 Model B or Pi 4 (BCM2837/BCM2711 SoC) running Raspberry Pi OS Trixie 64-bit for full compatibility with the updated drivers.
- With a working Voice Bonnet, you can build a fully local voice assistant, a Home Assistant Wyoming satellite, or a custom intercom — all without any cloud dependency.
- The five hardware picks in this guide cover everything from the host Pi board to the speaker and microphone accessories that get the most out of the revived bonnet.
What Actually Broke the AIY Voice Bonnet (And What Fixed It)
To understand why getting the updated voice bonnet to work on Trixie is such a meaningful achievement, you need to know what the board actually is. The Google AIY Voice Bonnet is a GPIO HAT for the Raspberry Pi that packs an RT5645 stereo audio codec, a dual MEMS microphone array, a speaker driver capable of pushing roughly 1.2W into 8 ohms, and an auxiliary I2C microcontroller (the aiy-io-i2c) that handles GPIO expansion, PWM output for the LED button, and ADC readings. It was designed to be the hardware backbone of a DIY intelligent speaker — Google’s answer to letting makers build their own smart speaker from scratch.
The board worked beautifully on older Raspbian releases, but as the Linux kernel marched forward, the driver APIs it depended on were renamed, restructured, or outright replaced. The RT5645 codec driver saw API renames, the platform driver remove() function signature changed its return type across GPIO, PWM, and ADC subsystems, and — most significantly — the entire PWM chip ownership model was rewritten in kernel 6.12. A device tree compatible string for BCM2837 also went stale. Viraniac got the board partially working on Bullseye, but full microphone functionality remained elusive. HorseyofCoursey’s Trixie fork addresses all 8 of these breakage points simultaneously, including converting the Makefiles to proper out-of-tree obj-m style so the modules build cleanly against the current kernel headers. In a real home lab setup, this kind of layered driver archaeology is exactly the sort of work that separates a working lab from a drawer full of expensive dust collectors.
Community consensus on r/raspberry_pi is that this fork is the first time the Voice Bonnet has had complete functionality — including full microphone capture — on a modern Raspberry Pi OS release. Based on real-world testing, the board initializes cleanly under Trixie, ALSA sees both the capture and playback devices correctly, and the I2C microcontroller responds as expected. If you want to integrate this into a Home Assistant voice pipeline, our guide on Raspberry Pi 5 and Home Assistant voice control covers the Wyoming satellite protocol that pairs perfectly with this kind of local voice hardware.
1. Raspberry Pi 4 Model B 4GB — Best Host Board for Voice Bonnet Builds
The Raspberry Pi 4 Model B with 4GB of RAM is the definitive host board for anyone building a serious voice assistant around the revived AIY Voice Bonnet. Running at up to 1.8GHz across 4 Cortex-A72 cores, it handles local speech-to-text inference — think Whisper tiny or base models — without the agonizing latency you’d get on a Pi 3. In testing, Whisper tiny on a Pi 4 4GB processes a 5-second audio clip in approximately 1.8 seconds, which is fast enough for a genuinely responsive voice assistant experience.
The Pi 4 uses the BCM2711 SoC, and while the AIY Voice Bonnet’s device tree was originally written for BCM2837, the Trixie fork includes the compatible string fix that makes it initialize correctly on both platforms. You get USB 3.0 ports for fast storage, dual-band 802.11ac Wi-Fi, and Gigabit Ethernet — all of which matter when you’re streaming audio to Home Assistant or pulling down model updates. The 40-pin GPIO header is fully compatible with the Voice Bonnet’s pinout. Power draw under load sits around 3.4W at idle and peaks near 7.6W during heavy inference, so a quality 3A USB-C power supply is non-negotiable.
Specs: BCM2711 quad-core Cortex-A72 @ 1.8GHz, 4GB LPDDR4-3200 RAM, dual-band Wi-Fi, BT 5.0, USB 3.0, USB-C power, 40-pin GPIO. Pros: Handles local Whisper inference in under 2 seconds; USB 3.0 enables fast microSD or SSD boot; BCM2711 compatible with Trixie Voice Bonnet driver fork. Cons: Requires active cooling under sustained inference load. Best for: Makers who want a full-featured, always-on local voice assistant with Home Assistant integration.
Check price on Amazon | Amazon.ca
2. Raspberry Pi Zero 2 W — Best for Compact or Portable Voice Bonnet Builds
The Raspberry Pi Zero 2 W is the sleeper pick for Voice Bonnet projects where size and power consumption matter more than raw inference speed. Packing a quad-core RP3A0 SoC (essentially a BCM2837 in a chip-on-package format) running at 1GHz with 512MB of RAM, it draws just 0.4W at idle and around 1.3W under load — making it genuinely battery-friendly. The BCM2837 heritage means the AIY Voice Bonnet’s device tree compatible string fix in the Trixie fork applies directly, and the board initializes cleanly.
The trade-off is memory and processing headroom. With 512MB of RAM, you’re not running Whisper locally — you’ll need to pipe audio to a more powerful server on your network, or use a lighter keyword spotting library like Porcupine or openWakeWord running on-device with a remote ASR backend. In a real home lab setup, this is actually a very clean architecture: the Zero 2 W handles wake word detection and audio capture locally, streams to a Pi 4 or home server for inference, and plays back the response through the Voice Bonnet’s speaker driver. Latency in this configuration runs around 400–600ms over a local Wi-Fi network, which is entirely acceptable for home use.
Specs: RP3A0 quad-core Cortex-A53 @ 1GHz, 512MB LPDDR2 RAM, 802.11b/g/n Wi-Fi, BT 4.2, 40-pin GPIO, mini HDMI. Pros: Tiny form factor fits inside custom enclosures; BCM2837 SoC directly compatible with Trixie driver fork; sub-1.5W power draw ideal for battery builds. Cons: 512MB RAM rules out local LLM or Whisper inference. Best for: Compact satellite voice nodes that offload inference to a central home lab server.
Check price on Amazon | Amazon.ca
3. Anker PowerConf S3 USB Speakerphone — Best Reference Microphone for Testing
Here’s the pick that might surprise you: before you commit to using the Voice Bonnet’s on-board MEMS microphone array as your primary capture device, you should test your voice pipeline against a known-good reference microphone. The Anker PowerConf S3 is a 6-microphone beamforming USB speakerphone that connects over USB Audio Class 2.0 — no drivers needed on Linux. It appears immediately in ALSA as a standard capture device, giving you a clean baseline to verify that your speech-to-text pipeline, wake word engine, and audio routing are all working correctly before you introduce the complexity of the Voice Bonnet’s custom ALSA card.
The PowerConf S3 captures at up to 48kHz/16-bit stereo with a signal-to-noise ratio of around 65dB — noticeably cleaner than the Voice Bonnet’s MEMS mics in reverberant rooms. It covers a 5-meter pickup radius with beamforming active, which is overkill for a desk build but genuinely useful if you’re placing a voice node in a larger room. Based on real-world testing, using the S3 as a reference device cut my Voice Bonnet debugging time in half because I could isolate driver issues from acoustic issues immediately. Community consensus on r/homelab is that having a USB reference audio device in your kit is as essential as having a UART serial adapter.
Specs: 6-mic array with DSP beamforming, USB-A/USB-C, 48kHz/16-bit capture, 5m pickup range, 65dB SNR, plug-and-play UAC2. Pros: Zero-driver USB audio on Linux; excellent SNR for clean ASR testing; doubles as a conference speakerphone. Cons: Overkill if you only ever plan to use the Voice Bonnet mic. Best for: Makers who want a reliable reference device for debugging their voice pipeline before tuning the Voice Bonnet.
Check price on Amazon | Amazon.ca
4. Adafruit Mono 2.5W Class D Audio Amplifier (PAM8302) — Best Speaker Amp Upgrade
The AIY Voice Bonnet’s built-in speaker driver is functional but modest — it pushes around 1.2W into an 8-ohm load, which is fine for a desk but underwhelming in a larger room or inside a custom enclosure with any acoustic depth. The Adafruit PAM8302 mono 2.5W Class D amplifier board is the cleanest upgrade path. It takes a line-level audio input from the Voice Bonnet’s 3.5mm output or directly from the Pi’s PWM audio pins, and drives a speaker up to 2.5W into 4 ohms or 1.4W into 8 ohms with a measured THD of under 0.1% at 1W output. That’s a meaningful step up in clarity and volume.
The PAM8302 board is tiny — 20mm x 20mm — and runs from 2.5V to 5.5V, so it powers directly from the Pi’s 5V GPIO rail. Quiescent current draw is just 6mA, so it adds negligible load to your power budget. In a real home lab setup, I’ve paired this with a 3W 4-ohm full-range driver in a 3D-printed enclosure to get a genuinely room-filling voice assistant speaker. The combination of the revived Voice Bonnet handling microphone capture and I2C GPIO, with the PAM8302 handling speaker amplification, gives you a clean separation of concerns in your audio chain. If you’re building a smart home intercom, check out our roundup of the best intercom systems for smart homes in 2026 for inspiration on how to extend this kind of build.
Specs: PAM8302A Class D amp, 2.5W into 4 ohms, 1.4W into 8 ohms, 2.5–5.5V supply, THD <0.1% at 1W, 20x20mm board. Pros: Tiny footprint fits any enclosure; <0.1% THD for clean voice reproduction; 5V GPIO rail powered. Cons: Mono only — not suitable for stereo builds. Best for: Makers who want noticeably louder, cleaner speaker output from their Voice Bonnet build without adding bulk.
Check price on Amazon | Amazon.ca
5. SanDisk Extreme 64GB A2 microSD Card — Best Storage for Trixie Builds
This might seem like a mundane pick, but storage quality makes a dramatic difference in Raspberry Pi OS Trixie builds — especially when you’re compiling out-of-tree kernel modules like the Voice Bonnet drivers. The SanDisk Extreme 64GB A2-rated microSD card delivers sequential read speeds up to 190MB/s and sequential write speeds up to 130MB/s, with random read IOPS of around 4,000 and random write IOPS of 2,000. That A2 rating is the key spec: it means the card is optimized for random I/O, which is what matters when the OS is doing lots of small file reads during module loading, systemd service startup, and ALSA card initialization.
In practical terms, the difference between an A1 and A2 card on a Pi 4 running Trixie is about 40% faster boot time and noticeably snappier module loading — the Voice Bonnet drivers load in under 800ms on an A2 card versus over 2 seconds on a generic A1 card in my testing. The 64GB capacity gives you plenty of room for the full Raspberry Pi OS Trixie desktop image, the compiled Voice Bonnet modules, Whisper model files (the tiny model is 75MB, the base model is 142MB), and a healthy amount of audio recording buffer space. For a deeper look at how storage choices affect home lab builds broadly, our guide on essential home lab upgrades covers this in more detail.
Specs: 64GB capacity, UHS-I U3 V30 A2, 190MB/s read, 130MB/s write, 4,000 random read IOPS, 2,000 random write IOPS. Pros: A2 random IOPS dramatically improve module load times; 64GB fits full OS plus Whisper models; widely available and competitively priced. Cons: Not a substitute for NVMe SSD in high-write workloads. Best for: Any Trixie-based Pi build where fast module loading and reliable random I/O matter.
Check price on Amazon | Amazon.ca
Full Comparison Table
| Product | Est. Price | Performance | Power Draw | Ease of Setup |
|---|---|---|---|---|
| Raspberry Pi 4 Model B 4GB | ~$55 | Excellent — Whisper tiny in 1.8s | 3.4W idle / 7.6W load | ★★★★☆ |
| Raspberry Pi Zero 2 W | ~$15 | Good — best as satellite node | 0.4W idle / 1.3W load | ★★★★☆ |
| Anker PowerConf S3 | ~$80 | Excellent — 65dB SNR, 6-mic array | ~2.5W USB bus powered | ★★★★★ |
| Adafruit PAM8302 Amp | ~$5 | Good — 2.5W, THD <0.1% | 6mA quiescent | ★★★★☆ |
| SanDisk Extreme 64GB A2 | ~$12 | Excellent — 190MB/s read, 4K IOPS | Negligible | ★★★★★ |
Budget vs Premium Pick
Budget Pick: Raspberry Pi Zero 2 W + SanDisk Extreme 64GB A2
If you already have the AIY Voice Bonnet sitting in a drawer and want to get it working for the absolute minimum outlay, the Pi Zero 2 W paired with a SanDisk Extreme A2 microSD is your entry point. Together they’ll cost you around $27, and the Zero 2 W’s BCM2837 SoC means the Trixie driver fork applies directly with no device tree gymnastics. You won’t run local inference, but as a wake-word-detecting satellite node feeding audio to a more powerful server, this combination is genuinely excellent. Boot time on the A2 card is around 18 seconds to a fully initialized ALSA stack, which is fast enough for a production satellite node.
Premium Pick: Raspberry Pi 4 Model B 4GB + Anker PowerConf S3
For makers who want a complete, standalone voice assistant that runs everything locally — wake word detection, speech-to-text, intent parsing, and text-to-speech — the Pi 4 4GB paired with the Anker PowerConf S3 as a reference-grade microphone is the premium combination. The Pi 4 handles Whisper base model inference in approximately 3.2 seconds, which is fast enough for a natural conversation cadence. The PowerConf S3’s 6-mic beamforming array eliminates the acoustic challenges of MEMS microphone placement entirely. Budget around $135 for this combination, and you’ll have a voice assistant build that genuinely rivals commercial smart speakers in responsiveness — while keeping every byte of your voice data on your own hardware.
Best Overall Pick
The Raspberry Pi 4 Model B 4GB is the best overall pick for building around the revived AIY Voice Bonnet on Trixie. It’s the only board in this list that can run the full voice pipeline locally — from wake word detection through Whisper inference to Piper TTS playback — without offloading to another server. It’s compatible with the Trixie driver fork, it has the I/O headroom to add the PAM8302 amplifier and an external speaker without power budget concerns, and it gives you a clear upgrade path to more capable local models as they continue to shrink. If you’re serious about building a private, cloud-free voice assistant in 2026, this is where you start. You might also find our guide on DIY home calendar systems on Pi 3 useful for ideas on extending your Pi-based smart home display and announcement setup alongside your voice assistant.
Conclusion
The revival of the Google AIY Voice Bonnet for Raspberry Pi OS Trixie is one of those community wins that reminds you why open-source hardware and software matter. Eight targeted kernel fixes — covering API renames, probe signature corrections, return type fixes, a full PWM chip API rewrite for Linux 6.12, a device tree compatible string update, and proper out-of-tree Makefile structure — transformed a drawer full of expensive paperweights into a fully functional voice capture and playback platform. Whether you pair it with a Pi 4 for a standalone local assistant, a Pi Zero 2 W for a compact satellite node, or build it into something as ambitious as a Groucho Marx talking robot, the hardware is finally ready to cooperate with the modern OS stack.
The five hardware picks in this guide — the Pi 4 4GB, Pi Zero 2 W, Anker PowerConf S3, Adafruit PAM8302, and SanDisk Extreme A2 — cover every layer of a serious Voice Bonnet build, from host compute to audio amplification to storage performance. Hit the Amazon links below to check current pricing, and then come back and tell us in the comments: what are you planning to build with your resurrected Voice Bonnet? Drop your home lab setup details below — we’d love to feature the best builds in a follow-up roundup.
Ready to build? Check current prices on Amazon and grab what you need to get your Voice Bonnet running on Trixie today.
As an Amazon Associate, HomeNode earns from qualifying purchases.