Local LLM Ollama Voice not performing actions

Configuration Voice Assistant
1

Hi all,

I’ve been trying a lot of the suggestion on here and reddit and still running into an issues. I’ve got Ollama running a PC w/ 3080. Ive got HA running on a Pi as a docker, I’ve got Whisper and Piper running on my Unraid box. The plumbing for all the intergrations is working well. Ive got HA setup to use Ollama intergration. I’ve tried Minstral-nemo 12B, Ollama 3.2, gemma3:12B. They all seem to be “working”.

When I type to the HA text in the app or web, it is able to turn on and off the lights fine. But when I use voice both on the app or the HA Voice, it says is does it, but no action is taken. I can use my voice and ask what the status the lights are, on or off, but it can not take actions. These devices are exposed to voice assistant.

Going through the NetworkChuck video, Under, setting → Virtual Assistant → Home Assistant, Under the Conservation Agent He has a gear Icon beside the it where he can select “No contol” or “Assist”. I do not have that anywhere. It is a 4 month old video, so im not sure if that interface has changed.

The closest thing I see to this is the Config for OLLAMA itsself where I can modify the prompt, but I do not see the ability to turn on Assist.

Any help would be greatly appricated.

2

This setting is found in the conversation configuration. In your case, in the ollama integration.
Are you using the latest version of HA?

3

Thanks for the response. Yes this is a new deployment running the latest docker.

Under /config/integrations/integration/ollama the only thing I have is the prompt template. At the bottom only has history count. Is there a config statement I need to add to the Prompt template to enable action?

Beside the conversation agent I exspected to have the gear Icon.

image
image609×1190 51.8 KB

4

It looks like an outdated version of the integration is being used. The new controls came out in June. Also, your screenshot is missing the switch to prioritize local commands.
I am not familiar with installing HA in docker, but I think the problem is related to that.

5

Ugh, your right! CasaOS defaulted to a static build from 5-2024! I just spent all day yesterday reloading fresh from an older version to an old newer version then =/… Thanks. Not sure if how this is going to go. But at least I got somewhere to start.