I keep having my home assistant freese when I try and activate HAV, been debugging it but didn't found anything yet to solve it.
Buttttt...
What I did find is an easter egg in the source code. It's "HA" in morse code. If you put that into the main button on the device it activates something :)
6 Comments
JelleWho@lemmy.world · 10 pts · 246d
For refference, the HAV unit didn't get a ping after nabu detection. The system froze with one cpu pinned to 100% usage. Screen and observer show that everything is fine. But the dashboard and such is unreachable.
I have now settup assistant completly again, and I think the only difference is "streaming wake word engine = enabled" and I manually force set the assistant in the (esphome) device to the assistant instead of "default". This seems to work again for now...
avidamoeba@lemmy.ca · 5 pts · 245d
All I can contribute is to say thay "it works on my machine." I run HA on a Yellow. Followed the default setup.
Recently connected it to a local LLM and it's much easier to use without having to remember the exact names of things.
JelleWho@lemmy.world · 3 pts · 245d
Did you try the .... ._ yet?
avidamoeba@lemmy.ca · 1 pts · 245d
Not yet. 😀
richie510@lemmy.world · 2 pts · 243d
I had this same issue with one of those little cube $10 voice hardware things. I was using the locally run wake word and it would crash HA every time I activated the wake word. I also have the Voice PE hardware and this never has caused the issue. I couldn’t find anything about it and didn’t really use the extra satellite much, so I just took it out of service for the last month.
ikidd@lemmy.world · 1 pts · 245d
brockhold@lemmy.world · 1 pts · 245d
I've had HA hang while running wyoming-openwakeword, but my setup is pretty different from yours -- I was trying to get wakeword detection off the audio track in an RTSP stream. I didn't solve it, and gave up.