I installed OpenWeatherMapHistory but I donāt know how to use it. It has 60 entities after installation. Which ones should I use to create the precipitation sensor? Can you provide examples of Jinja templates?
Is there an option to use a forecasted chance of precipitation entity (as a percentage) to skip at a certain threshold? I donāt have a rain sensor but do have a weather integration that supplies %chance of precipitation. Right now I just manually override, but having a rain skip option based on a forecast would be awesome. Love the integration!
You do not need to create all the sensors, it is possible to define only the ones you need once you have settled on a use for them.
You can also create jinja templates within the application to build just one sensor that you need using multiple values, see the examples in the documentation linked above.
I updated to version 2025.08.01 and Iām disappointed. For example, the pump turns on before the zone is turned on, which unnecessarily increases the pressure in the system. Previously, it worked the other way around: first the zone turned on, then the pump. And the worst part is that you removed the system venting. In version 2025.07.03, it worked perfectly. After watering, the valve was held for a moment to let all the pressure release. Do you plan to restore the 2025.07.03 versionās functionality in future releases?
Hi, Iām sorry you are disappointed, venting is still there, it is now the default it will always turn the pump off 3 seconds after the zone completes. The zone and pump start simultaneously, but I can add an option for a delay to be added. In fact it probably makes sense to allow both values to be configured.
I think we misunderstood each other . If possible, a change is needed to turn off the zone 2-3 seconds after the pump is turned off, not before.
Now the valves close and the pump works for 2-3 seconds, increasing the pressure, but it should be the other way around.
Adding a one-second delay to the pump start after the zone is activated would also be a good solution, as in the previous version
I tested it on2025.08.02 and the problem is that I have two pumps. The first pump is for drip irrigation and is low-powered. The second pump is for lawn irrigation and is high-powered. The problem is that no matter which program I run, both pumps turn on at the same time. Everything is set to only operate in one zone. This wasnāt the case in previous versions.
Hi, Normally an f5 screen refresh will resolve the problem on the occasions it occurs for me. Over last few releases of HA the custom card has resulted in some issues for users that I cannot recreate (or possibly have the skill to resolve).
There is an option in the advanced settings that when set will generate the yaml required to recreate the custom card using the HA entities card as the base. Once turned on it will create a persistent notification, copy the code from there and create a manual card using this yaml. Not quite an exact replacement but very close to the custom card. Using this will be more stable as it is using the base HA features. But if you change the config donāt forget to update the card with the newly generated yaml.
Can I check, are both zones running in a single program?
If so, the solution will be to run these as two program. Given they have independent water sources I assume they can happily overlap or have a common start time. You can allow this in the advanced settings by deselecting this option.
Hi, This error probably indicates that the program has not fully loaded before the card is being processed by the Lovelace frontend.
I am adding delay logic to wait and try a few times before giving the error, I canāt guarantee it will resolve the problem as it is not something I can readily reproduce.
Hi Peter. Itās an amazing work ! Congratulations and thanks for Your work.
I installed the latest component card. Works perfecly fine. Have a problem with the card itself. It is showing Error āProgram: not v4 or newer irriation componentā.
Is there any version checking or cn You descibe what could be this problem about ? Comp ver 2025.08.07, card ver 2024.10.01.
Thanks in advance !
The card can be a bit hit and miss unfortunately, I have had a couple of people with this issue. Sometimes a simple F5 refresh of the browser helps, other times clearing the cache.
The final option is to enable the yaml generation option in the configuration. This will write the yaml code that creates an equivalent entities card to the notifications. Simply create a manual card and paste in the generated yaml.
. If possible, a change is needed to turn off the zone 2-3 seconds after the pump is turned off, not before. 
