Automation failed - new word suggestion

Feature Requests
1

I think the word when the conditioning is not achieved is wrong.

Today when a condition is not achieved is says “failed”. Or have I misunderstood it is there a problem?

My suggestion is to use “achieved” instead of “failed”. When I read failed, I think something is wrong.

I have attached my automation and some pictures of the Traces

image

Executed: October 23, 2022 at 10:57:31
Result:
result: false
conditions/0
Executed: October 23, 2022 at 10:57:31
Result:
result: false
conditions/0/entity_id/0
Executed: October 23, 2022 at 10:57:31
Result:
result: false
state: 4.5
wanted_state_above: 16
conditions/1
Executed: October 23, 2022 at 10:57:31
Result:
result: false
conditions/1/entity_id/0
Executed: October 23, 2022 at 10:57:31
Result:
result: false
state: 4.4
wanted_state_above: 16
conditions/2
Executed: October 23, 2022 at 10:57:31
Result:
result: false
conditions/2/entity_id/0
Executed: October 23, 2022 at 10:57:31
Result:
result: false
state: 6.2
wanted_state_above: 16

alias: High amp
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.lgf_current_l1
  - platform: state
    entity_id:
      - sensor.lgf_current_l2
  - platform: state
    entity_id:
      - sensor.lgf_current_l3
condition:
  - condition: or
    conditions:
      - condition: numeric_state
        entity_id: sensor.lgf_current_l1
        above: 16
      - condition: numeric_state
        entity_id: sensor.lgf_current_l2
        above: 16
      - condition: numeric_state
        entity_id: sensor.lgf_current_l3
        above: 16
action:
  - service: notify.email
    data:
      message: >-
        L1: {{ states("sensor.elmatare_current_instant_l1") | float }} A L2: {{
        states("sensor.elmatare_current_instant_l2") | float }} A L3: {{
        states("sensor.elmatare_current_instant_l3") | float }} A
      title: High amp
  - service: easee.set_charger_circuit_dynamic_limit
    data:
      charger_id: EHXXYYZZ
      currentP1: 16
      currentP2: 16
      currentP3: 16
mode: single
2

Maybe it doesn’t bother me because I’m used to programming, but failed to me means it didn’t pass. Those are opposites. The output speak to the semantics of the test (the condition). If there was a problem with the condition (e.g. a template condition), then you would get an error (e.g. if the template failed to parse, meaning a syntactic issue). In other words, false means it wasn’t the desired outcome. Error would mean it couldn’t even determine a result.

3

Ok I get your point and can agree.

But I always want consistency :slight_smile:

Result says false, so maybe to make it less misunderstoodable, it should say “Stopped because a condition is false”

I have started to use HA one month ago so maybe I need to use it to get it.

So you mean that if a condition is getting and error it will say “Stopped …. Error”?