Hello everyone,
Iโm having issues getting the wake word detection working on a fresh Home Assistant OS installation on a Raspberry Pi 4 (4GB).
Important: I do not want to use Nabu Casa / Home Assistant Cloud. I want a fully local setup.
Setup:
Hardware: Raspberry Pi 4 4GB
Microphone: Razer Seiren V3 Mini (USB) โ correctly detected in assist_microphone config
Speaker: Built-in Audio Stereo
Add-ons: assist_microphone, OpenWakeWord, Whisper (faster-whisper), Piper
Pipeline: Nestor โ STT: faster-whisper (fr), TTS: piper/gilles, Wake word: OpenWakeWord + Okay Nabu
Problem: assist_microphone connects to the server, sends run-pipeline, then gets a ConnectionResetError: [Errno 104] Connection reset by peer repeatedly. The add-on restarts every ~8-16 minutes (signal 15, clean exit). OpenWakeWord loads okay_nabumodel correctly but stops receiving audio after a while.
assist_microphone log pattern:
INFO:root:Connected to server
INFO:root:Streaming audio
DEBUG:root:Event(type='run-pipeline', data={'start_stage': 'wake', ...})
DEBUG:root:Ping enabled
WARNING:root:Did not receive ping response within timeout
DEBUG:root:Server disconnected
ConnectionResetError: [Errno 104] Connection reset by peer
OpenWakeWord log pattern:
Client connected: XXXX
Loaded models: ['okay_nabu']
Receiving audio from client: XXXX
[... then after a few minutes ...]
Client disconnected: XXXX
[no new audio client connects]
What works:
Whisper starts correctly
Piper TTS works
Pipeline works via Assist web interface (text mode)
assist_satellite.announceaction plays audio correctly
CPU usage ~23%, no resource issues
What doesnโt work:
Wake word โOkay Nabuโ never detected
OpenWakeWord stops receiving audio after reconnection cycles
Did not receive ping response within timeoutappears regularly
Has anyone experienced this on a recent HAOS version? Any fix or workaround appreciated ![]()