June 15, 2018 at 11:08 pm #50708
I just recently installed OpenSprinkler pi at my house and I have noticed that the weather adjustment changes drastically throughout the day.
Early in the morning when I am actually watering and it is still cold I seem to get decreased watering times (this morning I was at 81%). Then in the heat of the day OpenSprinkler shows much higher watering times like 180%. It is definitely hot and dry enough that my watering should be increasing.
If the Zimmerman algorithm were actually using the average temperature from the previous day I wouldn’t be seeing large swings like this. I am wondering if it is somehow using the current temperature instead of the average? Is there any way to get this working properly so that I don’t have to manually adjust my watering times?July 5, 2018 at 11:18 am #50955
We will check: due to WUnderground discontinuing their service recently, we have switched to OpenWeatherMap and due to the API change we may be using the current temperature as opposed to average temperature yesterday (it’s possible that they don’t provide yesterday’s temperature unless if you go with a paid service).July 6, 2018 at 7:03 am #50969
I’m noticing the same thing. Big changes in water level. I have mine set to run at 4am and the sprinklers almost never run, or if they do it’s somewhere around 20%. I tried doing some troubleshooting and realized with OpenWeatherMap I needed the paid service to get historical data.July 9, 2018 at 3:05 pm #51049
Yes, same behaviour here after I switched to OpenWeatherMap: As temperatures go down at night, watering level drops dramatically.July 9, 2018 at 6:01 pm #51055
+1July 9, 2018 at 7:04 pm #51056
Have you looked into Dark Sky? Their api offers each user 1,000 free calls/day. Seems like it would work pretty similar to weather underground. Their forecasting is the best too, imho.
https://darksky.net/devJuly 10, 2018 at 5:54 am #51063
Hello Cody, yes looks very promising but how to change form WU to darksky API in OSPI ?July 11, 2018 at 10:44 pm #51086
Sorry Jemba, that was directed towards the developers. As the weather adjustment runs on the server, not the firmware, I don’t know if there’s a way to change it yourself.August 22, 2018 at 12:02 pm #52306
New to OpenSprinkler and just had my first somewhat successful weather adjustment with the Zimmerman option enabled. I have noticed the same thing. Last night before heading to bed, the water percentage on the home screen was at 111%. I thought, good, it’s hotter that usual lately so it’ll be nice that the watering times will increase automatically. But this morning it was down to 24% and my morning program only ran for a couple minutes, instead of the 20 minutes it was programmed for. Our high was around 90 with a low in the mid 50s. So it appeared that the adjustment was at the time the program ran, which based it off of the low temp.
To get around this, I would need to do one of the following:
– set the program to run in the evening so it adjusts based on the high temp of the day
– adjust the zimmerman option for a lower baseline temp
– adjust the program sprinkler times to something outrageous like 2 hours(if I wanted a 10-20 minute watering time).
Am I understanding that correctly?January 2, 2019 at 4:44 am #53627
Same here – It’s the height of summer here, and we just had a series of days over 30C and my OSPi watered for 27 seconds per station this morning – 3% – this didn’t happen with WU data.
Is there a fix for this?January 2, 2019 at 8:23 am #53629
Same here! To give an idea how time-of-day dependent opensprinker Zimmerman turned after switching to OWM, please see the attached data from the last days, oscillating between 0% and 138% in a few hours:
value acknowledged from timestamp 86 true parser.0 2018-12-31T12:21:29.356Z 66 true parser.0 2018-12-31T13:21:29.426Z 27 true parser.0 2018-12-31T15:21:29.555Z 23 true parser.0 2018-12-31T17:21:29.708Z 0 true parser.0 2018-12-31T18:21:29.764Z 6 true parser.0 2019-01-01T07:21:31.067Z 0 true parser.0 2019-01-01T08:21:31.196Z 97 true parser.0 2019-01-01T09:21:31.319Z 113 true parser.0 2019-01-01T10:21:31.424Z 125 true parser.0 2019-01-01T11:21:31.475Z 123 true parser.0 2019-01-01T12:21:31.552Z 75 true parser.0 2019-01-01T13:21:31.692Z 15 true parser.0 2019-01-01T15:21:31.916Z 11 true parser.0 2019-01-01T16:21:32.158Z 0 true parser.0 2019-01-01T18:21:32.468Z 77 true parser.0 2019-01-02T09:21:33.675Z 105 true parser.0 2019-01-02T10:21:33.803Z 133 true parser.0 2019-01-02T11:21:33.996Z 138 true parser.0 2019-01-02T12:21:34.086Z
I’ve several systems deployed here and definately need a fix soon.
- This reply was modified 2 weeks, 3 days ago by mcmuller.
You must be logged in to reply to this topic.