←back to thread

The era of open voice assistants

(www.home-assistant.io)
931 points _Microft | 1 comments | 20 Dec 24 00:29 UTC | HN request time: 0.214s | source
Show context
frognumber ◴[20 Dec 24 03:56 UTC] No.42468148[source]▶
I don't fully understand the cloud upsell. I have a beefy GPU. I would like to run the "more advanced" models locally.

By "I don't fully understand," I mean just that. There's a lot of marketing copy, but there's a lot I'd like to understand better before plopping down $$$ for a unit. The answers might be reasonable.

Ideally, I'd be able to experiment with a headset first, and if it works well, upgrade to the $59 unit.

I'd love to just have a README, with a getting started tutorial, play, and then upgrade if it does what I want.

Again: None of this is a complaint. I assume much of this is coming once we're past preview addition, or is perhaps there and my search skills are failing me.

replies(5): >>42468158 #>>42468230 #>>42468247 #>>42468341 #>>42469791 #
1. choffee ◴[20 Dec 24 10:21 UTC] No.42469791[source]▶
This device is just the mic/speaker/wakeword part. It connects to home-assistant to do the decoding and automation. You can test it right now by downloading home-assistant and running it on a pi or a VM. You can run all the voice assist stuff locally if you want. There are services for the voice to text, text to voice and what they call intents which are simple things like "turn off the lights in the office". The cloud offering from Nuba Casa, not only funds the development of Home Assistant but also give remote access if you want it. As part of that you can choses to offload some of the voice/text services to their cloud so that if you are just running it on a Pi it will still be fast.