When including entity state or values in TTS announcements we are forced to switch from the Graphical Editor to YAML and use templating. If you want to use the CHIME TTS addon from HACS to add nice alert sounds to your message it creates a problem because all of the drop down menus that work in the Graphical Editor are lost when you are forced into YAML view and you cannot adjust any other parameters unless you first remove the templating so you can switch back out of YAML view.
Other platforms I use such as Homeseer allow device states and values to be substituted into TTS strings simply by using special characters next to the device reference to indicate a the state or value of the device should be inserted.
For example:
If the time is 11:00:00 AM
Then Speak The outside temperature is $$DVR:3825: degrees but it feels like $$DVR:3830 degrees. The humidity is $$DVR:3826: percent. The barometer is $$DSR:3834:.
When spoken this will substitute values for temperature, windchill, humidity, and pressure trend.
Because this is done within the Graphical Editor for this platform it works with all integrations and is very easy to edit and manage.
Templating is neither easy to edit nor does it work well with other Integrations such as Chimes TTS. It would be better if there was a way to utilize entity states and values in TTS that worked entirely within the Graphical Editor.