tinyhumansai/openhuman · error
no voice provider with slug '{}' found in voice_providers
Error message
no voice provider with slug '{}' found in voice_providers What it means
create_stt_provider_by_slug looks up the requested slug in config.voice_providers; this fires when no entry has that slug — the provider was never configured or the slug is misspelled — before any capability check or client construction.
Source
Thrown at src/openhuman/voice/factory/helpers.rs:102
.to_string()
}
// ---------------------------------------------------------------------------
// Slug-keyed provider creation
// ---------------------------------------------------------------------------
/// Create an STT provider by looking up a slug in `config.voice_providers`.
pub(super) fn create_stt_provider_by_slug(
slug: &str,
model: &str,
config: &Config,
) -> anyhow::Result<Box<dyn SttProvider>> {
let entry = config
.voice_providers
.iter()
.find(|p| p.slug == slug)
.ok_or_else(|| {
anyhow::anyhow!(
"no voice provider with slug '{}' found in voice_providers",
slug
)
})?;
if !entry.capability.supports_stt() {
return Err(anyhow::anyhow!(
"voice provider '{}' does not support STT (capability: {})",
slug,
entry.capability.as_str()
));
}
let effective_model = if model.trim().is_empty() {
entry.default_stt_model.as_deref().unwrap_or("default")
} else {
model
};View on GitHub (pinned to 7491200858)
Solutions
- Add the provider under [[voice_providers]] in config.toml with that slug
- Check the slug spelling against the configured voice_providers entries
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/voice/factory/helpers.rs:102 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/21bc0277351c9e3e.
Report an issue: GitHub.