Smart Irrigation - save water by precisely watering your lawn/garden

jeroenterheerdt · June 16, 2021, 6:39pm

yes you can use a cumulative sensor (see the github). you need to handle the rain forecast yourself.

tc23 · June 29, 2021, 3:18pm

@jeroenterheerdt I’m having an issue where the daily adjusted run time only calculates it to zero, and so the irrigation never runs. I have tried manually changing that run time and the calling the service to recalculate it and it sets it back to zero. Any idea where I could troubleshoot or what could be causing that?

jeroenterheerdt · June 29, 2021, 4:46pm

so if your daily netto precipitation (which is by default calculated by taking the average of the hourly netto precipitation) is above 0 the daily run time won’t run, because irrigation is not necessary. So, take a look at your hourly netto precipitation and daily netto precipitation to see if that matches up with your expectations / weather patterns.

tc23 · June 29, 2021, 5:09pm

So I have a -.17 netto precipitation on the hourly. I don’t have a netto precipitation on the daily.

jeroenterheerdt · June 29, 2021, 7:05pm

it’s only updated at 11PM by default

rjbarrosog · July 7, 2021, 10:33am

Thank you so much for the good work. This integration is working very well for me! I have one question however: if i change my sprinkler or i need to update the ET reference values do I need to redo every step of the configuration or can i modify this variables somewhere?

jeroenterheerdt · July 7, 2021, 4:13pm

Hi @rjbarrosog - thanks for checking in. If you want to go back and change your settings afterwards, you can either delete the instance and re-create it or edit the entity registry under config/.storage at your own risk.

rjbarrosog · July 7, 2021, 6:41pm

Thank you so much for the quit turnaround. This was what i was thinking, not optimal but efficient…

Do you think this could be a possible upgrade: being able to alter the configuration so if you move from your home, change the sprinklers or you get updated ETo data for your location you don’t need to redo the integration? or even if i build my weather station and i don’t want to rely no more on the OWP, it would be easier.

Other than this, the integration is very good an I recommended it to everyone dealing with irrigation. I got water savings of about 50% compared to a timebased (defined by me) schedule.

Thank you

jeroenterheerdt · July 7, 2021, 7:00pm

we’re actually tracking that here: [REQ] make number_of_sprinklers, flow, area configurable using options flow as well. · Issue #27 · jeroenterheerdt/HAsmartirrigation (github.com), but to be honest I have not have the time to make that happen.

rickroetenberg · July 26, 2021, 7:09pm

Anyone a replacement website for http://wcatlas.iwmi.org/? This page isn’t working since a few days.

froggy.laurent · August 23, 2021, 9:08am

i found some data for France on meteofrance

krock · August 29, 2021, 8:43pm

How would I implement this if I wanted to target a certain water amount (1" each week) on my lawn?

jeroenterheerdt · August 31, 2021, 4:25pm

short answer: you wouldn’t. This component is not really suitable for that, although you can learn from how it was build. Basically, you will need to figure out the throughput of your system and then figure out how long to run the system for to get to 1"

jeroenterheerdt · August 31, 2021, 4:31pm

no internal version that I know of, so check with your local weather service. I sent an email to the owner of the system to ask what is going on and if it’s coming back.

stevehollx · September 8, 2021, 4:58pm

I just installed this and have a question that I can’t determine after reading the docs.

Can someone help me understand when to use sensor.smart_irrigation_daily_adjusted_run_time versus sensor.smart_irrigation_hourly_adjusted_run_time?

I understand that one updates daily, and one updates hourly. The documentation states to use the daily run time for irrigation automation, but I don’t understand why. Wouldn’t you want to trigger irrigation off the hourly stat, since it is updates more regularly, and would have adjusted if there was rainfall between 23:00 when the daily stat updates, and when the irrigation is set to run?

stevehollx · September 8, 2021, 5:15pm

I found a partial answer in an earlier post:

jeroenterheerdt:

What it currently does: the hourly is just a tracker to see what is happening, as you described. The daily adjusted run time is just a final update at 23:00 hours, so you can plan to water early in the morning, to compensate for yesterdays net loss of moisture, assuming it is < 0.
both daily and hourly adjusted run time look at the same data, the one is just done only once a day, and the other is done during the day to show process and what is expected to the user. You should see daily to match up at 23:00 hours with whatever the hourly is at that point. Hourly is on a day level by the way, it is just updated every hour. hope that makes sense.

And there is no risk for running irrigation without need, since even if the next day is raining, it will just compensate for what has already been lost, it is not predicting the future or whatever. if it rains for 3 days afterwards, it will not irrigate until enough moisture has been lost so compensation is required again.

I still don’t really follow why one would ever even irrigate with the daily snapshot from 23:00, though.

Wouldn’t you always just want to use the hourly and clear the bucket at that time? What is the advantage of the daily stat over hourly?

Is it simply just providing some loose normalization/aggregation to be able to view and trend irrigation time daily over a longer term?
Or is the daily stat allowing for aggregating run time across multiple days, wheres hourly only gives you insight for that day and would require irrigating daily if basing off that stat?

jeroenterheerdt · September 8, 2021, 6:22pm

the hourly ART is the ART at that hour, so imagine it rains very hard in that hour. Your ART will be 0. So if you happen to take just that hourly ART you don’t get any irrigation, while the other 23 hours of the day could have been very sunny, desert type weather so when looking at all 24 hours you actually would want to irrigate. That’s where the daily ART comes in: it averages over all 24 hourly ARTs (or takes the most recent if you happen to have that sensor configuration) to cover for these types of situations. Hope this helps.

adrien.b · September 20, 2021, 7:06pm

Hi,

I installed this integration a few days ago, and it works great.
I’m using OWM data for the moment, but I have a Popp Z-Rain meter that indicates both rain rate (mm/h) and cumulated water volume in m³ and mm. So I plan to use the cumulated rain gauge to replace OWM, as I’ve seen that the gauge said 2mm of rain during a day while OWM said 20mm.

But as the Z-Rain cumulated value should be manually reset, I’d like to confirm if I should reset it daily (for example just after the daily adjusted run time is computed by H.A.S.I), or should I reset it like the bucket only after irrigating ?

Thanks

jeroenterheerdt · September 20, 2021, 7:57pm

You should reset the cumulative sensor for every new day, regardless of whether or not the irrigation ran

froggy.laurent · November 22, 2021, 9:07am

hi
in the case i would like to run irrigation every 2 day, will it work if i make 2 automation ?

irrigate every 2 days
reset bucket every day

something like that :

alias: '[test] irrigate every 2 days'
trigger:
  - platform: time
    at: '08:00:00'
condition:
  - condition: template
    value_template: '{{ now().timetuple().tm_yday % 2 == 0 }}'
  - condition: numeric_state
    entity_id: sensor.smart_irrigation_daily_adjusted_run_time
    above: '0'
action:
  - service: switch.turn_on
    target:
      entity_id: switch.sprinkler_1
  - delay:
      seconds: '{{states("sensor.smart_irrigation_daily_adjusted_run_time")}}'
  - service: switch.turn_off
    target:
      entity_id: switch.sprinkler_1
  
mode: single

then

alias: '[test] reset bucket every day'
description: ''
trigger:
  - platform: time
    at: '09:00:00'
action:
  - service: smart_irrigation.smart_irrigation_reset_bucket
mode: single