#Trying to set up a custom wake word. Day 11, Captain's log.

1 messages · Page 1 of 1 (latest)

trim ocean
#

Hey there! A pleasure to be here. Trying to set up a custom wake word. Day 11 🤣 I'll get there! Wakeword, whisper and piper are added. Running a pc-satellite successfully. Whisper doesn't register anything though 🤔

For one, GPT is adamant there's a "Pipelines" tab under "Voice assistants" and just doesn't believe when I confirm there's none 😃

Technical writeup of the issue:
• Home-Assistant Core (latest) on Yellow.
• Added local add-ons: openWakeWord (10400), Whisper, Piper – all show up under “Wyoming Protocol”.
• Windows-PC running wyoming-satellite + FFmpeg; Assist sees it as “Windows-PC-Satellite” and status toggles Idle ↔ Listening.
• Satellite console streams OK but spams “real-time buffer […] too full, frame dropped” (FFmpeg dshow). :contentReference[oaicite:0]{index=0}
• Wake-word fires (state sensor flips), yet Whisper never receives audio → no STT, Assist stays silent.
• Under Settings → Voice assistants I only have Assistants | Expose (pipeline tab missing) so I can’t build a local pipeline that links wake-word → Whisper → Piper. :contentReference[oaicite:1]{index=1}
• Confirmed PC ↔ HA TCP 10700 reachable; 10400 still LAN-closed unless I expose it. :contentReference[oaicite:2]{index=2}

Super grateful for any help!

NB! Do i understand correctly that my service discovery is stuck on starting?

molten scroll