[anubhavlal07]

Four plugin classes don't override the provider property, so they fall back to the base class's "unknown": NVIDIA STT and TTS, Uplift AI TTS, and xAI STT. NVIDIA STT doesn't override model either. These are the values that metrics, telemetry spans and the fallback adapters report (#6690), so usage from these plugins shows up with no provider. Every other STT and TTS plugin sets them.

Fix: add the properties, using the names these packages already use elsewhere:

• NVIDIA STT and TTS report "nvidia", as nvidia.realtime does. STT.model returns the configured Riva model.
• xAI STT reports "xAI", as xAI TTS does.
• Uplift AI TTS reports "UpliftAI".

I didn't add model where the plugin has no model setting to report: NVIDIA TTS selects voices by function_id, and Uplift AI and xAI STT have no model option.

Tests:

• test_reports_model_and_provider in tests/test_plugin_nvidia_stt.py;
• test_reports_provider in tests/test_plugin_xai_stt.py;
• test_reports_provider in a new tests/test_plugin_upliftai_tts.py (plugin("upliftai")).

All three fail on main and pass with the change (34 tests across the three files). ruff check and ruff format --check are clean.

This change was prepared with the help of an AI assistant (Claude), and I reviewed and tested it.

[CLAassistant]

All committers have signed the CLA.

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🟡 Plugin metadata overrides lack documentation

The new model and provider overrides have no docstrings, despite the requirement to document new methods. Their plugin-specific values remain undocumented on these properties.

Learn more

The repository requires documentation for every newly written method. All five new property overrides lack docstrings: NVIDIA STT's model and provider, NVIDIA TTS's provider, Uplift AI TTS's provider, and xAI STT's provider. The base properties describe the general interface, but not the plugin-specific values of these overrides.

Example: A reader inspecting NVIDIA STT's model property sees no method documentation explaining that its value is the configured Riva model.

Recommended fix: Add concise docstrings to all five overrides identifying the value each exposes; document NVIDIA STT's model as the configured Riva model.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[anubhavlal07]

These follow the existing overrides: 119 of the 123 provider overrides in livekit-plugins have no docstring, and the base STT.provider / TTS.provider docstrings already describe the property. Happy to add them if maintainers prefer.