Jump to content

Waiting For Next Irigation Cycle Is Shorted


scotnor

Recommended Posts

Hello Everyone,

I have been using what I remember is version 2 of the irrigation program found in the wiki. I have modified it according to my current setup. I do not have the evapotranspiration module, so I don't use version 3. Last year, I noticed that it did not appear to be waiting the correct amount of time if no rain had fallen. I have just noticed this happening again. Upon further investigation, I have noticed that the wait appears to only be waiting half of the programmed time, i.e. 18 hours instead of the 36 hours that is in the program. There has not been any rain to reset the program chain. The program summary clearly indicates starting the wait program Friday at 11:30 pm and ending at Sunday 11:30 am. There are no entries in the log regarding a finished program at 11:30 am. My understanding of the program flow is that the wait for 36 hours program actually should never be stopped. So, my questions are, am I reading the program correctly, and if so, have a found a bug?

Regards,

Scott

Link to comment

The program that I am focusing on is the Weather Rain Delay 36 Hours program. It has no conditions and is enabled. It sets a variable Weather_Rained_Last_36_Hours to 1, then Waits 36 hours, then sets that variable to 0. The variable is an int variable. The Auto Scheduled Timer programs check if that variable is 0 only when the time condition is satisfied. The Weather Rain Delay 36 Hours program is briefly stopped if rain data provided by the weatherbug module is not zero, but I have modified this to be greater than 0.5. After being stopped, the program is restarted. Also, the Weather Rain Delay 36 Hours program is restarted by the Auto Scheduled Timer programs, which are both enabled. Weather Rain Delay 36 Hours is also set to run at startup. I found 3 versions of programs in the wiki. V1 is the brute force version, v2 uses variables and v3 uses the evapotranspiration module, which I don't have.

 

Sent from my zt180 using Tapatalk 2

Link to comment

Hello scontor,

 

Thanks for the detailed description. The best way to debug this is to have notifications sent before and after the wait. In the notification, use custom content to list out the status of the variables and program statuses. This way, we will know what contributes to this behavior.

 

With kind regards,

Michel

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...