#YAML got shifted around - what happened?

1 messages · Page 1 of 1 (latest)

edgy glen
#

I have an automation to update the weather forecast on my OpenHASP plates. It's been running fine for a couple years, then I upgraded to the latest HA and it broke.
I've verified that the YAML is correct to set all of the variables referenced in this code. The issue is that it seems like HA is flipping things around:
the code from my automation:

    - service: mqtt.publish
      data:
        topic: hasp/plates/command/json
        payload_template: >-
            [{{ b14 }}, {{ b15 }}, {{ b16 }}, {{ b17 }}]
    - service: mqtt.publish
      data:
        topic: hasp/plates/command/json
        payload_template: >-
            [{{ b21 }}, {{ b22 }}, {{ b23 }}, {{ b31 }}, {{ b32 }}, {{ b33 }}]```

When I look into the automation, it looks like it's grouping things incorrectly:
```actions:
  - data:
      topic: hasp/plates/command/json
      payload_template: "[{{ b14 }}, {{ b15 }}, {{ b16 }}, {{ b17 }}]"
    action: mqtt.publish
  - data:
      topic: hasp/plates/command/json
      payload_template: "[{{ b21 }}, {{ b22 }}, {{ b23 }}, {{ b31 }}, {{ b32 }}, {{ b33 }}]"
    action: mqtt.publish```

The automation triggers, but NONE of the steps complete due to an "unknown error"
whole plaza
#

How is that incorrect?

#

payload_template is no longer valid, replace with payload per the linked message.