Actually… Just tried it. I am on 2025.10, so newer than what was mentioned there. It still does not understand any better than from what I remember. Bummer.

But hey, at least the acknowledge that there’s the need for something between dumb pattern matching and an LLM.

Holy shit YES!

That article is from yesterday, and the relevant section is: https://www.home-assistant.io/blog/2025/10/22/voice-chapter-11/#improved-sentence-matching

Awesome to see improvements there. Thanks a lot for linking!

Oh wow, awesome!

Thank you for your sacrifice :D

While I don’t like it, it’s not hidden either:

https://bentopdf.com/privacy.html

There should definitely be an option to disable this for self-hosting, but if it’s just a counter for how often each tool is used by all users combined… Eh…

(Stirling also has something similar)

Prisoner Of War:

Why not open a PR to make it configurable? The maintainer is super active and friendly.

Thanks for the recommendation! That looks interesting indeed.

This entire topic is probably a sinkhole of complexity. It’s great to have somewhere to look for inspiration!

Yeah those are good points. Also noticed the CDN thing, it’s a bit annoying for a privacy-first project… But should be an easy fix 😄

Stirling’s backend is Java. So, yeah, heavy and slow sounds about right.

Ah, thanks for mentioning. Yep, they have a docker image; as mentioned, a nixpkg will be available soonTM; and frankly, you can just build / download the release artifacts and put them on any static host.

Please read the title of the post again. I do not want to use an LLM. Selfhosted is bad enough, but feeding my data to OpenAI is worse.

Yep, that’s the idea! This post basically boils down to “does this exist for HASS already, or do I need to implement it?” and the answer, unfortunately, seems to be the latter.

Thanks, had not heard of this before! From skimming the link, it seems that the integration with HASS mostly focuses on providing wyoming endpoints (STT, TTS, wakeword), right? (Un)fortunately, that’s the part that’s already working really well 😄

However, the idea of just writing a stand-alone application with Ollama-compatible endpoints, but not actually putting an LLM behind it is genius, I had not thought about that. That could really simplify stuff if I decide to write a custom intent handler. So, yeah, thanks for the link!!

Thanks for your input! The problem with the LLM approach for me is mostly that I have so many entities, HASS exposing them all (or even the subset of those I really, really want) is already big enough to slow everything to a crawl, and to get bad results from all models I’ve tried. I’ll give the model you mentioned another shot though.

However, I really don’t want to use an LLM for this. It seems brittle and like overkill at the same time. As you said, intent classification is a wee bit older than LLMs.

Unfortunately, the sentence template matching approach alone isn’t sufficient, because quite frequently, the STT is imperfect. With HomeAssistant, currently the intent “turn off all lights” is, for example, not understood if STT produces “turn off all light”. And sure, you can extend the template for that. But what about

• turn of all lights
• turn off wall lights
• turnip off all lights
• off all lights
• off all fights
• …

A human would go “huh? oh, sure, I’ll turn off all lights”. An LLM might as well. But a fuzzy matching / closest Levensthein distance approach should be more than sufficient for this, too.

Basically, I generally like the sentence template approach used by HASS, but it just needs that little bit of additional robustness against imperfections.

Thanks for sharing your experience! I have actually mostly been testing with a good desk mic, and expect recognition to get worse with room mics… The hardware I bought are seeed ReSpeaker mic arrays, I am somewhat hopeful about them.

Adding a lot of alternative sentences does indeed help, at least to a certain degree. However, my issue is less with “it should recognize various different commands for the same action”, and more “if I mumble, misspeak, or add a swear word on my third attempt, it should still just pick the most likely intent”, and that’s what’s currently missing from the ecosystem, as far as I can tell.

Though I must conceit, copying your strategy might be a viable stop-gap solution to get rid of Alexa. I’ll have to pay around with it a bit more.

That all said, if you find a better intent matcher or another solution, please do report back as I am very interested in an easier solution that does not require me to think of all possible sentence ahead of time.

Roger.

Never heard about willow before - is it this one? Seems there is still recent activity in the repo - did the creator only recently pass away? Or did someone continue the project?

How’s your experience been with it?

And sure, will do!

That is actually a really interesting approach to moderation, huh.

Yeah but why would I make myself dependent on Cloudflare.

To be fair, you can simply selfhost MinIO.

Lol, exact same situation here.

Quick question, did the migration to continuwuity break calls for you as well?