Just a few days after Google released a software development kit for Google Assistant, allowing developers to bring Google’s voice assistant service to third-party hardware, there’s a new hardware kit that lets you turn a Raspberry Pi into an Assistant-enabled device.

The AIY Projects voice kit includes a speaker, microphone, cables, arcade-style button, and a cardboard case that you can fold to put everything together in a small box. When it’s done you can trigger Google Assistant by pressing the button, clapping your hands, or using a different trigger.

One of the coolest things about the hardware kit? You can get it for free… when you buy issue 57 of MagPi, a magazine about the Raspberry Pi.

You can actually download a PDF of the magazine for free, but clearly the digital edition doesn’t come with the hardware needed to bring Google Assistant-compatible hardware to a Raspberry Pi 3.

That said, you don’t need this specific kit to do that. Google specifically called out the Raspberry Pi 3 as one of the devices compatible with the new Google Assistant SDK, which means that you can connect just about any mic and speaker to start working with the software development kit.

via Raspberry Pi

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign


Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

Subscribe to Liliputing via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 9,547 other subscribers

4 replies on “Hardware kit turns Raspberry Pi into a DIY Google Home (kind of)”

    1. Well, this one has a physical button to trigger it, so it doesn’t seem to always be listening. Presumably you can modify the code yourself to limit what it calls to (and audit its traffic with Wireshark e.g.).

Comments are closed.