I installed V5.2.10 from hacs, change version or not
No, 1 program with 3 zones. Every zone gets the exact same start time though.
Quick question for Pete. Regarding the following watering adjustment example from your Openweathermaphistory documentation on github:
{{
[(10
- day0rain
- day1rain*0.5
- day2rain*0.25
- forecast1rain*forecast1pop*0.5
- forecast2rain*forecast2pop*0.25)/10
,0]|max
}}
I was wondering if there is a reason why you are not using forecast0rain and forecast0pop in this example?
Hi Pete, i’m now in Spain and have to install the integration in my home assistant instance here.
I will try to reproduce the bug in my installation here on HA 2023.7.1.
Start time
input_datetime.startzeit_bewasserung
Inter zone delay
input_number.dauer_zone_pause
Riego relay 1 next run
Unavailable
Riego relay 2 next run
Unavailable
Riego relay 3 next run
Unavailable
Riego relay 4 next run
Unavailable
Riego relay 5 next run
Unavailable
Zone1 name
riego_relay_1
Riego relay 1 remaining
0:00:00
Riego relay 1 zone
switch.riego_relay_1
Riego relay 1 water
input_number.dauer_zone_hinten_unten
Riego relay 1 run freq
input_select.frequenz_zone_hinten_unten
Zone2 name
riego_relay_2
Riego relay 2 remaining
0:00:00
Riego relay 2 zone
switch.riego_relay_2
Riego relay 2 water
input_number.dauer_zone_hinten_oben
Riego relay 2 run freq
input_select.frequenz_zone_hinten_oben
Zone3 name
riego_relay_3
Riego relay 3 remaining
0:00:00
Riego relay 3 zone
switch.riego_relay_3
Riego relay 3 water
input_number.dauer_zone_vorne_unten
Riego relay 3 run freq
input_select.frequenz_zone_vorne_unten
Zone4 name
riego_relay_4
Riego relay 4 remaining
0:00:00
Riego relay 4 zone
switch.riego_relay_4
Riego relay 4 water
input_number.dauer_zone_vorne_oben
Riego relay 4 run freq
input_select.frequenz_zone_vorne_oben
Zone5 name
riego_relay_5
Riego relay 5 remaining
0:00:00
Riego relay 5 zone
switch.riego_relay_5
Riego relay 5 water
input_number.dauer_zone_terrasse
Riego relay 5 run freq
input_select.frequenz_zone_terrasse
Zone count
5
Remaining
0:00:00
I have a D1 mini pro controlling 5 relais for 5 zones in 1 program starting one zone after another with a pause of 2 secs in between.
I have found a circumvention for the problem by calling the Irrigation controller: reset_runtime for above switch shortly before the program start time.
I will reply after i have all installed here.
What about rain sensor, is this feature is working correctly? Because as far as I tested, binary sensor wont stop sequence.
Only postpones to another selected frequency if rain has already started before start time.
Hi Stoli,
No particular reason, I found this to be accurate enough in my area. You can try many different calculations until you find one that works for you.
The rain sensor is simply a binary sensor that stops the a program from starting if it is on.
It is designed to allow a user to develop their own model for stopping the program running in what ever way they want.
Check out GitHub - petergridge/openweathermaphistory: A home assistant sensor that uses the OpenWeatherMap API to get forecast, current obs and history data for a more complex model.
Hi Pete, I can no longer reproduce the problem in my current environment. The irrigation program started at the set start time and ran to completion. I did not find any exceptions from your integration in the log.
I made a slight change to the program as i added a binary switch for enabling/disabling the program.
That’s great news, I will investigate if that change is the key to the issue. Thanks for letting me know
Can you send me you configuration: A screenshot of the program config and each zone, and the values that you have set up in you helpers e.g. frequency options etc.
I will try to replicate your configuration to recreate this issue.
Also can you try making the program as simple as possible:
Program has only a start time
Zone only has watering time
Initially only 1 zone,
then if you could add zones in one at a time with only watering time
then add the additional attributes you use on the program/zones like frequency and interzone delay one at a time.
You can change the start time after each change so it will trigger so hopefully this will not take very long and we can track down the route cause of this issue.
Is there a way to change the rate at which calls to the openweathermap api are made? To something like every 30 minutes instead of hourly?
Hi Stoli,
The openweathermap history API is not real time he API only provides updates in hourly increments.
The internal refresh is actually ever 10 minutes but to limit the use of the free API calls there is a process to only make the call after an hour has elapsed.
Can I also have the value of each of the helpers, frequency, adjuster, irrigation enabled…
Pete
ciao Peter, dopo ultimo aggiornamento 5.3 funziona per adesso tutto. Grazie ottimo lavoro…
Piacere mio
Number 6 you can ignore, that’s from another automation.
Number 7 is an automation which sets the startdate every night to the next sunrise.