2024.10.01 is installed now. I’m waiting now for the next watering cycle. Today watering was skipped due to the rain yesterday.
Hi, I have recreated the issue you identified, testing the resolution now.
V2024.10.02 published as a Beta
I will update when I’m back home.
I have installed V2024.10.02 now. Watering is scheduled in 2 days after HA restart.
Today watering started as planned and now the next cycle is scheduled in 2 days.
I think the problem is solved now. Thank you.
1 Like
Hello.
Are show_last_ran and show_next_run to show/hide the data elements not working here?
Hi @noizecreator393,
The current version of the custom card does not support this feature you may be using the standalone installation.
The custom component implementation now installs the custom card automatically.
To remove the standalone card and revert to the auto installed version follow this process.
-
Delete the custom card and the HACS repository from your installation.
-
Ensure the hacsfiles/irrigation-card/… resource is removed, delete it if required
-
Upgrade/reinstall the latest version of the component.
-
Restart HA
-
Refresh the browser (you may need to clear the browser cache)
-
Add the card to your HA Dashboard
The card will be upgraded with each install of the component.
Beta release available
Release V2024.12.01b0
BREAKING CHANGE
- Depending on the complexity of the implementation some options may need to be transitioned to different entity types.
- Frequency selection options will need to be updated in the program configuration.
- The custom card will need to be edited.
This has been a significant redevelopment. All helper objects are now created automatically. All you need to configure now are the switches/valves and sensors.
Naming of entities is determined using the translation files. These have gaps so please volunteer to update or provide a new file. Contact me if you can help, it is not a complex process.
The custom card has been updated for this release, the move to entities rather than attributes on the program switch have allowed for a richer experience leveraging the icon translation capabilities.
It is now easier to get support information with the integration of Diagnostics
Frequency can now be determined as an offset of Sunrise or Sunset.
Add the option to pause and resume a running program.
Allow multiple zones to run concurrently in a program. If this setting is selected the zone transition is not available.
I’m sure this is a really dumb question - so sorry. I’m looking to rename the zones on the card only - ie would prefer not to rename the entities themselves. Is there an easy way to do it? Can’t figure it out.
Thanks in advance!
The card will present with the friendly name of the entity. So you will need to change the name of the switch or sensor. But this should not change the underlying entity naming.
Awesome, thanks for the quick reply.
Hi Peter,
Thanks again for the last update, working great !
I made a pull request with French translation updated according to your tutorial.
I’m no so used of this process of fork/commit/pull request etc…, so I’m not sure if you received it.
Just let me know 
Regards
David
I’m sure this has been asked, but couldn’t find it anywhere, wondering how to add the ‘enable irrigation’ toggle shown on the example on the github page?
I write this because I suspect that there are people that may find this irrigation method a little intimidating.
Due to many factors, my 1/3 acre needs 17 zones. 25 zone irrigation controllers are upwards of $800! I chose an RPi, 16 relay board (5x5 matrix) and wrote my own irrigation controller in c++. It worked, but the UI really sucked. I looked into using HA as my UI. I’m glad I didn’t find this discussion. What I did find was the Sustainable Irrigation Platform (SIP)
It’s everything I wanted in a UI. It’s out-of-program communication is through MQTT; a very basic jinja template. I converted my code to work as a node in the MySensors environment. I use HA as an intermediary which also allows me to display which zone is being watered. I only had two tough nuts to crack. The first was to have HA decode the jinja template (thanks for the help I got on this forum!) and figuring out how to send data in the MySensors environment.
I was up and running in a week. I’ve had some hardware problems (loose connector, stuck valves, failed relay, server went bonkers during a power outage), but the SIP-MQTT-HA-MQTT-MySensors has been rock solid. Dan (the developer of SIP) gave concise help, though little was needed because the documentation is sufficiently complete.
Don’t get me wrong, the work that went on here is incredible. I just think that one should consider matching the language to the task.
-OSD
Hi,
The show program option enables the field in the card.
However if there is a lag loading the switches that represent your solenoids that the irrigation program uses you will need to manually reload the config. There is an issue outstanding on this for me to figure a better way of monitoring/alerting this.
From the screen shot you don’t appear to have the latest. You should see settings next to the cog icon.
If you select the cog icon do more option appear?
x-post from another thread.
I am getting an irrigation system installed in the garden and obviously I want it smart and integrated with home assistant.
It is going to have 8 irrigation zones / solenoid valves. I have an Ecowitt rain sensor as well as multiple soil moisture sensors for different parts / zones of the garden.
The property is in Tuscany, where water in summer is extremely scarce. This is why I want the soil sensors (instead of just simple timers) to make sure I use just enought water, but not any more than that. Logic-wise this seems simple enought to me, but apparently this a rather unconventional approach and not something that controllers / software support out of the box?
The features I am looking for:
- Stop irrigation if rain is detected
- Skip irrigation if rain is forcast.
- Irrigate zone until a specific value of the respective soil sensor is reached
- Support a soil moisture sensor for a group of zones: Irrigate first zone until a certain moisture is reached, then repeat the same irrigation time for the other zones in that group. (this is for the lawn that is split in to multiple zones but only has one sensor)
- Adjust target soil moisture if a float sensor in the well is activated (basically a survival mode for periods of drought where I would irrigate just enough for plants not to die)
Is this something this Integration could achieve?
Hi Nicolas,
Here is some comments and references to the help file and another component that may assist you. Here is an overview of what various sensor models are available.
- Stop irrigation if rain is detected
- Yes the integration has a rain sensor feature, as long as you have it exposed as a binary sensor in HA it will plug directly into the system, Rain Sensor
- Skip irrigation if rain is forecast.
- The adjustment feature supports this Adjustment Sensor
- I use this in preference to the rain sensor as I can use historical rain and forecast rain to determine if watering should occur.
- Open Weather Map History support this capability, using historical and/or forecast data to adjust the watering time depending
- Irrigate zone until a specific value of the respective soil sensor is reached
- Not really supported but the option below could be an alternative.
- Support a soil moisture sensor for a group of zones: Irrigate first zone until a certain moisture is reached, then repeat the same irrigation time for the other zones in that group. (this is for the lawn that is split in to multiple zones but only has one sensor)
- This is not a feature that is supported
- However you could consider translating the current moisture level to a factor and apply using the adjustment capability, for example, use a template script to convert moisture level to a value between 0 (don’t water) and 1 (full watering) you can use the program start event to calculate when the program starts so it is not adjusted when the next zone commences
- Adjust target soil moisture if a float sensor in the well is activated (basically a survival mode for periods of drought where I would irrigate just enough for plants not to die)
- This is another model where you can use the adjustment sensor based on what ever attributes you have available to calculate the optimal factor to reduce watering, this can be different for each zone, for example, if the sensor is active limit watering to only 10% of the defined value