that’s the whole point of the integration - we can calculate / estimate it from the info you provide. Just enable pyeto module and off you go. I don’t know of any weather station that has an ET sensor. You don’t need it.
while using Pyeto is great, Davis Vantage VP2 with solar sensor does provide ET directly. Quite pricey though
i don’t understand. then why do you ask it as an input in sensor configuration 
Running currently 0.81 with ET and rain values delivered directly by weather station. I noticed in the system log file this message. HA : 2024.07.01
log
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:151
First occurred: 09:55:12 (17 occurrences)
Last logged: 09:55:26
Detected code that calls async_forward_entry_setup for integration, smart_irrigation with title: Smart Irrigation id7 and entry_id: d966bf08efd8de2c5ddebe6ef66907d6, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead. Please report this issue.
Detected code that calls async_forward_entry_setup for integration ipx800v4 with title: IPX800v4_jardin and entry_id: 2f6a2f23a13617fb47c2a71bd26d8ff1, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Detected code that calls async_forward_entry_setup for integration ipx800v4 with title: IPX800 and entry_id: 6a8c8b5c1841842bc777b376e5147d9b, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Detected code that calls async_forward_entry_setup for integration ecodevices with title: Eco-Devices 192.168.21.231:80 and entry_id: 936b7466dc89afd4398a9e1ba2001d78, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
In order to prepare the transition to the last version, it is run on a test machine. So I set-up a Passthrough module. To my understanding this module needs only two sensors to be declared, which I did. I’m wondering why other sensors are listed in this panel. Wouldn’t be nice to list only the required sensors?
Does this integration account for moisture lost to drainage?
Evaporation is the least of my worries as I have quite sandy soil with a good mulch cover.
I do not think so. The grafic also states that it does not.
1 Like
I noticed that in one of the recent releases, use of “Pirateweather” is now possible instead of OWM. I set up my SmartIrrigation using OWM. How can I change it so that it uses Pirateweather (which is what I use for default weather in HA anyways) without changing any of the zone names/information?
It’s an option for those that happen to have an ET sensor. 99.5% don’t. You don’t have to fill it in, in fact it’s set to none by default. Just because an option is there doesn’t mean you have to use it right?
Because you can use the same sensor group with many other modules and we don’t know which combination of zone, sensor group and module you’re going to make.
No it doesn’t. You’d have to take that into account yourself.
1 Like
Edit the configuration in the integration screen, not in the panel.
That is correct.
Thanks. I did this. However, that recreates a separate sensor entity for each zone. Is there a way to clean this up?
this is by design - you get one sensor per zone.
Hello, I really like the idea of this integration because evapotranspiration is exactly what I’m not able to manage with my own script. So it really fit my need and seem really well done.
Unfortunately I can’t get it working. I spent the last weeks trying to get it functional. I read the doc many times and started config from scratch many times, but no success.
The irrigation sensor appear but stay to zero
Finally instead of uninstalling it I write this message, and I hope with your help I’ll make it work 
I have a drip watering system connected on a zigbee valve and I just need to calcultate once per day the time to open the valve.
I have a weather station in the garden collecting many parameters but not evapotranspiration, so I expect it to be calculated by smart irrigation.
The weather forecast is pretty reliable on 48h.
My config:
General:
Weather data automatic : yes
Update sensorrs every : 1 hour
delay : 0
Automatic time calculation per zone : Yes
at: 17:55
Automatic suppression of weather data: Yes
at 23:59
Continuous updates for sensors (experimental) : No
ZONES (only one)
As it’s a drip irrigation system on the feet of the plants I don’t have a big area but I estimeted it to 15m² and I added a multiplier x10
I’m not sure about the bucket settings. Is it automatic? should I fill it?
MODULES
SENSOR GROUPS (only one):
Dew point: something strange happened here many times. When I load the page instead of the full name of the sensor, there is just “senso”. I write the full name of the sensor, it seem ok. When I come back the next day there is only “senso”.
Evapotranspiration: NONE because I don’t have a sensor, I guess it will be calcultated.
Here is my full settings:
Thanks a lot for any help you can provide
Sorry, I should have been more clear. I understand I will have one sensor per zone. What happened was that when I added the API for pirateweather, I have 16 sensors instead of 8 (I have 8 zones). I tried to manually change the entity names so that I am using the "new"ly created sensors for my automations, however it’s not working as intended.
Remove and readd the integration. Settings will be preserved, at least this happened to me when removing and readding
Yes that is the one I’m using, it has a ET sensor.
Please open a github issue so we can collect the info required. It looks like the name of your pressure sensor is weird and that’s likely causing an issue. Please post logs and config, preferably on github so I can track the work.
I set this up today but as of right now I’m reporting 0 value for the sensor even after manually forcing a calculation. Maybe that’s OK - but I want to keep an eye on it.
It might help to expose some other sensors of behind the scenes calculations to give us some confidence that things are working correctly. Like, maybe there are some sub-components to the calculation that are typically non-zero that you can expose.
Of course, these are our gardens and we make big investments time+money into making sure they’re healthy, so we need some assurance calculations work even if no watering is required.