Is it possible to disable the irrigation only for the next run?
use disable service targeted to the controller you want to disable. See documentation chapter 7
But is the controller enabled again after the next schedule? I just want to skip the next irrigation.
You have to setup an automation, not very hard to achieve if your are acquainted to it
Ok. i thought/hoped there would be an implemented way to do so.
Thank you!
Hi,
I would like to split configuration.yaml.
Added this in configuration.yaml
irrigation: !include irrigation.yaml
I am getting in âCheck Configurationâ in developer tools:
Integration error: irrigation - Integration âirrigationâ not found.
I obviously created file /config/irrigation.yaml
Hi,
i created automation for Rain sensor but is not working correctly - could somebody please help?
I am getting data from aquare sensor connected to Hunter Rain sensor - wet or dry status. When the status is wet i want to disable to 0% the irrigation. But is not workingâŚ
I have also in operation the Smart irrigation system but i think both can run independentlyâŚ
Traces:
Executed: May 23, 2023 at 20:38:04
Result:
params:
domain: irrigation_unlimited
service: adjust_time
service_data:
entity_id: binary_sensor.irrigation_unlimited_c1_z2
percentage: 100
target: {}
running_script: false
limit: 10
- id: '1684865711980'
alias: Rain_senzor
description: off for whole Controller
trigger:
- platform: state
entity_id:
- binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone
condition: []
action:
- service: irrigation_unlimited.adjust_time
data:
entity_id: binary_sensor.irrigation_unlimited_c1_z2
percentage: "{% if states('binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone')
== 'wet' %}\n {{ 0 }}\n {% else %}\n {{ 100 }}\n {% endif %}\n"
- service: irrigation_unlimited.adjust_time
data:
entity_id: binary_sensor.irrigation_unlimited_c1_z1
percentage: "{% if states('binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone')
== 'wet' %}\n {{ 0 }}\n {% else %}\n {{ 100 }}\n {% endif %}\n"
- service: irrigation_unlimited.adjust_time
data:
entity_id: binary_sensor.irrigation_unlimited_c1_z3
percentage: "{% if states('binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone')
== 'wet' %}\n {{ 0 }}\n {% else %}\n {{ 100 }}\n {% endif %}\n"
- service: irrigation_unlimited.adjust_time
data:
entity_id: binary_sensor.irrigation_unlimited_c1_z4
percentage: "{% if states('binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone')
== 'wet' %}\n {{ 0 }}\n {% else %}\n {{ 100 }}\n {% endif %}\n"
mode: single
Correct code is:
irrigation_unlimited: !include irrigation.yaml
1 Like
As a general rule, when something does work not I use Developers/Template renderer to troubleshoot.
Since there is one rain sensor, instead of acting separately on each zone you could disable/enable the controller itself.
- id: '1684865711980'
alias: Rain_senzor
description: off for whole Controller
trigger:
- platform: state
entity_id:
- binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone
condition: []
action:
- service: irrigation_unlimited.{{ iif(trigger.to_state.state == "wet", "disable",
"enable") }}
I think that opening and closing braces around 0 and 100 are not needed.
Please correct me if Iâm wrong, I wrote this without being able to test it. Please double check that âbinary_sensor.lumi_lumi_sensor_wleak_aq1_iaszoneâ returns exactly what you are looking for, that is âwetâ (Developers/States)
Hope this helps
Thanks I make mistake state of the sensor is on or off even in UI is showing wet or dry . I check it through states in developer tools . Now it is functional
How do i make a repeating sequence (every hour) for two zones that are switched on one after another?
sequences:
- name: "Neusaat"
duration: "00:06"
delay: "00:54"
repeat: 12
schedules:
- time: "07:00"
zones:
- zone_id: beet
duration: "00:03"
- zone_id: terasse
duration: "00:03"
What i am getting is a schedule that runs zone 1 for 3 minutes, delays for 54 minutes, runs zone 2 for 3 minutes, waits 54 minutes âŚ
Try using the cron mode scheduler.
sequences:
- name: "Neusaat"
duration: "00:03"
schedules:
- time:
cron: "0 7-21 * * *"
zones:
- zone_id: beet
- zone_id: terasse
Heaps of information about cron available on the internet. Try searching for cron expression
Thank you for that!
Hi there,
just started with âIrrigation Unlimitedâ, I am using version 2023.2.1.
My setup contains one controller, one sequence, four zones and a scheduler for two of the zones, as said, just starting.
controllers:
name: Restra
enabled: true
controller_id: bewasserung_restra
zones:
- name: Garten
zone_id: bewasserung_garten
entity_id: "switch.bewasserung_garten_1z_switch"
show:
timeline: true
schedules:
- name: "Sonnenaufgang"
time:
sun: "sunrise"
after: "00:00"
duration: "00:15"
- name: Rasen
zone_id: bewasserung_rasen
entity_id: "switch.bewasserung_rasen_2z_switch"
schedules:
- name: "Nach Sonnenaufgang"
time:
sun: "sunrise"
after: "00:30"
duration: "00:15"
show:
timeline: true
- name: Balkon
zone_id: bewasserung_balkon
entity_id: "switch.bewasserung_balkon_3z_switch"
show:
timeline: true
- name: Vorgarten
zone_id: bewasserung_vorgarten
entity_id: "switch.bewasserung_vorgarten_4z_switch"
show:
timeline: true
sequences:
- name: "Eco"
delay: "00:02"
repeat: 3
zones:
- zone_id: bewasserung_garten
- zone_id: bewasserung_rasen
Today I decided to change the schedulers a bit, to start a little later after sunrise.
I tried to activate the changes via YAML reload in the developer section, and via service call: irrigation_unlimited_reload.
But the changes are not shown in the attributes of entities of irrigation unlimited nor in the card.
In the standard logs there isnât any message regarding irrigation unlimited.
What do I need to refresh the schedules?
Thanks a million in advance
Restart HomeAssistant.
The only solution i found 
@StefanHabel
you were right, after a restart the new settings are active.
@rgc99
is there a more convenient option?
Hmm, it should work via the reload. Maybe need to look at this further.
Thanks a lot.
please let me know which information you need from my end.
Cheers
I found that disabling / enabling the controller makes the trick, no need to restart
1 Like
Thanks @kolia
tried it in the card and via calling the services (disable / enable) directly, but it had no effect.