Pocketoption unleash the power of binary options.
This integration is for irrigation systems large and small. It can offer some complex arrangements without large and messy scripts. This integration will complement many other irrigation projects.
Home Assistant makes automating switches easy with the built in tools available. So why this project? You have a system in place but now you have extended it to have a number of zones. You don't want all the zones on at once because of water pressure issues. Maybe you would like each zone to have a number of schedules say a morning and evening watering. What about water restrictions that limit irrigation systems to certain days of the week or days in the month, odd or even for example. Perhaps you would like different schedules for winter and summer. Now you would like to adjust the times based on weather conditions, past, present or future. Let's turn a zone or even a controller off for system maintenance. Starting to sound more like your system? Finally what's going on now and what's up next.
Each controller has an associated (master) sensor which shows on/off status and other attributes. The master will be on when any of its zones are on. The master sensor can have a pre and post amble period to activate or warm up the system like charge up a pump, enable WiFi or turn on a master valve. The master sensor has a number of service calls available to enable/disable all the zones it controls.
Zones also have an associated sensor which, like the master, shows on/off status and various attributes. Zones sensors have service calls that can enable/disable and provide manual runs. Also adjust run times in automation scripts using information from integrations that collect weather data like OpenWeatherMap, BOM, weatherunderground and many others. Go crazy with projects like HAsmartirrigation. Easily integrate probes and sensors from ESPHome for real-time adjustments. Examples provided below.
Unlimited controllers. Unlimited zones. Unlimited schedules. Schedule by absolute time or sun events (sunrise/sunset). Select by days of the week (mon/tue/wed. ). Select by days in the month (1/2/3. /odd/even). Select by months in the year (jan/feb/mar. ). Overlapped schedules. Unlimited sequences. Operate zones one at a time in a particular order with a delay in between. A 'playlist' for your zones. Hardware independent. Use your own switches/valve controllers. Software independent. Pure play python.
*Practical limitations will depend on your hardware.
Irrigation Unlimited is comprised of controllers, zones and schedules in a tree like formation. Each controller has one or more zones and each zone has one or more schedules. Controllers and zones will have a binary sensor associated with each one so they can be intregrated with Home Assistant.
Controllers and zones can specify an entity such as a switch or light, basically anything that turns on or off the system can control it. This is the irrigation valve. If this does not go far enough for your purposes then track the state of the binary sensors in an automation and do your own thing like run a script or scene.
This component will set up the following platforms.
Platform Description binary_sensor Show a valve on or off.
A binary sensor is associated with each controller and zone. Controller or master sensors are named binary_sensor.irrigation_unlimited_cN_m and zone sensors binary_sensor.irrigation_unlimited_cN_zN . These sensors show the state of the master or child zones. Attributes show additional information like current schedule and next run time and duration.
HACS is the recommended method for installation. If you are having difficulties then please see the troubleshooting guide.
Install from HACS.
Just search for Irrigation Unlimited integration in HACS and install it. Add Irrigation Unlimited to your configuration.yaml file. See configuration examples below. Restart Home Assistant.
Using the tool of choice open the directory (folder) for your HA configuration (where you find configuration.yaml ). If you do not have a custom_components directory (folder) there, you need to create it. In the custom_components directory (folder) create a new folder called irrigation_unlimited . Download all the files from the custom_components/irrigation_unlimited/ directory (folder) in this repository. Place the files you downloaded in the new directory (folder) you created. Restart Home Assistant In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Irrigation"
Using your HA configuration directory (folder) as a starting point you should now also have this:
Configuration is done by yaml. Note: The configuration can be reloaded without restarting HA. See below for details and binary options limitations.
The time type is a string in the format HH:MM or H:MM:SS. Time type must be a positive value. Seconds can be specified but they will be rounded down to the system granularity. The default granularity is whole minutes (60 seconds). This is the heart beat or system pulse. All times will be syncronised to these boundaries.
Name Type Default Description controllers list Controller Objects Controller details (Must have at least one) granularity number 60 System time boundaries in seconds refresh_interval number 30 Refresh interval in seconds. When a controller or zone is on this value will govern how often the count down timers will update. Decrease this number for a more repsonsive display. Increase this number to conserve resources. history_span number 7 Number of days of history data to fetch history_refresh number 120 History refresh interval in seconds testing object Testing Object Used for testing setup.
This is the controller or master object and manages a collection of zones. There must be at least one controller in the system. The controller state reflects the state of its zones. The controller will be on if any of its zones are on and off when all zones are off.
Name Type Default Description zones list Zone Objects Zone details (Must have at least one) sequences list Sequence Objects Sequence details name string Controller N Friendly name for the controller enabled bool true Enable/disable the controller preamble time '00:00' The time master turns on before any zone turns on. This is in effect a delay-start timer, controller will turn on before the zones postamble time '00:00' The time master remains on after all zones are off. This is in effect a run-on timer, controller will turn off after the specified delay entity_id string Entity ID ( switch.my_master_valve1 ). Takes a csv list for multiple id's all_zones_config object All Zones Object Shorthand default for all zones.
All Zone Objects.
This object is useful when the same settings are required for each zone. It is simply a shorthand or a more concise way to specify the same settings for each zone. The parameter becomes a default which can be overridden in the actual zone.
Name Type Default Description minimum time The minimum run time maximum time The maximum run time future_span time Run queue look ahead show object See Zone Show Object.
The zone object manages a collection of schedules. There must be at least one zone for each controller.
Name Type Default Description schedules list Schedule Objects Schedule details (Must have at least one) zone_id string N Zone reference. Used for sequencing. name string Zone N Friendly name for the zone enabled bool true Enable/disable the zone minimum time '00:01' The minimum run time maximum time The maximum run time future_span number 3 Number of days to look ahead entity_id string Entity ID ( switch.my_zone_valve1 ). Takes a csv list for multiple id's show object See Zone Show Object.
Zone Show Object.
These are various options to reveal attributes on the zone entity (only one for now).
Name Type Default Description timeline bool false Show the zone timeline. This will expose an attribute called timeline on the zone entity.
Schedules are future events, not dates for example Mondays. There must be at least one schedule for each zone.
The schedule can have the commencement or completion fixed to a time or event with the anchor parameter. Any adjustments to the duration will alter the start time if finish is specified or the completion time if start is specified. Note: If anchoring to finish and the schedule can not complete before the specified time then the run will defer to the following day. This is an important consideration if adjusting run times dynamically as it may lead to a 'skipping' situation. Ensure there is sufficient time to complete the run when making adjustments. See here for more information on adjusting runs times.
The parameters weekday , day and month are date filters. If not specified then all dates qualify.
Name Type Default Description time time/ Sun Event Required The start time. Either a time (07:30) or sun event anchor string start start or finish . Sets the schedule to commence or complete at the specified time duration time The length of time to run. Required for zones and optional for sequences name string Schedule N Friendly name for the schedule weekday list The days of week to run [mon, tue. sun] day list Days of month to run [1, 2. 31]/odd/even month list Months of year to run [jan, feb. dec]
Leave the time value in the Schedule Objects blank and add the following object. An optional before or after time can be specified.
Name Type Default Description sun string Required sunrise or sunset before time '00:00' Time before the event after time '00:00' Time after the event.
Sequences allow zones to run one at a time in a particular order with a delay in between. This is a type of watering 'playlist'. If a delay is specified and a pump or master valve is operated by the controller then consider the postamble setting in the Controller Object . Set this to the largest delay to prevent pump on/off operations.
Sequences directly descend from a controller and are loosely connected to a zone entity via the zone_id parameter. The zone_id may point to one or many (a list) zone entities. A zone may be referenced more than once in a sequence.
Name Type Default Description schedules list Schedule Objects Schedule details (Must have at least one). Note: duration if specified is the total run time for the sequence, see below for more details zones list Sequence Zone Objects Zone details (Must have at least one) delay time Delay between zones. This value is a default for all Sequence Zone Objects duration time The length of time to run each zone. This value is a default for all Sequence Zone Objects repeat number 1 Number of times to repeat the sequence name string Run N Friendly name for the sequence enabled bool true Enable/disable the sequence.
Sequence Zone Objects.
The sequence zone is a reference to the actual zone defined in the Zone Objects . Ensure the zone_id 's match between this object and the zone object. The zone may appear more than once in the case of a split run.
Name Type Default Description zone_id string/list Required Zone reference. This must match the zone_id in the Zone Objects delay time Delay between zones. This value will override the delay setting in the Sequence Objects duration time The length of time to run. This value will override the duration setting in the Sequence Objects repeat number 1 Number of times to repeat this zone enabled bool true Enable/disable the sequence zone.
Special note for schedules and the duration parameter contained within when used with sequences. Each zone in the sequence will be proportionaly adjusted to fit the specified duration. For example, if 3 zones were to each run for 10, 20 and 30 minutes respectively (total 1 hour) and the schedule.duration parameter specified 30 minutes then each zone would be adjusted to 5, 10 and 15 minutes. Likewise if schedule.duration specified 1.5 hours then the zones would be 15, 30 and 45 minutes. Some variation may occur due to rounding of the times to the system boundaries (granularity). This parameter influences the durations specified in the sequence and sequence zone objects.
The testing object is useful for running through a predetermined regime. Note: the speed value does not alter the system clock in any way. It is accomplished by an internal 'virtual clock'.
Name Type Default Description enabled bool true Enable/disable testing speed number 1.0 Test speed. A value less than 1 will slow down the system. Values above 1 will speed up tests. A value of 2 will double the speed, 60 will turn minutes to seconds and 3600 will turn hours to seconds. Upper limit will depend on individual systems. show_log bool true Outputs controller and zones to the log output_events bool false Prints event information to the console. Useful for creating the Test Result Objects auto_play bool true Automatically start tests times list Test Time Objects Test run times.
Test Time Objects.
This is the test time object. Test times do not alter the system clock so there is no danger of disruption to the Home Assistant system.
Name Type Default Description name string Test N Friendly name for the test start datetime The virtual start time (YYYY-mm-dd HH:MM) end datetime The virtual end time (YYYY-mm-dd HH:MM) results list Test Result Objects Expected timing results.
Test Result Objects.
These are the expected results from the test object. Every time a controller or zone turns on or off it is compared to the next item in this list. To aid in generating this list from scratch set output_event to true in the Testing Object . Events will be printed to the console which can be copied to this object.
Name Type Default Description t time required The time of the event c int required The controller number z int required The zone number. Zone 0 is the master s int required 0 = Off and 1 = On.
For a more concise style, results can be on one line for example:
Sun event example.
Simple water saving / eco mode example.
Every hour on the hour.
This is similar to the above but using sequences in a 3 zone system. Each zone runs for 12 minutes for a total of 36 min (plus delays). In Summer the total duration is extended to 45 minutes and winter reduced to 30 minutes. When using the duration parameter in the Schedule it relates to the total duration of the sequence, each zone is adjusted accordingly.
Just in case this does not go far enough then create three sequences with one schedule each. This will allow complete control over all aspects of the sequence including which zones to run, order, durations, delays, repeats etc. Still want more then create a sequence for each month of the year. This example reverses the order in Spring/Autumn for no good reason and excludes a zone in Winter.
Finish at sunrise.
For a more comprehensive example refer to here.
Schedules can not only have a day of week (mon, wed, fri) but also a month of year (jan, feb, mar). This allows the setup of seasonal watering schedules. For example run every day in summer and twice a week in winter. Setup a different schedule for each month of the year using this filter.
Use sequences to setup a water saving or eco mode. Eco mode uses small cycles with a delay to allow the water to soak in and minimise run off. Run all the zones for half the time and then repeat.
No need to restart HA after changing the configuration.yaml file. Go to Configuration -> Server Controls -> YAML configuration and reloading and press 'RELOAD IRRIGATION UNLIMITED'.
After setting up configuration.yaml, the operation can be controlled via service calls as shown below . Perform manual runs, adjust watering times, cancel running schedules and enable/disable zones from a frontend.
The binary sensor associated with each controller and zone provide several services. The sensors offer the following services:
enable disable toggle cancel manual_run adjust_time.
If a controller sensor is targetted then it will effect all its children zones.
Services enable , disable and toggle.
Enables/disables/toggles the controller, zone, sequence or sequence zone respectively.
Service data attribute Optional Description entity_id no Controller or zone to enable/disable/toggle. sequence_id yes Sequence to enable/disable/toggle (1, 2..N). Within a controller, sequences are numbered by their position starting at 1. Only relevant when entity_id is a controller/master. zones yes Zones to enable/disable/toggle (1, 2..N). Within a sequence, zones are numbered by their position starting a 1. A value of 0 means all zones.
Cancels the current running schedule.
Service data attribute Optional Description entity_id no Controller or zone to cancel.
Turn on the controller or zone for a period of time. When a sequence is specified each zone's duration will be auto adjusted as a proportion of the original sequence. Zone times are calculated and rounded to the nearest time boundary. This means the total run time may vary from the specified time.
Service data attribute Optional Description entity_id no Controller or zone to run. time no Total time to run. sequence_id yes Sequence to run (1, 2..N). Within a controller, sequences are numbered by their position starting at 1. Only relevant when entity_id is a controller/master. Each zone duration will be adjusted to fit the allocated time.
Adjust the run times. Calling this service will override any previous adjustment i.e. it will not make adjustments on adjustments. For example, if the scheduled duration is 30 minutes calling percent: 150 will make it 45 minutes then calling percent 200 will make it 60 minutes. Must have one and only one of actual , percentage , increase , descrease or reset . When a sequence is specified each zone's duration will be auto adjusted as a proportion of the original sequence.
A schedule anchored to a start time will alter the completion time. Likewise a schedule anchored to a finish time will change the commencement time. In this situation ensure there is enough time in the current day for the schedule to complete or it will be deferred to the following day. Adjustments must be made before the scheduled start time. Running schedules will be not affected.
Use forecast and observation data collected by weather integrations in automations to adjust the run times. See below for more information.
Service data attribute Optional Description entity_id no Controller or zone to run. actual yes Specify a new time time. This will replace the existing duration. A time value is required '00:30'. percentage yes Adjust time by a percentage. A positive float value. Values less than 1 will decrease the run time while values greater than 1 will increase the run time. increase yes Increase the run time by the specified time. A value of '00:10' will increase the duration by 10 minutes. Value will be capped by the maximum setting. decrease yes Decrease the run time by the specified time. A value of '00:05' will decrease the run time by 5 minutes. Value will be limited by the minimum setting. reset yes Reset adjustment back to the original schedule time (Does not effect minimum or maximum settings). minimum yes Set the minimum run time. maximum yes Set the maximum run time. Note: The default is no limit. sequence_id yes Sequence to adjust (1, 2..N). Within a controller, sequences are numbered by their position starting at 1. Only relevant when entity_id is a controller/master. Each zone duration will be adjusted to fit the allocated time. zones yes Zones to adjust (1, 2..N). Within a sequence, zones are numbered by their position starting a 1. A value of 0 means all zones.
Reload the YAML configuration file. Do not add or delete controllers or zones, they will not work because of the associated entities which are created on startup. This may be addressed in a future release, however, suggested work around is to set enabled to false to effectively disable/delete. All other settings can be changed including schedules. You will find the control in Configuration -> Server Controls -> YAML configuration reloading. Note: since version 2021.10.0 all settings can be changed including new controllers and zones.
Service call access roadmap.
A reminder that sequences directly descend from a controller. Therefore service calls that manipulate a sequence should address the parent controller. An entity_id of a zone when trying to adjust a sequence will most likely not have the desired effect.
The combination of three key parameters entity_id , sequence_id and zones will target the various sections of the configuration.
entity_id: This will be either the controller or zone entity. sequence_id: This is the position number of the sequence under the controller. sequence_id: 1 is the first, 2 is the second and so on. zones: This is the position number of the zone reference under the sequence. zones: 1 is the first, 2 is the second and so on. As a shortcut, zones: 0 will alter all zone references in the sequence. May also take a list zones: [1,3,5]
The following is a valid irrigation unlimited configuration. It shows how various points can be changed using the service calls above. Example numbers have the nomenclature C.Z.S.R = Controller.Zone.Sequence.zoneReference. If Z is zero then the entity_id must be the controller/master i.e. binary_sensor.irrigation_unlimited_cN_m. If Z is not zero then then entity_id is the zone i.e. binary_sensor.irrigation_unlimited_cN_zN.
The adjust_time service call examples show the adjustment method of actual . This is shown for simplisity however all methods are available as described above . The enable service call can also be disable or toggle .
Because this is an integration there is no integrated frontend so there is a clean separation between the irrigation engine and the display. It allows for a great deal of flexibility in the final appearance. For an out-of-the-box vanilla solution, simply put the master and zone binary sensors onto an entity card to see what is going on.
This card uses markdown which is included in Home Assistant as standard. Create a new card and paste this into it. See here for more information about markdown.
Markdown does a great job but it does have some limitations in particular colour which it does not support. This next card uses Lovelace HTML Jinja2 Template card (it's available via HACS). Create a new card and paste this into it. Now you can unleash the power of HTML including colour, go ahead and have a tinker, I know you want to.
The above two cards read data from the irrigation_unlimited.coordinator entity. The configuration attribute of this entity is a JSON formatted string and can be used in all Home Assistant templates. There is more information in the JSON dataset if you want to go looking. Most fields have sensible labels and easy enough to figure out. Now the wheels must be turning.
Most of the following will require installation of further lovelace cards. For some inspiration and a compact card try this.
and it expands to:
Note: This card uses some custom cards multiple-entity-row, fold-entity-row, logbook-card and at the moment card-mod for styles.
For watering history information here is a sample card.
Note: At time of writing this requires a pre-released version of mini-graph-card. Note: If you get "NaN" displayed instead of the actual value then clear out your browsers cache and make sure the development release is installed.
Although not really part of the integration but to get you started quickly here is a temperature card.
And a rainfall card. Note how the watering times reduced as rainfall started. More on this below in Automation.
Finally, a system event log.
Putting it all together, here is the complete picture.
This configuration is three vertical stacks and works well on mobile devices.
Minimum version 2021.12.0 of Irrigation Unlimited is required for this feature. First up, enable the timeline in the zone show object.
Like the watering history card above it also shows the upcoming schedule for a complete overview of your irrigation. Find the code here. Requires apexcharts-card.
If you prefer something akin to a airport departure board then try this. Uses Markdown card which is built into Home Assistant so will work straight out of the box.
The manual_run and enable/disable cards require additional support files. Minimun version 2021.6.3 of Irrigation Unlimited is required. There is a support file packages/irrigation_unlimited_controls.yaml which should go in the config/packages directory. Also required is a pyscript which is called from the above automation to populate the input_select with all the irrigation unlimited controllers and zones. The script should go in the config/pyscript directory . If you don't have a packages and a pyscript folder then create them and add the following to your configuration.yaml.
Using your HA configuration directory (folder) as a starting point you should now also have this:
More information on packages can be found here and pyscript can be found here, don't worry about the Jupyter kernel unless you are really keen. Hint: A pyscript is used instead of Jinja2 as it produces a list which Jinja2 is not capable of, Binary Options many have tried. The pyscript is a small piece of code that convert for example ‘1.1 Zone1’ inside an input_select control into ‘binary_sensor.irrigation_unlimited_c1_z1’ and then call the actual service. They are just helpers sitting between the lovelace card and the integration. It's a great way to add some additional capabilities to lovelace cards.
Manual run card.
Here is a card for manual runs, see requirements above. You can find the code here. Note: This card uses paper-buttons-row and time-picker-card.
This card will enable or disable a zone from a dropdown list, see requirements above. The code is here. Like the manual run card it requires paper-buttons-row.
Due to the many weather integrations available and their relevance to your situation, there is realistically no way to provide a built in 'auto-adjustment' feature. Therefore, no attempt has been made to include a solution and this also makes the integration more independant and flexible. Run time adjustment is achieved by setting up sensor(s) that consume weather information such as rainfall and temperature but could factor in wind speed, solar radiation etc. to determine if more or less watering time is required. You might also consider using forecast information. A service call is then made to irrigation unlimited to adjust the run times. This does mean some knowledge of creating automations is required.
On a personal note, I use the national weather service BOM for my forecast information but find their observation data not relevant due to the extreme regional variations in my situation. There are many micro climates (mountains) and a few kilometers in any direction makes a lot of difference, down pour to a few drops. To this end I have a Personal Weather Station (PWS) that feeds Weather Underground where I use the WUnderground integration to retrieve the data.
You will find my adjustment automation here which feeds off the temperature and rainfall observation data. There is a card here which displays this information (uses multiple-entity-row). Some ideas were gleaned from kloggy's work.
This example uses the data from a soil moisture probe created in ESPHome to adjust the run times.
HAsmartirrigation calculates the time to run your irrigation system to compensate for moisture lost by evaporation / evapotranspiration. The following automation runs at 23:30 and takes the calculated run time from HAsmartirrigation and updates Irrigation Unlimited with the new watering time. It then calls HAsmartirrigation to reset the bucket when the irrigation has run.
The example below offers two methods for a single zone or a sequence.
This section shows how to send a notification when a sequence starts or finishes. Messages can be sent for example via email (SMTP), push notification to mobile phones, twitter and many others. See here for more information on notifications in Home Assistant. Note that it is not limited to sending notifications but many other actions are available.
Irrigation Unlimited fires events that can be captured in an automation using the event platform as a trigger.
These events are fired when a sequence starts and finishes. The trigger.event.data contains additional information that can be used in automation scripts. Here is the list of additional fields.
Field Description controller.index The sequential index of the controller. controller.name The friendly name of the controller. sequence.index The sequential index of the sequence. sequence.name The friendly name of the sequence. schedule.index The sequential index of the schedule. Note: This maybe blank/empty(None) if it was a manual run - useful as a test. schedule.name The friendly name of the schedule. run.duration The run time of the sequence.
This example displays a persistent notification on the front end when a sequence completes. Note the use of templating to construct a specific message. Although not used here, this platform also supports markdown.
Here is the notification displayed in the Home Assistant web interface.
There is quite a lot of information on using notifications in Home Assistant on the web. Try Google, YouTube etc. for some great information and tips.
There should be little trouble installing this component, please use the HACS method where possible. Binary sensors are created automatically. However, if you experience difficulties please check the following:
This integration depends on two other components; recorder and history . Both of these components are part of the standard Home Assistant installation and enabled by default with the default_config: line in the configuration. If you have removed this line then a history: and recorder: section must be setup manually. If a mistake is made in either one of these configurations then they will not start and in turn, Irrigation Unlimited for which it depends on, will not start. Please check the log file for the following lines:
The above shows the requirements were loaded successfully. Note: The lines may not be consecutive in the log. If you do not see these lines then go back to basics and remove any history: and recorder: sections and ensure the default_config: line is present. Restart HA and check you have these log entries.
There must be a irrigation_unlimited: section in the configuration. If the section is missing or invalid then Irrigation Unlimited will not start. Check the log file to see it successfully started up.
The above shows that Irrigation Unlimited loaded successfully. Note: The lines will most likely not be together so do a search. If it failed then use the minimal configuration shown here . This is a good starting point to get aquainted with this integration.
For more detailed information set your logging for the component to debug:
Last but not least.
If all else fails please open an issue.
All feature requests, issues and questions are welcome.
Contributions are welcome.
If you want to contribute to this please read the Contribution guidelines.
Code template was mainly taken from @Ludeeus's integration_blueprint template.