Hello, I am 100% new to HA. I have HAOS running in a Proxmox VM. I am trying to figure out how to get my assistant to respond to my voice.
#Home Assistant Wake Word issues
1 messages · Page 1 of 1 (latest)
if it helps, Ollama is running on another computer so I dont need to deal with GPU passthrough for Ollama
the other box is running ubuntu server 24.04LTS
thanks in advance to anyone who helps me
do you have openwakeword set up in your pipeline? I don't see it at the bottom of that page.
@proud hull there should be three dots at the top of the menu for the voice assistant that will give you the option to add the streaming wake word.
if it is not there, make sure that you have the wyoming protocol entity added under integrations
I see 2 services listed under your wyoming protocol but you should have 3, piper, whisper and openwakeword
this would be a place to start although the overflow menu does appear to be missing in your screenshot? what version of home assistant are you running? are you up to date?
I have now added OWW to Wyoming and clicked the 3 dots to add it
im gonna test it now
HAOS latest
not the docker versiojn
full on HAOS
I have a similar test setup let me try and play with ir. I haven't run the voice assist locally but instead been using it through esp device so id have to take a look at that personally.
@proud hull I suggest you try a different approach. instead of passing the audio devices to your haos vm and using assistant microphone which hasnt really been updated in a while. attach the audio devices to a separate vm and run THIS project instead.
its a newer (technically still "experimental") way of running voice on linux. and as its based on the esphome protocol its easier to update and keep feature parity with other voice satellites.
I believe it’s working but audio out seems to have something wrong with it so I’ll need to debug that
I see the wake word triggering then GPU useage spike as the LLM responds
audio isnt working tho
ima test with another device
im unable to get ANY audio to play outa the device, witch is odd, because ive had this exact USB to 3.1mm jack work perfectly in the past