#VPE no longer working

1 messages · Page 1 of 1 (latest)

charred hill
#

I got a Home Assistant Voice PE a few days ago and initial setup worked fine. I played around a bit with Ollama on a VM and setting up an assistant with that. In the Ollama process I had to remove all exposed entities for it to even return a response, but that took 30 seconds for a simple prompt, so ultimately that proved to be too slow on my NAS without a GPU.

Now I'm trying to put it back to use my default HA assistant with whisper STT / Piper TTS, but the VPE no longer does anything. It responds to the wake word (even when I change it), but then immediately goes idle again, looking at the ESPHome device logbook. After it does that, I have to say the wake word twice for it to play the wake sound, but then immediately goes idle again, so I can't give it any commands.

Any clue on what I could have done to break things? Thanks!

desert plinth
charred hill
#

thanks, deleting it from the ESPHome integration is enough?

desert plinth
#

disconnect vpe from power, delete vpe and reboot, then flash new

#

normally it will show as discovered afterwards and will create the pipelines etc.

#

Ollama is no go without gpu 😉 (unless you've got all the time in the world to wait for responses).

charred hill
#

yeah I found that out after spending a bunch of time getting it set up 😄

desert plinth
#

i am using nabu casa cloud, that does the trick for me.

#

faster, better voice and supporting HA

charred hill
#

yeah, I kind of want to avoid any cloud, but that's kinda hard to do nowadays I suppose

#

thank you! reflashing and readding it did the trick

desert plinth
#

nabu casa is home assistant, so everything is encrypted and will backup to nabu cloud also

charred hill
#

kind of curious how I broke it, but I guess it doesn't matter too much

charred hill
desert plinth
#

different pipelines i guess, always reboot everything to verify its not in the cache

#

So you're up&running?

charred hill
#

yeah I restarted the thing and HA multiple times while debugging the issue but somehow it was just not cooperating

#

it's working again now yup!