Add TTS (text to speech) back to lovelace media player #11923
Replies: 10 comments 5 replies
-
I downgraded to 2022.2.9 where it is working |
Beta Was this translation helpful? Give feedback.
-
Please, I understand having it in the media part, but removing it makes it more clicks to achieve what we could do quickly before. |
Beta Was this translation helpful? Give feedback.
-
Agree, this is such useful function.. i dont even have media browser enabled |
Beta Was this translation helpful? Give feedback.
-
It also broke the TTS functionality for my google home speakers for some reason. |
Beta Was this translation helpful? Give feedback.
-
This could easily by done alternatively by using an input_text helper and passing it's contents via an automation/script to the call service. Then you can have an input in your lovelace to type the text in directly. If you have multiple speakers can even additionally add input_select to choose between all your speakers. |
Beta Was this translation helpful? Give feedback.
-
"could easily be done" - I'd love to see some people in the real-world working a real job. hahaha. Removing the TTS option from individual cards only to replace it with a message saying TTS isn't available there is counter-productive. If you're going to have that message you may as well have a link to the Media Browser. And if you go that far, you might as well go back to square one and put the original control back. Look, TTS is not a "Media Browsing" function at all. TTS doesn't belong in the Media Browser UI. Its implementation in that spot is awkward, non-intuitive and at the moment buggy that it's missing any number of player entities, leaving people without the ability to control many of their devices (see home-assistant/core#67518) . Compromise. Go all-in on the Media Browser, but leave the TTS control on individual cards for quick one-off access. Everyone knows that (once the bugs are fixed) automations of all sorts can be created to do so much more, but none of it is a replacement for quick-access built into the original entity card. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue. No chance to get TTS working on my players via the media section. This "update" is one of the worst "improvment" I've ever seen in home assistant. It's simply a very huge step back. Want not to be rude but this "improvment" is bullsh*#*! Please, bring back the functionality as before, thank you. |
Beta Was this translation helpful? Give feedback.
-
I faced the same problem today. However, I did find one: Alternatively, you could of course also build a media_card with a custom:button-card and then go into more detail regarding TTS in a "tap_action". |
Beta Was this translation helpful? Give feedback.
-
Why would this be removed!!! The new process is soooooo annoying! |
Beta Was this translation helpful? Give feedback.
-
I agree it's not easy, but this is a summary of what you would need to see a text input in the dashboard and have some speaker say it out loud when the text changes (when you press enter). I'm using home assistant 2023.6.0
This creates a new Entity with ID
Now, whenever you go to your dashboard and you update the text and press enter, you will hear it. |
Beta Was this translation helpful? Give feedback.
-
The latest update removed the ability to quickly enter text and broadcast to a speaker. We used this frequently to notify family members in the basement. Can we please bring back? There is no easy alternative. Need a quick solution from lovelace overview page.
Beta Was this translation helpful? Give feedback.
All reactions