- This topic has 21 replies, 8 voices, and was last updated 8 years, 6 months ago by
.
-
Posts
-
I have completed the Hungarian translation including many fixes. They are all present on getlocalization.com site, however I wonder how and when can I test it in WEB/mobile.
Thank you for your contribution. These updates will be incorporated into the next version release.
Thanks again!
I just merged all of your changes into the main code base and am working on a few issues I believe you reported. Once I have all the known issues resolved, I will push an update out. I am hoping to have this update out within 1-2 weeks.
Thank you for your patience.
That’s great.
Meanwhile I am still adding minor changes, so if it does not need huge effort then please merge again before you release.
Absolutely, I always merge the localizations before pushing out an update. Thank you again for your contribution!
Next to “when”, I may have a question “what” is in the pipeline for the next release (releases)
Is there a list of features that are planned in the (near) future?thanks.
Right now it’s bug fixes and minor improvements. Do you have any suggestions for the next app version that you would like to see included?
Thanks!
My suggestion still remains.
Zimmerman method that takes the precip from the past week into account.
lets say I want to have 10l of water per week.
If it rained 4l in the last 7 days, watering % is about 1/7th of the remaining 60% irrigation.My current problem is that on day 1 it rains 10l, on day 2 no rain, but on day 3, the irrigation % will be 100% (if I only take rain into account)
I would like to see more impact of rain in the last couple of days.I know that I can create my own script, but I think this is something more users can benefit from.
There are also discussions with flow meters and logging to have exact the 10l per week and this is maybe the ultimate goal, but an easy solution between current and ultimate solution would be nice?
Rain – I’ve just experienced the same issue. We had a very good amount of rain day before yesterday. OS set 0% watering yesterday, back to normal watering today :(. It would have been good to be 0% watering today and maybe also tomorrow.
For now I’ve had to disable OS so it does not water.
Hi,
Today I recieved the update of Opensprinkler Android app. It looks very good. Some minor corrections are needed. I will do it later.
However it seems that the Hungarian translationa of log review page is missing (Timeline, table, Start, end, etc..)Wokke,
Regarding your issue of watering too soon after a rain, try the California Restriction setting. It has some problems (see my posts) but its intent is to inhibit watering for 48 hours after a rain.
This is not an ideal solution but it would help.
Bill
@sakos I just found the cause for this and will get a fix out for it soon. Thanks for pointing it out!
Hi Samer,
I did not open a new topic as it was originally related to the Hunagarian translation. I would like to ask two minor changes which would let better translation.
Some words are used on different places with slightly different meanings. Is it possible to use separate strings for the different places?– Word “Disable” is used in station properties window and on the left menu combined with “operation” word. The best solution would be to have complete “Disable operation” and “Enable operation” strings and use “Disable” standalone only.
– Word “Submit” is used on run-once page in the meaning as “run the program immediatelly” and on other configuration windows as “save changes”. Would be good to change the string to “run now” or something similar on the run once page.
I have the same issue here in south florida. We had .5 inches of rain on Tuesday, 1.77 inches on Wednesday, 0 on Thursday (plenty of irrigation for at least 5 days) and now on Friday morning my system is back to watering cycle of 105%. I had suggested two months ago that the algorithm take into account a 3-7 day rolling average of the rainfall and allow us to set it at something like 1″ =0%. While it might be debatable, some turf in this area requires only 1″ of irrigation per week.
Thanks.
I love this system, but now that summer rains are here and we get upwards of 2=3″ in a given day (sometimes everyday, but many times it will be so scattered that my station will not get any for one day, but I don’t need to water the next day after 4″ of rain the previous two days.
That depends on whether we can get 3-7 days of rainfall data from WUnderground. I am not entirely sure if the current API provides such historic data, probably not without a paid WUnderground API service.
Ray,
Thanks for the reply. I know when I click on a weather station on Wonderground map, it gives me the current stats. When you click on the station “id” that link takes you to a detail page with stats for months and months and broken down to daily including wind, temp, rain accum etc. Not sure this is accessible from any available API.
What I had in mind (excuse my ignorance as I am not a programmer) was once we set up the program and set the station parameters, we are getting “daily” rainfall from the API. Can the system “add and average” those individual days so that at the end of the first 7 days, we now have the full set of readings and one day drops off and the next “new” reading is added in and averaged. Granted, it will take 7 days to be fully accurate / implemented, but that is fine for most applications.
Thanks,
Dennis
Honestly insight3fl this could probably be accomplished simply by using a rolling average of the water level. If you have rain for 2 days with 0% totals and then followed it with a third day of 100, you would have a final average of 33%, meaning a result much closer to what you’d need.
It wouldn’t be perfect but would add very little code to the firmware, and would require 0 extra calls to WU. It’s very similar to what I did with my ET fork of the project which uses a water balance. It just uses whatever yesterday was averaged with today’s calculation. Essentially weighting new data based on recent history. It will water less until enough days have passed without rain.
Shawn,
Thanks for your input. Not sure how that would work. AS I mentioned in my original comment, I have my system set to go on every third day. So say that would be today (Monday), then the next cycle would be Thursday. I need to run twice a week for about 20 minutes per zone in absence of any rainfall within three days of at least 1″.
So I irrigate this morning (Monday) and then this afternoon it rains .5 inches today, 1.77 inches on Tuesday, 0″ rain on Wednesday (now plenty of water for at least the next 3 days or more) and on Thursday, my system is ready to water at 100% and goes on. This is exactly what happened last week. The system seems to only look at the day preceding the day to irrigate. I want it to look at several days (at least 3 but better 7).
@Shawn, you are totally right — given that OS firmware queries the weather script every hour, it can easily keep a history of the weather dat on its SD card. Samer and I have talked about it before, we just never had time to sit down and implement it. Your ET-based algorithm probably uses the same approach I assume.
Ray yes I use a rolling balance of precipitation, sprinkler and rain vs need. It’s not perfect but does work to prevent watering after a heavy rainfall. Since it pulls weather forecast information every hour and updates the running total accordingly, it even does well to prevent excess watering the day of or up to 3 days before a major rainfall event.
- You must be logged in to reply to this topic.