Live data from Hacker News

The era of open voice assistants

home-assistant.io

111–120 of 290 posts

Re: The era of open voice assistants

#111
post #98
post #78

Earlier quoted context omitted.

It is, I think, a common feeling among Echo/Alexa users. Now that people are getting used to the amazing understanding capabilities of ChatGPT and the likes, it probably increases the frustration level because you get a hint of how good it could be. I believe it boils down to two main issues: - The narrow AI systems used for intent inference have not scaled with the product features. - Amazon is stuck and can't signi…

I think the economics here are wrong by orders of magnitude. It doesn't make sense to deploy to the home an expensive GPU that will sit idle 99% of the time, unless running an LLM gets much cheaper, computationally. It's much cheaper to run it on-premise and charge a subscription, otherwise nobody would pay for ChatGPT and would have an LLM rig at home instead.

You are right, but that's not my point. The point is that it's difficult to scale in the cloud products that requires lots of AI workloads.

Here, home assistant is telling you: you can use your own infra (most people won't) or you can use our cloud.

It works because most likely the user base will be rather small and home assistant can get cloud resources as if it was infinite on that scale.

If their product was amazing, and suddenly millions of people wanted to buy the cloud version, they would have a big problem: cloud infrastructure is never infinite at scale. They would be limited by how much compute their cloud provider is able/willing to sell them, rather than how much of that small boxes they could sell, possibly loosing the opportunity to corner the market with a great product.

If you package everything, you don't have that problem (you only have the one to be able to make the product, which I agree is also not small). But in term of energy efficiency, it also does not have to be that bad: the apple silicon line has shown that you can have very efficient hardware with significant AI capabilities, if you design a SOC for that purpose, it can be energy efficient.

Maybe I'm wrong that the approach will get common, but the fact that scaling AI services to millions of users is hard stand.

Re: The era of open voice assistants

#112

Earlier quoted context omitted.

> We need more projects like home assistant Isn't openHAB an existing popular alternative? https://www.openhab.org/

HA long ago blew past OpenHAB in functionality and community. Unless you have a hard-on for JVM services, HA is the better XP these days.

> HA long ago blew past OpenHAB in [...] community.

Home Assistant seems insurmountable to beat at that specific metric, seems to be the single biggest project in terms of contributions from a wide community. Makes sense, Home Assistant tries to do a lot of things, and succeeds at many of them.

Re: The era of open voice assistants

#115
post #83

Earlier quoted context omitted.

But like, isn't YAML still available for configuring things? Have they gotten rid of any YAML configs, with things that are now UI only? My understanding was that they've just been building more UI for configuring things and so now default recommend people away from YAML (which seems like the right choice to me).

> But like, isn't YAML still available for configuring things? For most, yes. But for some included integrations it's UI-only (all of those I've had to migrate, it's been a single click + comment out lines, and the config has been a breeze (stuff like just an api key/IP address + 1-2 optional params).

Where and how are those configs stored? There has to be a backing representation somewhere, right?

Re: The era of open voice assistants

#116
post #7

I'm actually really excited for this! I noticed recently there weren't any good open source hardware projects for voice assistants with a focus on privacy. There's another project I've been thinking about where I think the privacy aspect is Important, and figuring out a good hardware stack has been a Process. The project I want to work on isn't exactly a voice assistant, but same ultimate hardware requirements Someth…

I invested in Mycroft and it flopped. Here’s hoping some others can go where they couldn’t.

IIRC one of the main devs behind this device came from Mycroft.

Re: The era of open voice assistants

#117
post #84
post #81

Had to laugh a bit at the caveat about powerful hardware. Was bracing myself for GPU and then it says N100 lol

I mean, comparatively many people are hosting their home Assistant on an raspberry Pi so it is relatively powerful :D

And the CM5 is nearly equivalent in terms of the small models you run. Latency is nearly the same, though you can get a little more fancy if you have an N100 system with more RAM, and "unlocked" thermals (many N100 systems cap the power draw because they don't have the thermal capacity to run the chip at max turbo).

Re: The era of open voice assistants

#118
post #3

That's a pretty timely release considering Alexa and the Google assistant devices seem to have plateaued or are on the decline.

Curious what you mean by that.

On the Google side it's become basically useless for anything beyond interacting with local devices and setting timers and reminders (in other words, the things that FOSS should be able to do very easily). Its only edge over other options used to be answering questions quickly without having to pull out a screen, but now it refuses to answer anything (likely because Google Search has removed their old quick answers in favor of Gemini answers).

Re: The era of open voice assistants

#119
post #111
post #98

Earlier quoted context omitted.

I think the economics here are wrong by orders of magnitude. It doesn't make sense to deploy to the home an expensive GPU that will sit idle 99% of the time, unless running an LLM gets much cheaper, computationally. It's much cheaper to run it on-premise and charge a subscription, otherwise nobody would pay for ChatGPT and would have an LLM rig at home instead.

You are right, but that's not my point. The point is that it's difficult to scale in the cloud products that requires lots of AI workloads. Here, home assistant is telling you: you can use your own infra (most people won't) or you can use our cloud. It works because most likely the user base will be rather small and home assistant can get cloud resources as if it was infinite on that scale. If their product was amazi…

But here you're assuming that your datacenter can't provide you with X GPUs, but you can manufacture 100X, which is dictated by 1% utilization.

Re: The era of open voice assistants

#120
post #34

Earlier quoted context omitted.

> No wake words: it should listen to everything, process it, and understand when it's being addressed Even humans struggle with this one - that's what names are for!

Yeah, I’m having a hard time imagining how no-wake-word could work in practice.

Like that really annoying friend who jumps in every other sentence with "Well actually..."
Post reply on HN