CF image for Google Home Mini running Linnet + Home Assistant (local, no Google cloud) #11
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Concept
Build a CF-flavored firmware image for the Google Home Mini (Gen 1/2) that replaces Google Assistant with a fully local stack: Whisper STT, Piper TTS, Home Assistant, and Linnet for real-time tone annotation. Turns a cheap/salvageable smart speaker into a privacy-first home node with no cloud dependency.
Reference
Technical approach documented at: https://courk.cc/running-custom-code-google-home-mini-part1
The approach uses a NAND flash interposer system ("NandBug") built around an ICE40HX1K FPGA + FT2232H USB interface. The original NAND is desoldered and hosted on a daughterboard; the FPGA arbitrates between the Google Home PCB and the programmer. Key challenge: rootfs is protected by dm-verity (see Part 2+ for exploit path).
Hardware: Marvell ARMADA 1500 Mini Plus SoC + 256MB TC58NVG1S3HBAI6 NAND flash. Most components are BGA; CPU is largely undocumented.
CF software stack on device
Why this matters for CF
Google Home Minis are cheap, widely available, and have decent mic arrays and speakers. Jailbroken and reflashed, they become a privacy-first home node that integrates with the FOSS/OSH home assistant robot concept (roadmap#43). Linnet integration adds the tone annotation layer that benefits ND users who want context surfaced from household voice interactions.
Hardware effort required
This is a medium-difficulty hardware hack. Could become a CF hardware kit (PCB design + flashing tool).
Next steps