HA Smart Irrigation automation - reset bucket only when about irrigation_unlimited

[rgc99]

You are right, split the automation into two separate tasks; adjustment and bucket reset. I think history_stats may be your friend here. First create a sensor to count the number of times the system was on yesterday and then an automation to reset the bucket if the system was on:

sensor:
  - platform: history_stats
    name: Irrigation Unlimited yesterday run count
    entity_id: binary_sensor.irrigation_unlimited_c1_m
    state: “on” 
    type: count 
    end: "{{ now().replace(hour=0, minute=0, second=0) }}" 
    duration: 
      hours: 24 
 
automation: 
  - alias: HA Smart Irrigation reset bucket 
    trigger: 
    - platform: time
      at: 04:30
    condition:
      condition: numeric_state
      entity_id: sensor.irrigation_unlimited_yesterday_run_count
      above: 0
    action:
    - service: smart_irrigation.smart_irrigation_reset_bucket
    mode: single

Lots of possibilities here but hopefully this will get you going. Let me know how you get on so we share it.

[Stan-Gobien]

Hey, thanks for your answer.
So the idea is that we count the number of times irrigation unlimited has run in the past 24 hours (yesterday might be a misleading name). If the count is higher than 0, meaning it has run then we reset the bucket.
Good idea.

The question is, when should we call the reset bucket automation?
Ideally it should be called right after the run has finished, but because of variable schedules that's a bit difficult.
The "sensor.smart_irrigation_daily_adjusted_run_time" gets calculated at 23h.
I'm pretty sure that the result of that calculation is very different depending on the value of the bucket.
So would it be best to run the automation at for instance 22h?

[Stan-Gobien]

Considering if the run was perhaps at sunrise we still loose most of the day of raining or vaporization if we reset only at 22h in the evening.

So still not ideal. In my situation I can schedule the reset perhaps at 9h in the morning, because I will always schedule the automatic runs a bit before sunrise.

The best solution would be some kind of sensor "run finished" that changes from off to on on finish and could thus trigger the reset automation.

Could we not trigger the reset automation on the state attribute "Status" of "binary_sensor.irrigation_unlimited_c1_m" changing from 'on' to 'off'?

[Stan-Gobien]

Just thinking a bit out loud here:

Could we not trigger the reset automation on the state attribute "Status" of "binary_sensor.irrigation_unlimited_c1_m" changing from 'on' to 'off'?

[rgc99]

Rereading the docs; calculations are done at 23:00 and the bucket should be reset after any irrigation so yes let's do that. Here is the complete automation.

automation:
  - alias: Smart Irrigation adjustment
    description: Adjust watering times based on smart irrigation calculations
    trigger:
      - platform: time
        at: "23:30"
    action:
      - service: irrigation_unlimited.adjust_time
        data:
          entity_id: binary_sensor.irrigation_unlimited_c1_z1
          actual: >
            {% set t = states('sensor.smart_irrigation_daily_adjusted_run_time') | int %}
            {{ '{:02d}:{:02d}:{:02d}'.format((t // 3600) % 24, (t % 3600) // 60, (t % 3600) % 60) }}
    mode: single

  - alias: Smart Irrigation reset bucket
    description: Resets the Smart Irrigation bucket after watering
    trigger:
      - platform: state
        entity_id:
          # Add Irrigation Unlimited sensors here
          - binary_sensor.irrigation_unlimited_c1_m
        from: "on"
        to: "off"
    action:
      - service: smart_irrigation.reset_bucket

[Stan-Gobien]

I've implemented the new automations as suggested.