Irrigation Custom Component with Custom Card

petergridge · January 29, 2023, 9:21pm

The monitoring fits best where the frequency is set using the number of days model, lets use 3 days as an example. So if the controller is inactive and the program runs the last ran time would be updated and the system would wait another 3 days resulting in 6 days between watering events. If the program does not run, and the system is active again the program will run at the next runtime after the system is active, missing, hopefully, only one day of watering. This is to make it as robust as possible if you are away from home and not aware that the system was offline. I do have a to-do to monitor the individual switches that represent the zones in case they go offline, this will be a better implementation that does not need the additional sensor exposed.

The interlock is really a failsafe, in case someone (lets say the non techo person of the house) alters the start time of a program with the some unexpected result e.g. not enough pressure to water correctly, over watering… I agree it is typically not a problem, but it’s a feature now that can be controlled, prior to this it was a poorly documented default.

andrefvdm · January 31, 2023, 6:47pm

Hi, when installing from HACS (new install), i get “No matching entities found” to “Start time entity*” and others. Do I have to define the entities in configuration.yaml first ?

petergridge · January 31, 2023, 7:53pm

Hi @andrefvdm

You need to define the entities that allow you to control the features you want. I did tinker with creating these programmatically but it was not consistent with the way HA was travelling and I abandoned that path.

I have have moved away from defining the helpers in YMAL and create them via the Helpers tab in the Settings, Devices and services paged, I find it easier and there is no need to restart HA when you add new ones.

I would recommend you create.
For the program:

Input_datetime for the program start time (time only)
Input_boolean to support the toggling of the configuration in the custom card
Input_boolean to support the enabling/disabling of the program

For each Zone:

Input_number to provide the duration of the watering cycle
Input_select to define the frequency you want the zone to run, you can do this on the program if you want and save a few entities but I have different frequencies on some zones

This will get a basic setup running, have a read of the notes on GitHub and try a few of the other features.

andrefvdm · January 31, 2023, 7:55pm

excellent, I figured it out and got it working thanks ! now for the testing . Thanks a million so far !

petergridge · February 19, 2023, 5:16am

Check out the new support for Card Mod in V5.2.0 of the Irrigation Custom Card.

Card-Mod

Support for GitHub - thomasloven/lovelace-card-mod: 🔹 Add CSS styles to (almost) any lovelace card. Allows you to apply CSS styles to various elements of the Home Assistant frontend.

type: custom:irrigation-card-test
program: switch.test_irrigation
entities:
  - switch.dummy_2
show_program: false
card_mod:
  style: |
    ha-card {
      background-image: url('/local/lawn.png');
      --mdc-theme-primary: black;
      }

Arturo_Castano · February 21, 2023, 4:06pm

Hi guys.
I’m having some issues configuring the component.
I want to add more programs, and I can’t find how to do it. I can only set the program up with different zones, but I want different programs so I can be more specific with the time and days.
Any idea?
In the past, it seems that it was done by .yaml, but I can’t find the .yaml file either.
Any help would be much appreciated

petergridge · February 21, 2023, 7:34pm

Hi,

You can add more instances of the integration. From the ‘settings’/‘devices and services’ menu option click ‘add integration’ and search for ‘irrigation controller’ select the integration to add it and configure using the config flow process. Irrigation-V5/README.md at main · petergridge/Irrigation-V5 · GitHub

HA is generally moving away from YAML for the configuration, it has introduced the config flow model that provides for a UI based configuration, generally a better experience for users. The yaml is hidden away in the .storage hidden folder. But that is best left alone.

Cheers

cristidobrescu · March 31, 2023, 7:39pm

Hi, is there any way I get rid of run_freq tab of each zones I declare in config? I have to mention not any of zones has run_freq declared, I left it blank when I config them; beside this It keep showing up. I also tried to edit switch.py but no success

petergridge · April 1, 2023, 9:25am

Hi,

This is a bug, I will get onto it in the next week or so.

Cheers

cristidobrescu · April 1, 2023, 10:41am

thanks a lot

petergridge · April 3, 2023, 4:26am

Hi @cristidobrescu,

I have beta version 5.2.1 with the fix, please review that this fixes your issue and let me know.

In HACS ensure you have ‘Show beta versions’ checked when you select ‘Redownload’

Noticed you have an older version of the card, the new version is cleaner and has some additional features.

cristidobrescu · April 3, 2023, 8:28am

Hi @petergridge, thanks for the well done fix update, you’re the man; great work by the way. I just have one more question, as input_select freq interval, I set up in option like bellow:

options:

“1”
“2”
“3”
“[‘Mon’,‘Tue’,‘Wed’,‘Thu’,‘Fri’,‘Sat’,‘Sun’]”

“1”, “2” represent the days interval to start? because seems like is not working for me.
Only this option is working: * “[‘Mon’,‘Tue’,‘Wed’,‘Thu’,‘Fri’,‘Sat’,‘Sun’]”

petergridge · April 3, 2023, 9:22am

Hi, here is how I have the test input_select configured

I have done away with YAML as much as I can and use the helps.

cristidobrescu · April 3, 2023, 12:11pm

I have to admit, the input select was made in yaml, not using helpers opt; I will set another one using helpers. I will let u know about it.

Magno · April 3, 2023, 12:20pm

Hello Peter,

Amazing Work. @petergridge Is there any special trick to make the Inter Zone Delay Work? For me, it seems to do nothing. It simply stops one zone and goes to the next one. Even the total counter does not consider it.
In the example below I have a delay of 5min and 3 zones (each with 5min also).

For me this is relevant because I’m setting this up to take advantage of the photovoltaic quarter cycle counting system.

Many thanks in advance

cristidobrescu · April 3, 2023, 12:28pm

You were right, using yaml config is not a good idea to use; using helpers made the select to work as it should be

petergridge · April 4, 2023, 3:21am

Hi @Magno, the delay is measured in seconds not minutes, try 300 for the value. You are correct though, I do need revisit the program runtime to include the delay. The initial use case was for small delay so it was implemented in seconds. I also should update the documentation to reflect this

Magno · April 4, 2023, 10:09am

It has made the trick. Many thanks.

cristidobrescu · April 6, 2023, 8:04pm

Hi @petergridge is it posible the “last_ran” result to be added as an option for zone config? It may be displayed also on Program Data as an option. I would like to be not shown on card tfor each zone.
thanks

NOTE: The “Morning Program” never start, that`s why it has no “last_ran” result

loic69 · April 7, 2023, 9:23am

Hi all
Is this possible to add the next runtime info ?
Other question :
I’d like to link this integration with real mete information (last rain and next daily rain) to compute if I have to launch irrigation or not. Not a problem for that because I can use rain_sensor features.
Is it possible to have the rain_sensor for program ? I have a lawn programm with 4 zones and it’s more simple to use rain_sensor with the program it-self instead of create one entity rain_sensor by zones…

Other question.
If my frequency is set to 3 days.
so the D day, my rain_sensor decide to not turn of irrigation, what’s is the next runtime ? Tomorrow or in 3 days ?
My question is about this runtime calculation.If my lawn need water each 3 days and if’s raining a litle, probably that the lawn don’t need at D day irrigation but maybe tomorrow and not in 3 days.
What do you think about that ?

On my old jeedom domotique, I writed a script wich compute at each runtime start irrigation if there is a need of irrigation.

If Yes, OK , launch irrigation and then compute next runtime time with the frequency.
If No, no Irrigation, and report next runtime time to tomorrow.

As this in case of rain, irrigation starttime is compute each day with rain history sensor and daily rain forecast.