NOT Condition possible?

And now THAT’S why I wanted to see the complete automation. Why do you change the mode in the action rather then the condition?

And yeah, we do want you to post the complete automation even if you only if you changed a single word. This would not be the first time we all spend a whole day because a tyop was made :wink: Sometimes even as simple as a capital letter.

I’m sorry, I have corrected the typo (post 19 is correct). I just edited the one word here. It was correct in the YAML editor, with the modes differing in Condition, not in Action. I understand this now looks suspicious and like an user error, I’ll try again, but I’m positive it was correct.

Don’t know why that one isn’t working but switched to the state condition:

alias: AC - when humidity over 53, start Dry
description: ''
  - type: humidity
    platform: device
    device_id: feab63e34ffcdc250e0284838d497114
    entity_id: sensor.ble_humidity_living_room_sensor
    domain: sensor
    above: 53
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - condition: time
    after: '07:50'
    before: '22:30'
  - condition: not
      - condition: state
        entity_id: climate.daikinap64316
        state: cool
  - service: climate.set_hvac_mode
      device_id: 83e6ff5154b8c396f590d02f2d737675
      hvac_mode: dry
mode: single

Hope I didn’t make a typo in the entityId :smiley:

1 Like

No, I have double and triple checked, reloaded automations, it’s not an user error. Both versions do the exact same thing I don’t want.

Yes! This (automation from post #24) works as expected. I wonder why the original didn’t. Maybe a bug with device conditions instead of state conditions? Maybe @tom_l knows?


I’ve never used device triggers or conditions, so :man_shrugging:

1 Like

What’s the emoji for “told you so” again :smiley: