Hass.io automation conditions configuration - 'or' & 'and' options?

Installation Home Assistant OS
1

Hi guys, I’ve been adding a new automation to push a PB notify to my phone, of when local wind speed and any of a small range of directions is valid. (like wind >25kmh and direction is N, or NNW, or NW).

In hass.io automation GUI there is an obvious option to add multiple conditions to an automation trigger, but not an obvious check box to make them ‘or’ or ‘and’ with the previous condition. It seems from looking at the my automations.yaml that it’s ‘anded’ by default.
Is there a way to ‘or’ all the conditions in the actual GUI without having to text edit stuff in the yaml file afterwards ?
Hope that makes sense…
Martin

1 Like
2

Maybe I put the question in the wrong forum ?
Or should this be a feature request if it’s not possible in hass.io currently ?
Anybody :slight_smile:

3

I’m having the same problem with multiple or conditions. Text editing the yaml file only produces an error:

Unsupported condition: or

Would be really good to have it in the GUI.

4

I am having many of the same problems. Here is a link to my post (https://community.home-assistant.io/u/budlyte). I am beginning to think the CONDITION OR is not supported by hassio. I have tried every thing including automation right out of the documentation and nothing passes the config check. I also don’t think anyone on the forum has an answer so I am going back to multiple automations each checking one condition.

If you have any insight please share.

5

Interesting. I have a config that passes validation now and does load, but I’m yet to get a trigger result from it. That might be because the conditions of wind direction and speed have just not happened yet, but the longer it takes the more doubt I have…
Here is the code block that passes validation using OR conditions. Keep in mind that the sub block syntax ordering was originally created by hassio automation GUI (as default AND, then I edited to an OR manually), so it seems to read somewhat backwards in the order I’d have created it. (any comments about why that is ?)

- action:
  - data:
      message: 'BOM Adelaide says slope soaring wind at {{ states(''sensor.bom_parafield_wind_speed_kmh'')
        }} kmh '
      target:
      - device/Galaxy S4
      title: Slope wind notification
    service: notify.my_notifications
  alias: Notify Slope Soaring wind
  condition:
    condition: or
    conditions:
    - condition: state
      entity_id: sensor.bom_adelaide_wind_direction
      state: NW
    - condition: state
      entity_id: sensor.bom_adelaide_wind_direction
      state: NNW
    - condition: state
      entity_id: sensor.bom_adelaide_wind_direction
      state: N
  id: '1515112066303'
  trigger:
  - above: '10'
    entity_id: sensor.bom_adelaide_wind_speed_kmh
    platform: numeric_state