sharp zealot
I use Ollama with preferring local .
When i say "set timer for 2 minutes (or 30 seconds, or even 60 seconds), it works well. However, when i say "set (or start) timer for one minute" - it goes to the LLM.
In Dev tools sentence parser works good for everything.
Latest HA, tried on ESPHome satellite and on Wyoming.
Any clues?
upper pawn
did not expect you to ask questions 😉
will test this in a minute, or 60 seconds
both 60 seconds and 1 minute timer works at my side, running nabu casa/goole ai, processed locally
tested on voicePE and respeakerlite running your software..
sharp zealot
Hmmmm wonder what the hell.
Hassil intents aren't super complicated. Must be something with pipeline or STT...
sharp zealot
did not expect you to ask questions 😉
Well, everyone has their own troubles
upper pawn
yup
must be dns lol
no sentence trigger configured that is overriding your command?
sharp zealot
no sentence trigger configured that is overriding your command?
Nah, I am pretty ok with default timers. 😉
In case of custom intent it would go to local scripts I guess... But it just doesn't recognize built-in intent.
Very curious
sharp zealot
both 60 seconds and 1 minute timer works at my side, running nabu casa/goole ai,...
Are you on HA 2025.8.3?
sharp zealot
Hmm, I just tried pipeline with direct Assist - and it works with 1 min timer as it should. But not on Ollama+Hassil
Will try different model
Huh, with Gemini and GPT4o it still doesn't want to set timer for 1 min
sharp zealot
yes, fully updated system
Is your conversation agent LLM with prefer local?
sharp zealot
what if you specify 60 seconds = 1 minute in your assist's model settings?
Model shouldn't be involved at all.
I think that our discrepancy can be hidden in language. I'm on English.
upper pawn
that's right, i will set it to EN after getting a cup of coffee and a big smoke, and test.
sharp zealot
Prolly En Hassil intents got crooked somehow... It's more extensive comparing other languages. At least that's the last idea on what's going on.
upper pawn
yeah, i guess that seconds is fully implemented as input to HA and will be directly processed, minutes is more natural language and triggers llama etc to act.
i tested EN, but results are the same, both seconds and minute work and handled locally
upper pawn
found this on my friend (or not sometimes) google ai..maybe true maybe not though 😉 :
In your Home Assistant YAML configuration, you can add this as a variation to the HassStartTimer intent. This is the best approach for a consistent, local experience. You'll need to find the sentences.yaml file for your voice pipeline and add the variation.
The most direct solution is to explicitly train your local voice assistant pipeline to recognize the phrase "set timer for 1 minute."
?
sharp zealot
Yeah if it gets super annoying I will just create alias. 🙂
Thank you for verifying!
