-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resume bucket value if forecast rainfall is not met #423
Comments
how would this work? a forecast is a forecast, so at the time of calculation the only thing we can do is take into account tomorrow's (or the days after's) forecast(s) and adjust tomorrow mornings irrigation accordingly. I fail to see how we would achieve what you describe. As an example: Makes sense? Feel free to provide other options. |
I see your point about the rain possibly falling later in the day. I'm not a coder by any means, but what I was envisioning to make this as accurate as possible, is a placeholder for the anticipated rain impact. For example, if the forecast anticipates .5" rain and the ET calculation takes that into account, place that amount in a placeholder. At the end Sunday in your example, you would "true up" and add anything left in that placeholder. If no rain was detected, all of it would be added back. .25", would mean half of the placeholder would be added back. |
but ET is not equal to rainfall ,so this is not going to work, unless I am missing something. |
What is the current logic? If we get rain forecast, are you just using the amount of rain to calculate the new bucket value? I think it would make more sense to never use forecast value but rather setting a flag to be used in our outomation if there is rain forecast in the next 24hrs. |
That is essentially the concept that I was trying to articulate as well. Sent from my iPhoneOn Jul 23, 2024, at 1:14 PM, acarlo79 ***@***.***> wrote:
What is the current logic? If we get rain forecast, are you just using the amount of rain to calculate the new bucket value? I think it would make more sense to never use forecast value but rather setting a flag to be used in our outomation if there is rain forecast in the next 24hrs.
In this way, your bucket calculation will be always accurate and you avoid to water if there is rain....if the rain won't arrive, the new bucket will be calculated correctly again and you will water again the following day.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
correct, the amount of forecasted rain is taken into account to calculate the new bucket value. |
I would maybe change this part since forecast is just a "guess" and could lead to a wrong bucket beeing calculated. I would just expose a value to tell (rain is forecasted in the next 24hrs) so you could skip tomorrow watering and then calculate the new bucket correctly (with or without the rain fall of that day). I think would be possible already now if you take a forecast rain sensor and set the forecast days to 0. |
I've had a few instances recently where rain was forecast and the integration appropriately took that into account, however the rain never came and it should have watered. It would be great if the integration compared the anticipated, forecasted rainfall vs what my rain gauge actually reads and adjust accordingly. It seems as if once the forecast rainfall is calculated, it's never undone or modified that amount is not met.
The text was updated successfully, but these errors were encountered: