I actually have things like “play x by y” functioning really well without a LLM.
Have a custom service that exports all song/album/artist names from MusicAssistant, does some simple cleanup, and places the list where HomeAssistant expects it for custom voice intents. Then this: https://github.com/charludo/hass-closest-intent is enough that imperfect STT can still easily be matched to those song/artist/… names.
But… That would force them to provide a great user experience in order to retain users!! That’s an unacceptable burden on the largest companies in the world!!
It’s just a helper. It’s a way for your calendar to ask “uhhh… Should I already know of any calendars…?” and the service going “oh actually yeah, the user configured their email account, hold on, here’s the corresponding calendar”.
That’s just basic functionality. Maybe what’s tripping you up is that it’s a separate service? Because I assume you have nothing against inputting your email into a mail client and a calendar separately.
If so, then for one, it’s not really a difference if the mail app stores this into or the service does; and second, it’s a good thing to have this standardized into a single purpose built service, rather than having each app reimplement this stuff.
CPU and RAM usage is so negligible it’s laughable.
IDK.
It seems like you read something about personal data in the service description and just jumped to the conclusion that this is something nefarious.
How exactly is it bloatware though? Not a KDE user myself, just had a look at the wiki. Seems it’s just a convenience utility to allow you to not have to enter the same things into multiple applications?
This is VERY different from pre-installed apps in your start menu that collect and sell info about you…
Yeah, thinking more about it, I don’t think the term “bloatware” (as it is commonly used) applies here at all.
How do I completely disable it forever?
To answer your question: sudo systemctl mask <servicename>.service
The much more common disable just disables autostart; masking will point the service file at /dev/null, which makes it impossible to load or start the service, even when other services or apps (like the clock widget someone mentioned in the comments) request it.
Yes, you can! See the “threshold” value/slider. It’s at 0.7 by default, which seems to be a good tradeoff. 1 means exact match or failure, 0 will afaik match anything to everything.
Ah, I didn’t see the Edit, so we’re both in the same boat 😂
Finally got this through another comment below. No, this should not be able to happen, unless you yourself have created a custom intent + shell script action in home assistant that runs this. The integration itself does not execute actions/scripts or the like, it just finds the closest string in a list of strings, and then hands that to the official conversation agent/Hassil.
Yes, should be completely language agnostic. I’m not a linguist though, so take with a grain of salt 😅
There’s nothing language specific going on though, apart from a slight preference to split slots on word boundaries determined by spaces. So, might work a bit worse in e.g. Japanese.
Burden of proof is on Astrology claiming to be real.