Hello,
I just wanted to mention that the HowTo that you referenced is complete, the integration of your implementation according to it is ok, with the mention that for me all the browser_mod dialogs work in Win7, Android but not in Win10, but I think this is some problem with my browser/firewall/antivirus that I am still researching.
I found the way!!! Easy and without any issue and without any cons.
In the automation Irrigation Synchronise Sensor Zone Switches
in the file garden_controller.yaml
in the package
folder, in the action
of the automation just replace the actual - service: homeassistant.update_entity
with this
- service: homeassistant.update_entity
data_template:
entity_id: >
{% if states('input_text.irrigation_zone1_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone1_switch
{% elif states('input_text.irrigation_zone2_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone2_switch
{% elif states('input_text.irrigation_zone3_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone3_switch
{% elif states('input_text.irrigation_zone4_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone4_switch
{% elif states('input_text.irrigation_zone5_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone5_switch
{% elif states('input_text.irrigation_zone6_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone6_switch
{% elif states('input_text.irrigation_zone7_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone7_switch
{% elif states('input_text.irrigation_zone8_switch_entity_id') in trigger.event.data.entity_id %}
sensor.irrigation_sensor_zone8_switch
{% else %}
none
{% endif %}
And everything seems to be working.
It should be double checked by others, just to be sure it works for all…
I can’t believe I missed that!
Myabe my excuse can be that it was a case of looking at something for so long you end up having no idea what you are looking at…
Thank you for finding this (and well done)!!
I’ll update GitHub soon.
But will this scale above 8 zones dynamically? Personally I’d rather opted for a “fixed” naming convention *zoneX and scale dynamically, than having to edit a bunch of code to adapt to different number of zones. My 2cents worth…
For the “is it raining / did it rain” - I still have an old Rainbird rainsensor which works like a switch/relay - I wired the common of my zone through it, so even it the cycle runs for some reason and it rained the valve solenoids cant turn on. The history tab will be a bit off, but the plants wont be drowned.
Ops i missed out some message in these days! I’ll try it asap!
That’s a good question. In a word the answer is, no.
But…
It would be (as far as I know) impossible to write a system that dynamically adjusts completely to any number of zones using pure yaml (I am sure with some Python modules it would be possible) and to be honest when I wrote this I never even considered more than eight as that is all I wanted In fact I never expected this much interest in it because whilst Version 1 was used by a few people as far as I could tell there wasn’t much interest or activity in its development.
As it stands now, in order to extend it you have to at least add extra input_*
. There may be other things but the only person I know who is actually doing this is @Athan. They have adapted the code and offered some suggestions for changes to make that adaptation simpler.
This change in particular is really a fix to a coding error that should never have been there in the first place and simply makes the history work as intended and restores the status quo.
I am very open to changes to make it scale to more zones and it would be great to make it as dynamic as possible but at the very least I do hope that at some point there will be documentation about what changes/additions are needed to implement this.
In principle I am entirely in agreement with this
Hmm… if I understand correctly I don’t think it will because the History is based on the actual time that actual switch is on. If your Rainbird sensor stops the switch turning on then no ‘history time’ will be recorded.
There may be other things but the only person I know who is actually doing this is @Athan.
I have a repository that i forked from @klogg and keeping it updated with his latest changes. I have choose to have up to 16 zones. Keep in mind that i haven’t change the core code (except from the changes that i have already propose to Klogg), i just manually added the extra code that needed to support the zones.
Updates
Enhancement
Better able to deal with more than eight zones (thanks to @Athan)
Bug fix
Fix History (thanks to @woody4165)
New Feature
Allow cycle start time to be an offset from sunset/sunrise (suggested by @ekkesa)
Hello everybody,
is there a step by step guide to irrigation?
I don’t really know where to start.
The HA irrigation version 2 documentation is not that great.
I have two rainbird controllers with a total of 10 cycles.
Unfortunately there is a problem with the support of the second Rainbird controller.
thank you.
The Readme and Prerequisites of this project are really well done.
Take some time to read them better…
Hi i have a issue with the updated item_cycle_start_time.yaml below, when i switch back to the previous version item_cycle_start_time.yaml all is working ok, and can’t work out why its not loading the new file and everything checks out ok in the HA logs ?
New version item_cycle_start_time.yaml view.
Previous item_cycle_start_time.yaml, loaded with all the new files minus the updated item_cycle_start_time.yaml which works fine.
Think i may of jumped the gun as there are now some package files to up load, we let you know once i have upload all the files…
All sorted now by uploading the rest of the files from packages doh …
Hi @klogg
I’m getting this strange issue when using the sliders to select the irrigation time
This is happening from 10 days or more.
What can I check ?
Thanks
Yes so am I…
Hello, I pulled the latest modifications from klogg, should these fix the History?
For me it still does not work…
Do you have a github repository where I can pull this commit from?
I had the impression it is integrated in klogg’s
No, I don’t have any github repo, I just modified the code locally…