Automation editor changing subsequent chevrons for "|"

Configuration
,
1

I have an auromation to switch off a charge point when a couple of conditions are met. However, when the automation is saved it changes subsequent chevrons, after the template_value to “|” any reason for this? please see automation below: especially the second line with value_template. I believe its causing the automation to fail, although not with any errors. It does this with other automations.

Ill just add that im using the automations editor with the “edit yaml” option.

alias: Auto Van Charge Off
description: Turn Van Charging off
trigger:
  - platform: template
    value_template: >
      {{ (states('sensor.sofar_gen_watts') | float(0) +
      states('sensor.sofar2_gen_watts') | float(0)) <= 6.8}}
  - platform: template
    value_template: |
      {{ states('sensor.sofar_battery_soc') | int(0) <= 95 }}
condition: []
action:
  - service: homeassistant.turn_off
    entity_id: switch.van_switch
mode: single
2

This > and this | are valid ways to indicate the YAML option’s value continues on one or more lines.

syntax - How do I break a string in YAML over multiple lines? - Stack Overflow

That’s unlikely.

Your automation’s two Template Triggers behave like this:

  1. Triggers at the moment the total generated power is equal to or decreases below 6.8. Further decreases will not serve to trigger the automation.
  2. Triggers are the moment the battery’s SOC is equal to or decreases below 95. Further decreases will not serve to trigger the automation.
3

Thanks for the reply as long as its a valid character thats OK. The failure must be somethuing else I have done. Whats the reason behind the editor changing the chevron when the automation is saved?

4

That’s what the developers of the Automation Editor decided to use as the default line-continuation character. There are several other YAML and Jinja2 conventions that are used to format scripts and automations.

What is the exact nature of the failure?

If it fails to trigger, review the explanation I posted above.

5

Thanks, sorry for sounding so stupid! But I hadnt saved the automation after fixing a problem!!