TTS Providers | Home Assistant | Page 1

dreamy turret Mar 2, 2026, 9:55 AM

#

Are TTS Providers being deprecated or should they be kept?

#

Looking at this PR https://github.com/home-assistant/core/pull/163114

#

And I didn't quite know how to handle the old TTS Provider. Looked around and found this PR by @tribal pewter https://github.com/home-assistant/core/pull/108293

He writes: "For now, we'll keep the legacy cloud tts provider and set it up to allow users that use the corresponding service to still use that. We haven't decided if and when we want to deprecate that."

Was wondering if that still is the case?

surreal willow Mar 2, 2026, 10:27 AM

#

The legacy tts actions are being deprecated in favor of the TTS entities. But that is currently happening on a per integration level. New integrations should only implement TTS entities.

dreamy turret Mar 2, 2026, 10:29 AM

#

Makes sense. This is not a new integration though and still has a legacy TTS provider class. Should we issue a repair warning - nudging the user to use the TTS entity instead, or should we just support both - as is the case for the cloud integration?

surreal willow Mar 2, 2026, 10:35 AM

#

which integration?

dreamy turret Mar 2, 2026, 10:37 AM

#

The PR I'm reviewing adds a config flow to the "Pico TTS" integration. The other integration I was mentioning is "Home Assistant Cloud".

surreal willow Mar 2, 2026, 11:03 AM

#

ah, ok, I also reviewed that PR

#

don't put too much effort in the tests, there is a second PR that will replace the PicoTTS executable with a python library

tribal pewter Mar 2, 2026, 12:41 PM

#

At the time we decided to keep the Cloud TTS provider to avoid a breaking change in automations.

#

I'd say that most integrations can deprecate the old provider with a repair issue.

dreamy turret Mar 2, 2026, 1:05 PM

#

I see, so raising a repair issue in async_get_engine is fine?

#TTS Providers