Reloading configuration does not have any effect indeed. I’ve been used to enable/disable the controller with an automation for a while to get it updated. I just checked again and I do confirm that.
could you tell us which service you called for what entity? Should be
service: irrigation_unlimited.disable
data:
entity_id: binary_sensor.irrigation_unlimited_c1_m
and then
service: irrigation_unlimited.enable
data:
entity_id: binary_sensor.irrigation_unlimited_c1_m
I created a script
alias: Irrigation_disable_enable
sequence:
- service: irrigation_unlimited.disable
data:
entity_id: binary_sensor.irrigation_unlimited_c1_m
- delay:
hours: 0
minutes: 0
seconds: 10
milliseconds: 0
- service: irrigation_unlimited.enable
data:
entity_id: binary_sensor.irrigation_unlimited_c1_m
mode: single
and ran it several times. The changed settings in my irrigation.yaml are not recognized by irrigation unlimited. All entities remain unchanged.
I played a bit with the script, moved the configuration back to configuration.yaml and again to the included irrigation.yaml
ok, eventually it turned out that reloading config, disabling and enabling led to a situation that the new settings are picked up.
alias: Irrigation_disable_enable
sequence:
- service: irrigation_unlimited.reload
data: {}
- service: irrigation_unlimited.disable
data:
entity_id: binary_sensor.irrigation_unlimited_c1_m
- service: irrigation_unlimited.enable
data:
entity_id: binary_sensor.irrigation_unlimited_c1_m
mode: single
Well done. To get things even more automated reload could be added at the beginning
service: irrigation_unlimited.reload
data: {}
I do believe it is now fixed. If anyone is willing to install from repro and let me know it would be appreciated. Like to draw a line under this and release.
Sorry, I posted this morning, without replying to you, you may have missed it. Just checked, reloading configuration updates duration. Thanks
My installation features a large circuit with many buried pipes, 12 valves are currently managed by Irrigation Unlimited, soon 14. Pressure of the main output pipe is monitored in order to detect any leak when all valves are closed. I’m now in the process install the water consumption monitoring of each circuit (I use sequence mainly in order to avoid watering overlap, even if I could very well open several valves at the same time). Now comes the need to monitor any possible overconsumption when each valve is open. It is fairly easy to calibrate water consumption for each circuit thanks to a watering metering system that reports water consumption to HA
Then based on each valve opening time it would be easy to detect whether water consumption is normal, under normal, or over normal.
It would be great to be able to display an alarm status for each circuit directly is irrigation unlimited card. It would be great indeed to display also water consumption, but the space is scarce I don’t see how it could be managed.
I could very well display that information on a specific card, but I think it would be nice to display at least an alarm status directly in Irrigation Unlimited card.
Any thoughts?
Great, thanks a lot. The code has been released as a pre-release. However I don’t see where in hacs you can choose the version any more. If you had previously selected ‘Show beta versions’ then I think you will get the update notification. Otherwise, if things look good will do general release soon.
@rgc99 Great integration. I am just looking to setup a manual runs. I am using the manual card in the documentation and if I pick the controller and a sequence it works. I am looking to on off a single zone for X minutes. I don’t see an error but nothing happens.
Thoughts?
Hi,
I am running last beta version - rain sensor - not more working. I have test 3 automatization but controller still showing running normaly - none zero.
State of my rain senzor is now off so the controller should be donw…
alias: Rain
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_m
percentage: >
{% if states('binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone') ==
'off' %}
{{ 0 }}
{% else %}
{{ 100 }}
{% endif %}
mode: single
alias: Rain_test
description: off for whole Controller
trigger:
- platform: state
entity_id:
- binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone
condition: []
action:
- choose:
- conditions:
- condition: state
entity_id: binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone
state: "off"
sequence:
- service: irrigation_unlimited.adjust_time
data:
enitity_id: binary_sensor.irrigation_unlimited_c1_m
percentage: 0
- conditions:
- condition: state
entity_id: binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone
state: "on"
sequence:
- service: irrigation_unlimited.adjust_time
data:
enitity_id: binary_sensor.irrigation_unlimited_c1_m
percentage: 100
mode: single
alias: Rain_senzor
description: off for whole Controller
trigger:
- platform: state
entity_id:
- binary_sensor.lumi_lumi_sensor_wleak_aq1_iaszone
to: "off"
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') ==
'off' %}
{{ 0 }}
{% else %}
{{ 100 }}
{% endif %}
- 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') ==
'off' %}
{{ 0 }}
{% else %}
{{ 100 }}
{% endif %}
- 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') ==
'off' %}
{{ 0 }}
{% else %}
{{ 100 }}
{% endif %}
- 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') ==
'off' %}
{{ 0 }}
{% else %}
{{ 100 }}
{% endif %}
mode: single
Thanks for finding this out. It will also help anyone wanting to try out the latest version as a pre-release.
On that note if any problems arise it would be best to open an issue report but please provide your config and perhaps even more importantly the irrigation unlimited log files. These can be found under Settings → System → Logs. Enter in the “Search logs” box irrigation_unlimited and press the “Load Full Logs” button. Paste what is displayed into a “fenced code block” - that is three back ticks on a line of their own at the start and end. This will help a lot.
Hi the problem is the log is totally empty none error nothing … I create the issue on GitHub . Thanks for reply.
@rgc99: I’m using your piece of code in order to change automatically the watering time on all zones. Being based on average component, it will fail starting 2023.04 (I’m still running 2023.03). Are you still using it? Did you find another way to compute average temperature and raining? Thank you
I am still using the average component but not the way as per the documentation. I also receive the message but it also seems to still work. Looks like it has been reported and fixed but not released. It seems other users have done a manual install.
Thank you, yes I’ll do a manual install. Would you kindly let us know the adjustments you made on this part.? I’ve a Davis VP2 PWS with evapotranspiration measurement. I was thinking to give a try to HA smartirrigation but at the same time I’d like to keep the footprint reasonable.
I no longer use the wundergroundpws integration. I updated my PWS to a Fine Offset HP2553 which is rebranded under many names like ecowitt. This unit can feed the weather data to a custom server. A bit of PHP code to feed a MySQL db, all done on my NAS, and the data is locally at hand. From there I use the HA SQL platform to grab the info from the db and setup a bunch of sensors. Everything I want to know about the weather is available without crossing the web. Works a treat.
However, It has been raining so much over the last couple of years that I enclosed my vegetable garden to control the water. Weather station not so useful now. I purchased a soil moisture meter and adapted the automation to suit. Working quite well.
Same with me. I collect and process all data locally and use it directly. While you need to protect yourself from the water, it is quite the opposite here, we are looking for water 
Hopefully I’ve a well equipped with a pump that makes me independent.
On a side note, I wanted to “buy you a coffe” and my banking system refused to do it, suspecting a fraud. Can we send PM on this platform, so would could have a private chat? I could make a direct money transfer.
Just setting up my system. Trying to work out how to represent my hierarchy.
I have the following:
KitchenValve: this opens and closes the valve that feeds my outdoor tap
OutdoorTapGardenaValve: this is a Gardena valve that currently, is overkill, but I have purchased for future permanent system enhancements (currently using portable sprinklers but may use this in future for underground Gardena system) - this is an extra layer of water security actually on the outdoor tap so for water to flow through to sprinklers, both KitchenValve and OutdoorTapGardenaValve will need to be open
JohgeeTuyaDualValve: this is connected to the OutdoorTapGardenaValve and has valves for Zone1 and Zone2 sprinklers
So I have a hierarchy of 3 valves. How do I represent that hierarchy in yaml?
So if I understand well KitchenValve and OutdoorTapGardenaValve are in series and JohgeeTuyaDualValve is connected to these.
Make a group of the two firsts, declare it at controller level, and then create one zone with two switches each one representing a zone.
You may wish to set-up a preamble and postamble depending on your set-up.
irrigation_unlimited:
controllers:
name: "Controler 1"
entity_id: switch.valve_group
zones:
- name: x1
entity_id: switch.valve_zone1
- name: x2
entity_id: switch.valve_zone2
Replace by your entity ids