Why hasn't this automation triggered?

[dryheat122]

I have an automation that is supposed to open an irrigation valve when soil moisture according to sensor gets below a certain point. Here is how the trigger is set up:

The value of that sensor is currently 74. The trigger point was previously 70, but I changed it to its current value of 75 this morning. I expected that after doing that it would trigger immediately, but it has not done so after several hours. Does the value have to change before it triggers, maybe?

[BebeMischa]

Has the humidity in this period ever exceeded the 75%?
If not, there was nothing to trigger for…

[tom_l]

The numeric state trigger occurs when the value crosses the threshold you specify. So from above 75 to below 75 in your case.

There are other ways to trigger whenever a value occurs below a set point. e.g. trigger whenever a value is received below 75. So 67 to 68, 68 to 70, etc…

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Well, the picture has the 75 value in the below section, so when it moves from 75 or higher down to below 75…

@dryheat122

Automations #1: trigger only fires when it changes from not true to true

This topic is part of the community-driven cookbook where you can find other topics you might be interested in or might like to contribute to. In an automation written to run when the heating drops below 20C, the trigger will fire when the temperature changes from 20 to 19. trigger: - platform: numeric_state entity_id: - climate.study for: hours: 0 minutes: 10 seconds: 0 below: 20 It will not fire again until the temperature rises above 20C and drops fo…

[dryheat122]

Can you please share the other ways?

[tom_l]

This will trigger for any value under the value of 75:

triggers:
  - trigger: state
    entity_id: sensor.foobar
    not_to:
      - unknown
      - unavailable 
conditions:
  - condition: numeric_state
    entity_id: sensor.foobar 
    below: 75

[dryheat122]

Yes, it started out at 85%

[dryheat122]

That’s what I have:

alias: Garden Irrigation
description: ""
triggers:
  - type: humidity
    device_id: 2e973d8f812a29b0c67148e21fe923d5
    entity_id: 996b089adb801311519d048501e555ed
    domain: sensor
    trigger: device
    below: 75
conditions: []
actions:
  - type: turn_on
    device_id: 403255d471db7a0291c49472312c738b
    entity_id: e00e2b8696609b936d2421c77c973acf
    domain: switch
  - action: notify.mobile_app_pixel_9_pro_xl
    metadata: {}
    data:
      message: Garden irrigation start
  - action: assist_satellite.announce
    metadata: {}
    data:
      message: Garden irrigation start
  - delay:
      hours: 0
      minutes: 30
      seconds: 0
      milliseconds: 0
  - type: turn_off
    device_id: 403255d471db7a0291c49472312c738b
    entity_id: e00e2b8696609b936d2421c77c973acf
    domain: switch
mode: single

Oh well, I ran the valve manually so we’ll see if it triggers when the value comes back down.

[tom_l]

@dryheat122

That’s what I have:

That is nothing like what I wrote.

[BambamNZ (David)]

@dryheat122

The value of that sensor is currently 74. The trigger point was previously 70, but I changed it to its current value of 75 this morning.

What was the value when you amended the automation trigger point?
If it was already at 75 or below 75, the automation would not have been trigger, HA will not retrospective review values of tiggers in automations, it is point in time action. When the threshold is crossed HA will trigger the automation.