Add important disclaimer about LLM model impact on performance
- Clarify that integration provides search, but LLM determines accuracy/speed - Recommend qwen3:4b as good starting point for local voice pipelines - Link to Performance section for optimization guidance
This commit is contained in:
1 parent
ec0bcd174d
commit
c1908a549f
1 file changed
+2
@@ -28,6 +28,8 @@ Before using this integration, you need:
|
|||||||
|
|
||||||
**Use both together:** Many users run Music Assistant for UI/management and this integration for voice control via custom conversation agents.
|
**Use both together:** Many users run Music Assistant for UI/management and this integration for voice control via custom conversation agents.
|
||||||
|
|
||||||
|
> **⚠️ Important:** This integration provides the search functionality - your conversation agent's LLM model and hardware determine the actual voice command accuracy and response time. For local voice pipelines, qwen3:4b is a pretty good starting point. See [Performance](#performance) for optimization guidance.
|
||||||
|
|
||||||
## The Problem
|
## The Problem
|
||||||
|
|
||||||
Want to control Spotify with your voice in Home Assistant? You'll quickly hit these issues:
|
Want to control Spotify with your voice in Home Assistant? You'll quickly hit these issues:
|
||||||
|
|||||||
Reference in new issue
Block a user