Data_template error

Configuration
1

I have this automation:

- id: Buongiorno info HUB
  alias: Info
  initial_state: true
  trigger:
    - platform: time
      at: '13:45:00'
  condition:
    - condition: state
      entity_id: input_boolean.mauhome
      state: 'on'
  action:
    - service: tts.google_translate_say
      entity_id: media_player.studio, media_player.sonos_stereo
      data_template:
        message: >-
          Sono le {{states('sensor.time')}},
          ed è {{states('sensor.dark_sky_summary')}}. 
          La temperatura esterna è di {{states('sensor.temperature_158d0001b95f60')|int|string }} gradi,
          mentre la temperatura interna è di {{states('sensor.temperatura_media_casa') |int|string }} gradi. 
          *Previsioni.* {{ states.sensor.dark_sky_hourly_summary.state }}. 
          *Citazione. * {{state_attr('sensor.wikiquote', 'entries')[-1].summary|striptags}}.

It doesn’t work and if i try to trigger it from the services i get:

extra keys not allowed at @data [‘data_template’]

Where is the error in the data_template?

2

Move the line with entity_id below data_template.

  action:
    - service: tts.google_translate_say
      data_template:
        entity_id: media_player.studio, media_player.sonos_stereo
        message: >-
          Sono le {{states('sensor.time')}},
          ed è {{states('sensor.dark_sky_summary')}}. 
          La temperatura esterna è di {{states('sensor.temperature_158d0001b95f60')|int|string }} gradi,
          mentre la temperatura interna è di {{states('sensor.temperatura_media_casa') |int|string }} gradi. 
          *Previsioni.* {{ states.sensor.dark_sky_hourly_summary.state }}. 
          *Citazione. * {{state_attr('sensor.wikiquote', 'entries')[-1].summary|striptags}}.
3

No way… always the same error.

4

This isn’t what you’re asking, but you don’t need the time condition… unless there’s an eighth day I don’t know about :wink:

Also… perhaps it needs to be a single-line template? Even though you properly used > to denote a multi-line template.

5

Good answer… you’re right… but that is the minimal problem… :slight_smile:
I tried also a single line, but with no good result.

6

Does that template work in Developer Tools > Template?

7

Yes, it works fine there…

8

Try this:

  action:
    - service: tts.google_translate_say
      data:
        entity_id: media_player.studio, media_player.sonos_stereo
        message: "Hello world!"

If that produces an error, I have to admit whatever is causing it is non-obvious to me.

If it works, evolve it to this:

  action:
    - service: tts.google_translate_say
      data_template:
        entity_id: media_player.studio, media_player.sonos_stereo
        message: "{{ now().month }}"
9

If i do this inside the service UI i get the same error. with data and not data_template

10

Did you rename the TTS service in your config? It should print a “service not found” error if you use a non-existent service but who knows at this point. Post your TTS config if you’re not sure what I’m talking about.

11

Wow! It failed with that very basic example? Strange.

EDIT
I agree with Tediore that there may be something fundamentally wrong and the data_template error is misleading but the only way the service can express the underlying flaw.

12

That’s really strange as now i ran the automation again and all is working good… maybe some bug inside the service UI?
BTW Problem solved !

13

Based on the recent problems you’ve been experiencing, I would say more than just a bug and possibly a systemic problem with your instance of Home Assistant.

Screenshot%20from%202019-11-21%2009-50-00
Screenshot%20from%202019-11-21%2009-50-00613×674 33.5 KB

1 Like
14

You’re right but as i moved to hassio i am fixing all the errors i had previously. Now all seems working as expected. I fixed the google_calendar error, the side_panel in hassio and the mqtt_errors i had with hassbian. Now it seems fixed also this about the data_template, so… i hope to have some time without headaches… :slight_smile:

15

You can’t use data_templates in the service caller in the UI :wink:

16

Yes, now i know it !