Question about config.yaml vs Configurator

Tags: #<Tag:0x00007f77f8819968>

so I noticed a few things as a noob to this:

  1. when using the configurator to set up automations, it puts the automation out of order compared to what you would see an as example on the HA page
  2. when i modify something simple like order, or try to add a comment in configurator, it doesnt save once I save, exit and eventually go back to view the config via Configurator…why is that?
    Configuration example:
- id: '1581688049688'
  alias: Office No Motion Day
  description: ''
  trigger:
  - entity_id: binary_sensor.office_sensor_sensor
    for: 00:10:00
    from: 'on'
    platform: state
    to: 'off'
  condition:
  - after: sunrise
    before: sunset
    condition: sun
  action:
  - data:
      transition: 30
    entity_id: light.osram_lightify_flex_rgbw_ee4d0200_level_light_color_on_off
    service: light.turn_off

HA Site Example:

 alias: Motion Sensor Lights On
  trigger:
    platform: state
    entity_id: binary_sensor.ecolink_pir_motion_sensor_sensor
    to: 'on'
  condition:
    condition: time
    after: '07:30'
    before: '23:30'
  action:
    service: homeassistant.turn_on
    entity_id: group.office_lights
    data:
      transition: 15

It sorts the options alphabetically. It makes the resulting automation more challenging for a human to read but, for whatever reason, that’s how it works.

It doesn’t save added comments and if it finds existing comments it will remove them.
School of Hard Knocks: the Automation Editor