Maybe the working configuration just above your post may help you
Agree, but HASmartirrigation measuring the times, with the sequence you need also the duration as parameter. How integrate this together is the question
See here for the details on how to integrate the two systems. You will need to tailor the action: â data: section to suit your needs.
You might need to alter the graph to display all the zones. Please post your graph yaml. Here is one from my own system showing three zones using apexcharts-card.
type: custom:apexcharts-card
header:
show: true
title: Watering timeline
show_states: false
graph_span: 10d
span:
start: day
offset: '-7day'
all_series_config:
type: column
group_by:
duration: 1d
func: sum
fill: 'null'
show:
as_duration: minute
now:
show: true
label: Today
series:
- entity: binary_sensor.irrigation_unlimited_c1_z1
data_generator: |
return entity.attributes.timeline.map((item) => {
const sd = new Date(item.start);
const ed = new Date(item.end);
return [sd, (ed - sd) / 60000];
});
- entity: binary_sensor.irrigation_unlimited_c1_z3
data_generator: |
return entity.attributes.timeline.map((item) => {
const sd = new Date(item.start);
const ed = new Date(item.end);
return [sd, (ed - sd) / 60000];
});
- entity: binary_sensor.irrigation_unlimited_c1_z4
data_generator: |
return entity.attributes.timeline.map((item) => {
const sd = new Date(item.start);
const ed = new Date(item.end);
return [sd, (ed - sd) / 60000];
});
yaxis:
- decimals: 0
apex_config:
title:
text: minutes
apex_config:
tooltip:
enabled: true
x:
format: dd MMM
Produces this:
Thanks for lot for your help. I managed to get it as expected with different colors. What a card!
@rgc99 thanks for the unlimited irrigation integration, it is working great for me. I have a RainBird wifi setup, an intigrated that with HASSIO via rainbird intigration, which now provide the sensors to open sprinkler valves.
Hey there,
Iâm wondering what the best way would be to implement a master solenoid. In actual fact, it is really just a relay that switches the mains for my 24V supply. Iâm trying to reduce the overall load and having the supply connected to the mains for 99% of the time is somewhat wasteful.
I would like to be able to specify another entity for example on each of the zones, as I do have more than one 24V supply, which incidentally is also used for non-irrigation solenoids.
One option would be to use a couple of Tasmota relay units and use the âBacklogâ function to achieve this however would be good to have it in the yaml for visibility.
Cheers,
Paul
Hi Paul,
The controller takes an entity_id like the zones. The controller will come on when any of the zones are on. In addition the controller has pre & post amble settings which might be useful, more information can be found in the documentation.
The entity_id can actually be a list either a CSV string or YAML style using dashes. With this you can turn on multiple devices without using a tracking automation.
Just done a custom integration. Using a cheap valve controller from Automatic 4-zone Lcd Display Watering Timer Irrigation System Garden Water Timer Controller With 2 Solenoid Valves - Garden Water Timers - AliExpress , wedged in a ESP8266, a step-up converter and a 3-to-8 decoder I can now control the valves from HA. Feeding it from 3.3V.
For the time being I still use a link-tap as main solenoid, the DIY unit is to split the one main into 4 distinct channels so I have enough water pressure on each one.
What currently works : have full control over the valves from HA using MQTT commands like cmnd/irrigation4_/VCLOSE 4.
What does not work yet: although my unit publishes the valve status tele/irrigation4_/SENSOR = {"Valves":{"v1":"1.00","v2":"0.00","v3":"0.00","v4":"1.00"}} I have yet to figure out how I get HA to recognize it.
So you mean I could put multiple entity_idâs in each of the zones below for example?
zones:
- zone_id: '1'
name: 'Front Garden'
entity_id: 'switch.irrigation_solenoid_1'
- zone_id: '2'
name: 'Front Steps'
entity_id: 'switch.irrigation_solenoid_2'Sure, stems back to issue #17 some time back. Here is a few ways to write the configuration.
zones:
- zone_id: '1'
name: 'Front Garden'
entity_id: 'switch.irrigation_solenoid_1,switch.irrigation_solenoid_3'
- zone_id: '2'
name: 'Front Steps'
entity_id: [switch.irrigation_solenoid_2,switch.irrigation_solenoid_4]
- zone_id: '3'
name: 'Another zone'
entity_id:
- switch.irrigation_solenoid_5
- switch.irrigation_solenoid_6
All makes sense now, thanks for the pointers.
can share your the lovelance configuration?
your configuration is beautifulâŚ
I asked this before but still struggling:
irrigation_unlimited:
controllers:
preamble: "00:01"
zones:
- name: "Ăim 1"
entity_id: "switch.relay_1"
- name: "Ăim 2"
entity_id: "switch.relay_2"
- name: "Damlama"
entity_id: "switch.relay_3"
- name: "BoĹ Vana"
entity_id: "switch.relay_4"
sequences:
- delay: "00:01"
name: "Ăim Sulama 2"
schedules:
- name: "Gubre 2 11_18_08_2022"
time: "06:00"
zones:
- zone_id: 1
duration: "00:06"
- zone_id: 2
duration: "00:08"
- zone_id: 3
duration: "00:08"
So, i have â00:01â preamble and â00:01â delay on the sequences. The result is that the controller state goes to on, waits 1 min preamble time, then starts zone 1 and waits 1 min in between zones. So far so good.
I have an automation which should warn me to from a cast speaker to close the doors since the Zone 2 sprinkler can water inside. It should warn me 1 minute earlier than the Zone 2 sprinkler start time. If i use the state of binary_sensor.zone2, it is much too late because the sprinklers are already started. Now i use the state of binary_sensor.zone1 to turn to off, since it is the start of 1 minute sequence delay time.
- alias: Irrigation Start Warning
trigger:
platform: state
entity_id:
- binary_sensor.irrigation_unlimited_c1_z1
from: "on"
to: "off"
action:
- service: script.tts_resume
data:
msg: Irrigation starts, please close the doors.
The state and attribute âstatusâ of binary_sensor.zone2 is only on when it is actually watering. During the start delay sequence there is no âonâ state on any part of the binary_sensor.zone2.
I want to tie this automation to actual Zone 2 sensor, since right now if the irrigation sequence is not in order of Zone1 to Zone2, the notification wonât work. I only need the warning message for Zone2. Thanks.
I would turn zone 2 into a script/automation. Remove the entity_id: for zone 2 in the configuration. Now listen for zone 2 to turn on similar to what you do above.
- alias: Irrigation for Zone 2
trigger:
platform: state
entity_id:
- binary_sensor.irrigation_unlimited_c1_z2
from: "off"
to: "on"
action:
- service: script.tts_resume
data:
msg: Irrigation starts, please close the doors.
Add to the action: section of the above a 1 minute âwarningâ delay, then turn on the valve, another delay with the value obtained from the current_duration attribute from zone 2 and finally turn off the valve.
Something like this (totally untested but to show you my thinking)
- alias: Irrigation for Zone 2
trigger:
platform: state
entity_id:
- binary_sensor.irrigation_unlimited_c1_z2
from: "off"
to: "on"
action:
- service: script.tts_resume
data:
msg: Irrigation starts, please close the doors.
- delay: 60
- service: switch.turn_on
target:
entity_id:
- switch.???? # Whatever was in entity_id: for zone 2
- delay:
seconds: {{ state_attr('binary_sensor.irrigation_unlimited_c1_z2',current_duration') | float(0) }}
- service: switch.turn_off
target:
entity_id:
- switch.???? # Whatever was in entity_id: for zone 2
2 Likes
Thank you very much for the latest nice addition in irrigation card. I started to experiment the manual timer and I found some kind of side effect. In order to get the manual timer working, the related zone needs to be enabled. By doing so, the sequence will resume automatically which I do not wanât precisely because I want to irrigate just for a certain period of time. Is there something Iâm missing, is it what is expected or is it something that could be changed? Thank you
It might be best to open an issue where we can work through it. Could need configurations and some step-by-step details.
Once you installed the companion card, create a blank card, in the editor add
type: custom:irrigation-unlimited-card
name: Any name
I am wondering if anyone out there is running this against a Hunter Hydrawise controller like me.
Here is what i am observing:
I have 24 zones of various types of watering solutions (rotors, subsurface drip, etc.)
I thought I had everything tuned perfectly and aligned to our specific irrigation needs which is delivered to me via email (and API) for my specific house, so if the lawn needs 0.5", everything changes vs. 0.25", including variable order of zones.
What I learned is that the Hunter controller apparently has a maximum zone time of 15 minues when the API manual start is called.
This is an issue for all my subsurface irrigation that needs 30-45 minutes.
I only figured this out by observing the Hunter online app at the same time IU was running a sequence. What effectively happens is that any time called for above 15 minutes never happens. IU assumes the zone is running until it sends the âOFFâ request.
I tried to diagnose whether it was somehow connected to what I put as time per zone that I configured in the Hunter app, but that did not matter at all.
Before I change everything to compensate for this limitation, i wanted to send it out to see if anyone else encounter this same issue.
Thanks for any help.
Hello, I am awe of this integration and want to use it. I have a toro Bluetooth 6 zone controller with a rain sensor.
I can not see a way to connect thisâŚAnd advise would be appreciated thanks