There are many many combinations of hardware and software which can do the same job.

I do however also want to pass on enough understanding of how the pieces fit together and the issues involved. This document tries to fast-track you to a working, extensible Home Assistant voice assistant without all the experimenting, dead ends and a learning curves I went through. That is a lot for a new user to get their head around, even someone with 30 years programming experience ! There were learning curves for Home Assistant, Rhasspy stand-alone, Rhasspy Base/satellite, External MQTT, HermesLEDcontrol, and Home Assistant Intents. Over the past year I have gone from a Home Assistant newbie - to a working Home Assistant with Rhasspy and 3 Satellites configuration. It seems obvious to me now that using a voice assistant means multiple microphone units distributed around the house (why have only one place where commands can be given?) and logically these satellites should be relatively cheap, with the bulk of the cpu-intensive work done on one shared base station. Using a Raspberry Pi Zero with reSpeaker 2-mic HAT Introduction So saying, lets get started with the preamble… Add Rhasspy local voice control to Home Assistant Sorry about the formatting - particularly headings and indentation … didn’t translate so well into forum posts Part 3 - Setup Rhasspy as Voice Asssistant.I have decided that it makes sense to split the 37 A4 page document into 5 parts: I got bogged down trying to write troubleshooting hints for anticipated problems that new users might encounter.Review and recommend improvements, particularly to the introductory overview (Part 0).Having reviewed the tutorial I wrote, there are a couple of areas I request your help:

Google home raspberry pi zero