It’s only a small irritation but why can’t input_* services be writtten For example: - service: input_text.set_value entity_id: input_text.my_input_text value: Some text here Instead of - service: input_text.set_value entity_id: input_text.my_input_text data: value: Some text here O…

All extra attributes go inside data, even entity_id. entity_id is also the only exception to the rule (it can go inside or outside). If this change were to go through, this would be the only service that doesn’t use data/data_template. Why does it require data? Because under the hood, the call.s…

[image] petro: even entity_id. entity_id is also the only exception to the rule (it can go inside or outside) In some instances placement of entity id is actually really specific and inconsistent: Inconsistent usage of `entity_id` in automations/scripts depe…

Yep, that’s why you’ll notice most of my support posts always have this format (because it works 100% of the time): service: x.y data: entity_id: a.b

Except for this one instance: [image] TTS to read state of an entity Configuration Try it like this: action: - data: volume_level: 0.2 entity_id: media_player.bose_soundtouch service: media_player.volume_set - service: tts.google_translate_say ent…

Why do input_* need 'data'?

Archive Month of "What the heck?!" (2020)

tom_l September 1, 2020, 1:30pm 5

Except for this one instance: