Anatomy of a voice assistant

I recently wrote a blog series on how OVOS/Neon works - which service handles what part of the assistant pipeline? How do they interact? What are some configurations you can use for different scenarios, including minimal development setups? The series is aimed at less technical users but can also be a good overview for developers trying to remember which code to edit for their use case.

Please share with anyone who may have interest and feel free to send feedback! I do update blog posts from time to time as corrections/new information becomes available. Enjoy!

3 Likes

You forgot to mention your Rust implementation of the message bus which I’m using everywhere. :innocent:

1 Like


Should I make it more prominent? I only mentioned it in passing

1 Like

I would not bother with C++ IMO, its buggy and not really maintained.

1 Like

it was a proof of concept, and now that we have the rust bus i agree!

2 Likes

Mike, good stuff. I looked at the first one, will try to peruse the others today. Just one piece of feedback: when you mention HiveMind, you assume the reader knows what it is. Maybe describe it and/or make it a hot link. -Mike Mac

Thanks Mike! The header is a link to the HiveMind documentation. Should I make the link more prominent?

D’oh - my bad. I went through the other blog entries - great stuff!

1 Like