It looks like there is actually something wrong with the rain delay (or I'm a moron).
I turned off the rain check driver at 7:46pm on 5-16.
But when the schedule checked at 4am on 5-17 it showed a rain delay.
Am I just missing something here?
I need all the log info for that error, please:
I didn't run any programs to turn on the valves but the latest update that you posted on 5/18 looks to have fixed the rain delay not updating in the time table. I can see the rain hold change from true/false in the timetable status header to match the status of the rain check driver.
My weeds are definitely getting greener and spreading since I started watering on a schedule. Thanks again for all of your work on this.
Had another go at implementing this tonight and here is a few things that came up.
-
I can't enter a 0. I would not want my sprinklers to come on in certain months in the event of a configuration issue.
-
When I click on the 100.0 for the value then the data entry field appears and then immediately disappears before I can enter anything.
-
After I create a name I can no longer rename it.
Feature Request
My current solution has overrun protection which is a nice safety net if something goes wrong. I could do the same thing with RM but in-app is cleaner.
P.S. I applied the most recent version from HPM before starting this task.
The minimum valve time is 20 seconds. Even if Zero were allowed, when the math is done, 20 seconds minimum is produced.
The "can't make a change bugs" are very odd and frustrating because I encountered them in the first weeks of writing the code back in January. I'll need to take some time and rewind to much earlier platform releases to be certain where to find the bug.
I understand the safety net logic. I have one myself for anything water related. Belt-and-suspenders. I think using RM for that is a wise idea.
I updated to the latest version and was looking around in the app and I noticed something. It seems with each update a "pointer" to the rain check driver gets added. Below is a screenshot showing multiple rain check drivers available but I only have 1 installed. I can fix this by deleting everything and starting over but was wondering if you know what's causing this. I've seen it before and starting over fixed it
I discovered it has nothing to do with the updates. The above has something to do with the rain check driver (or the sprinkler app). Each time the rain check driver is turned on/off another instance is created in the drop down in the sprinkler app. I recreated everything this morning and had clean zones. I turned the driver on/off a bunch of times and I have 18 instances of the rain check driver in the drop down.
Getting some wonderfully obscure bugs.. possibly a good sign 
Might mean the big majority of the code is working properly. 
I ran into this when using the NWS driver but, because I wasn't in control of the dry/wet cycle, I wasn't able to troubleshoot much. We are still very much in our dry season here in FL. Other than this oddball, everything else has been rock solid!
Thanks for the update. My zones didn't run this morning so I updated to the latest fix, wiped the offending zones and set them back up. Probably messed something up when I was testing to find the cause of the bug. We are supposed to finally get some rain next week so I'll let you know if I find anything else.
Thanks again @csteele
1 Like
Although app status has been in the project since the beginning, I only noticed that it wasn't working a couple days ago. I was preparing to add it, only to find it was there, but broken.
Now it's a lot less broken, perhaps even working correctly.
1 Like
Is group 1 (the global group) supposed to honor the rain delay? I couldn't find anything in the docs about whether it is supposed to.
I'm using the rain check driver and am finding that it doesn't honor the delay when activated.
Easily fixed by adding another group to the child but was curious if it was a feature or a bug.
No, it does not. It's common to all.
1 Like
Unfortunately, I am still running into the issue of the app not recognizing that the rain delay driver has been set to dry. Here are a couple screenshots that show the that the driver was "dry" and the app still thought there was a delay.
UPDATE: I should add that I have 2 separate rain check drivers. One for the drippers zone and one for the 3 sprinkler zones. Maybe that has something to do with it.
The final screenshot shows that rain delay as false. It shows the front yard as on because I am manually running that zone this morning.
