How can we help?


4.0.954 - Finish by sunrise - no watering

Comments

13 comments

  • Avatar
    Rick Felter

    Also looked at the console itself. The schedule for that program says start time is “60 mins after sunset”, which isn’t right and shows a next watering date of tomorrow. Going back to old schedule for now. We have a heat wave right now, can’t skip watering.

  • Avatar
    Nicholas

    Maybe the hour that was reschedule already passed ? Console means directly on LCD of the unit ?

  • Avatar
    Rick Felter

    I’ll have to wait a couple of days until the next event. Had rain last night and now a surplus for the next day or two. Yes, console meaning the LCD. Also notice the scheduling on the LCD doesn’t have the finish by option. It’s just the web interface.

  • Avatar
    Rick Felter

    This simply isn’t working on my device. It is calculating the start time correctly when viewing the web UI of the programs screen — but the sprinklers do not come on at that time. Two days now for both of my zones, I’ve had to go in and edit the start time to a fixed time, and then the sprinklers run as expected. I.e program start today was supposed to be 5:04 AM in order to finish by 15 mins after sunrise. As of 5:45, sprinklers did not come on. Changed to 5:56 AM fixed start time, and program runs. I opened up a ticket for this on the website and sent diagnostics as well as attached debug log.

  • Avatar
    Rick Felter

    This was related to the iOS app not having support for the new finish by setting. New beta now has it, and program ran properly this morning. Thanks.

  • Avatar
    Rick Felter

    Update... After several days of watering without issue at the scheduled time, today nothing ran. The program shows it was supposed to run 72% of its scheduled time, and it didn’t run. Additionally, the watering history for today simply says “No watering data”.

  • Avatar
    Rick Felter

    Also notice now in the log, the system is reporting that the program is going to start in a negative number of seconds:

     

    2018-08-28 12:26:00,278 - DEBUG - rmParserManager:506 - Program 11 will start in -31020 seconds(2018-08-28 03:49:00) deltaLastParsersRun: 8295 lastUpdate: 1535465265


    It should have ran at 3:49 AM this morning.. How do I resolve this?

  • Avatar
    Theodore (Edited )

    Hi Rick, 
    I have looked over the your logs and yes, most probably it is a bug, but it should not be related to or influencing your "not watering" problem. Its effect should only be that the simulator will run for a program that actually it's not scheduled for that day.
    Also, as far as I can see, you are/were experiencing some rain in those days and I think that watering needs were satisfied.
    Also, I suspect that the programs are running ok now. Let me know if this is not the case.

    Thanks,

    Theodore

  • Avatar
    Rick Felter (Edited )

    As far as the rain goes -- no, we have not had any rain since 8/22.  And no, the programs are only running OK now because after 2 days in a row of the programs failing to run at all, I changed the schedule back to "Start 120 minutes before sunrise".  When the feature (Finish by...) was first introduced in the beta, it didn't work at all.. But then the iOS app was updated to support that option as well, and I changed the schedule to "Finish by 10 minutes after sunrise".  And that was working for both of my programs for 7-10 days or so -- and then it just stopped working with no error messages at all, the watering history displaying "No watering data" on the day it was supposed to run.. After the day would end, the watering history would just have nothing at all for that day -- usually it would at least show the day, show the originally scheduled run time for each zone -- and if it didnt water, it would show 0:00 for each zone along with either "Water surplus" if there was a surplus, or "Rain detected by sensor" if the rain sensor was triggered. I've attached a full screenshot of my watering history.. You can see that on Tue 8/28, there is simply nothing there.  Wed 8/29, you can see I just ended up doing manual watering because it skipped that one as well.  You can see on days like 8/27, there were zones that didnt water due to a surplus.  And days like 8/22 where there was rain detected.

    Oh and one more thing -- on those watering history pages -- where it says on days like "Thu Aug 30 2018 -- 0.12 inch Rain since last run" -- not even sure where it gets that from -- because there has not been any recorded since 8/22.. I know this for a fact because my weather source is my own Weather Underground station -- and there has been no rain at all since 8/22.

  • Avatar
    Nicholas

    If your Weather Underground has API key setup it will also get forecast not only your own observed data. Why do you think "skipping" is bad ? Depending on zones settings and evapotranspiration zones might be skipped and that's how it should work. Do you actually see vegetation wilting ?

  • Avatar
    Rick Felter

    Skipping is fine if there is a surplus. THAT. is what it’s supposed to do. What it is not supposed to do is when the simulation runs and the logs show that the zones have water needed values, and it is supposed to run, and it just doesn’t. And yes, we develop brown spots on the lawn when we have continuous days of 90 deg+ weather and sun with no rain.

    Why can’t you just acknowledge it isn’t working properly instead of arguing with me? When it skips a day, the watering history states why (Surplus, restriction, etc) — in these cases the program prepares to run - and then doesn’t. And the watering history shows nothing at all.. And the logs indicate that the program is supposed to run in some negative value of minutes after it was supposed to run.

  • Avatar
    Nicholas

    Hi Rick,

    I'm not arguing for the sake of arguing, I'm trying to find out if your problem steams from the Finish before ... option or something else. We can't replicate the issue with Finish before... not starting watering. I believe that it might be something related to Available Water management and weather data received from WUnderground. RainMachine reports (on the graphs) what data it got from WUnderground. 

    What I think it happens is:

    1. RainMachine gets RAIN and QPF report from WUnderground which is not quite correct with your observations

    2. This RAIN/QPF is saved as Available Water and programs are getting skipped.

    3. The program not showing on watering log for an entire day could this be because when you changed from Finish by  to Start before the next run was reset to the current day and since program was every 2 days it didn't water next day ?

     

    To solve 1. I would add another weather service like NOAA or Forecast.io. For 2. maybe reduce the Field Capacity from each zone setting to have less available water.

    P.S. Program showing with negative start offset in logs is not a bug, it's correct it means that program had been scheduled to start in the past from the current time.That doesn't mean that program really started watering, just that it supposed to start but it might be skipped for various reasons (adaptive frequency, restrictions etc).

  • Avatar
    Rick Felter

    I am using two sources — NOAA and WU. I am using WU without an API key just for my station data.

    Here’s the thing - I switched it back to “Start 2 hours before sunrise”, and the schedule works fine. I don’t want to start messing with field capacity and other variables because the zones and programs work perfectly when using the other scheduling options. Now that we are in September, I can try using the “Finish by” option again since there will be less concern of high water need.

Please sign in to leave a comment.