Speech-To-Phrase
A fast and local speech-to-text system that is personalized with your Home Assistant device and area names.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
56/100 Fair
- Maintained
- 70last commit 52 days ago
- Popular
- 51349 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 53 days ago
- GitHub stars
- 349
- Open issues
- 90
- Last commit
- 2026-09-30
- Latest release
- v1.4.3
- License
- Apache-2.0
- Activity
- stale
Checked 20 days ago - source: GitHub (OHF-voice/speech-to-phrase)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Download and keep the Whisper model file Before starting the STT CLI or daemon, download a Whisper model, such as medium for the CLI or large-v3 for the server, and keep it in the path the commands point to, like thirdparty/whisper.cpp/models. Without that model file, speech-to-text will not work or the daemon may fail to start. source
- Port 1234 is used by the STT server If you run sttd, it listens on 0.0.0.0:1234 by default, which means any device can try to reach that port. Open port 1234 only where you trust it and remember it is for sending audio to the speech-to-text server. source
- Use GPU settings only if CUDA is ready If you enable GPU acceleration, install the CUDA toolkit first and then use settings like --use-gpu=true and --gpu=0. This can speed up transcription, but if CUDA is missing or the GPU ID is wrong, the server may fail or run unexpectedly slow. source
Fetched 37 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which repository has the newer rewrite of Speech-to-Phrase?
Development has moved to OHF-Voice/apps, while this repository holds the older Kaldi-based version up to v1.4.3. The rewrite uses a constrained CTC decoder, home-assistant-intents sentences, and a web UI for choosing commands.
How can you add your own sentence values?
Use --custom-sentences-dir to point at directories of YAML files per language. For an English model, the example file is /path/to/custom_sentences/en/sentences.yaml, and list values should be quoted.
Which Home Assistant names does Speech-to-Phrase use?
It combines predefined sentence templates with the names of Home Assistant entities, areas, and floors that are exposed to Assist. It only matches known phrases rather than acting as general-purpose speech recognition.
What language support does the rewrite currently have?
The rewrite currently serves ca, cs, de, en, es, fr, it, and nl. It notes that ru, hi, and sl still need sentences, while the rest need both sentences and an acoustic model.
Answers sourced from github.com
Community
- Speech to text engine - Speech-to-phrase not working (other)
- Speech-to-phrase fallback to faster-whisper (no cloud) (other)
- [Full Release] Speech-to-Text API - Announcements - Developer Forum ... (forum)
- General Discussion - SpeechChat Forums (forum)
- Self hosted Text to speech : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads