Home Assistant release with the issue:
Version 0.98.1
Last working Home Assistant release (if known):
UI (States or Lovelace UI?):
Using lovelace
Browser and Operating System:
Chrome or Firefox
Description of problem:
In Automation.yaml I have this automation:
- id: Incoming call
alias: call
trigger:
platform: state
entity_id: sensor.phone
to: ringing
action:
- service: tts.google_say
data_template:
message: Call From {{ states.sensor.phone.attributes.from_name }}
entity_id: media_player.mpd
everything work well.
If I edit this automation with 'Automation Editor' it doesn't show correctly and data_template statememt is not available
Javascript errors shown in the web inspector (if applicable):
Additional information:
Would love to see this working, is the only thing stopping from fully manage automations thru the editor. need to fallback to the yaml to edit things.
related: #3258 ?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
still an issue
at least data_template can be edited via "Edit as YAML"
This is still an issue, and the workaround as @Jazzi0 says is to edit the YAML in the GUI.
Still an issue in 0.107.7
any progress to this? I just wondered why the editor just shows nothing until I found this open bug ;)
using "Edit as YAML" works, but when reloading automations with the editor, it breaks the formatting of the template.
from:
"{{ state_attr('weather.domov', 'forecast')[0].condition }}"
it "converts" it into:
'{{ state_attr(''weather.domov'', ''forecast'')[0].condition }}'
and that doesn't work...
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
still an issue